Skip to content
Decisions API logo

Decisions API

Returns typed choice, score or yes/no answers with probabilities for text, JSON or image input, served through a model API.

From $10 onceActively maintained

For developersFree tier
decisions-api.dev ↗Launched on Product Hunt · Oct 5, 2026
Open decisions-api.devAlternativesSet it up for my teamIs Decisions API yours? Claim the card →
At a glanceswept Oct 22, 2026

102 linking domains

Emerging

For
Developers and teams classifying, scoring and routing text or images through an API.
Price
From $10 oncepricing page, read Oct 22, 2026
Activity
Actively maintainedsite updated 11 days ago
Runs as
API
Used for
  • Route support tickets to billing or urgent queues
  • Score messages for urgency on a 0-3 scale
  • Run yes-or-no behaviour checks on agent output
read off decisions-api.dev on Oct 22, 2026
Worth knowingcomputed from what we read · each with its source
Pricingpricing page, read Oct 22, 2026

From $10 once

pricing page

How a program reaches itfound, not claimed · read Oct 22, 2026

This card as JSON, for your agent →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use Decisions API for?

Sign in to leave a note
Questions this page answers
  • What is Decisions API?

    Returns typed choice, score or yes/no answers with probabilities for text, JSON or image input, served through a model API.

  • Who is Decisions API for?

    Developers and teams classifying, scoring and routing text or images through an API.

  • How much does Decisions API cost?

    Paid plans start at $10 once, per Decisions API's pricing page on 2026-10-22.

  • Do people use Decisions API?

    Emerging.

  • Is Decisions API still maintained?

    Actively maintained: site updated 11 days ago.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

How we read every tool → · By INITE Atlas Desk