Skip to main content
Mercury Decide evaluates named questions against a shared state and returns typed answers with probabilities. Use it for routing, classification, and scoring with POST /v1/decisions and the model mercury-decide.

Send a decision request

Set INCEPTION_API_KEY to your API key. Each request includes a model, a state, and a non-empty map of questions. The names you choose for questions are preserved in the response.

Question types

The state, instructions, and criterion descriptions can be strings, JSON objects, or arrays. Instructions may be omitted or null. Questions are evaluated independently against the shared state. A score can be fractional; it is not restricted to a single level.

Read the response

The response contains the model name, an answers map keyed by your question names, and usage. For example, a request with a single noul question named billing could return:
The values above are illustrative. For choice, probabilities uses your option names. For score, it uses string indices such as "0" and "1", and legend maps those indices back to your criteria. Both include a confidence value between 0 and 1.

Pricing and limits

Mercury Decide costs $0.04 per million input tokens. Only input tokens are billed; output tokens are reported in usage.output_tokens but are not charged. See Models & Pricing.
  • Send requests to /v1/decisions. Mercury Decide does not support /v1/chat/completions, streaming, or tool calling.
  • Use Error Codes for authentication, rate-limit, and service errors.