Route work
Choose the best allowed tool, workflow, or destination for a task.
DECISION APIs
Give your software a clear next decision.
Send the situation and the choices you allow. Get back a structured answer, confidence, alternatives, or a clear “not enough information” result.
You stay in control. The API recommends a decision; your application decides what happens next.
WHAT IT DOES
Turn messy inputs into decisions your systems can act on.
Use one consistent interface for routing, ranking, classification, prioritization, and “should we proceed?” decisions across your products and operations.
Prioritize opportunities
Rank leads, search terms, support requests, issues, or content by what deserves attention next.
Classify at scale
Turn large streams of messy text or records into consistent categories your software can use.
Know when to stop
Return an explicit unknown result when the available information does not support a confident answer.
HOW IT WORKS
Three steps from input to usable answer.
1
Send the situation
Provide the task, the relevant data, and the choices your application is willing to accept.
2
Get a bounded decision
Receive the selected choice, confidence, ranked alternatives, or an explicit unknown result.
3
Use it your way
Your own rules decide whether to accept the answer, ask for review, or take an authorized action.
AVAILABLE FIRST
Tool Router
When an assistant, workflow, or software agent has several allowed tools available, Tool Router chooses the best fit for the current task. If none is a good fit, it says so instead of inventing one.
- You define the allowed choices.
- You receive a structured result, not free-form prose.
- Low-confidence requests can return “unknown.”
- Your application keeps control of permissions and execution.
Example
TaskFind this customer before drafting a reply
Allowed choicesCustomer lookup · Draft reply
DecisionCustomer lookup
Confidence88%
PRODUCT FAMILY
One decision layer for many business systems.
The same pattern can sit behind your CRM, support desk, website operations, search program, content workflow, internal tools, or agent platform.
Tool Router
Choose the best allowed tool or action for the job.
Context Router
Choose which information sources should be used for a task.
SEO Opportunity
Rank the pages, queries, and issues most worth working on next.
Support Triage
Route and prioritize incoming customer requests.
Search Intent
Classify what a searcher wants and how commercially relevant it is.
Entity Match
Estimate whether records refer to the same person or company without auto-merging them.
BUILT FOR CONTROL
Useful when the answer is clear. Safe when it isn’t.
Bounded choices. The API chooses only from the options you provide.
Confidence included. Your software can set its own acceptance threshold.
Explicit unknown. Ambiguous requests can stop instead of forcing a guess.
No automatic side effects. A decision does not automatically publish, send, spend, delete, or execute.
GET ACCESS
Provision your first Decision API key.
Create an account, generate a key, and start with the Tool Router endpoint. You can revoke keys from your portal at any time.
FAQ
Decision API questions
A Decision API takes a defined situation and a bounded set of choices, then returns a structured decision your software can use.
The API can return an unknown result instead of forcing a choice. Your application can then request review or use another workflow.
The decision response itself does not perform an external action. Your application controls what is authorized to happen after the decision.
Yes. Decision products can be connected to business data and software sources through scoped integrations built for that use case.
Create an account, provision an API key, and use the Tool Router schema as the first integration point.