Documentation / Start here
Quickstart
Send one request, read the named answers, and keep the decision ID for later.
1. Set your origin and key
Ask your staging administrator for the API origin and a tenant-scoped inference key backed by a funded wallet. For a local stack the origin is http://localhost:8080. Inject ARBIRO_API_KEY from your secret manager in a server-side shell; never put it in browser code.
Shell
export ARBIRO_BASE_URL=http://localhost:8080
# ARBIRO_API_KEY must already be set in this shell.2. Submit a decision
This fixture classifies a scheduling message and asks whether it mentions a date. Run the same command again to retry the same submission. Use a new idempotency key when changing the input.
Shell · curl
curl -i "$ARBIRO_BASE_URL/v1/decide" \
-H "Authorization: Bearer $ARBIRO_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: docs-example-01" \
--data-binary @- <<'JSON'
{
"policy": "default-cascade@v1",
"state": {
"message": "The delivery window moved to Friday."
},
"questions": {
"topic": {
"type": "choice",
"instructions": "Classify the message.",
"criteria": {
"schedule": "Timing or dates",
"other": "Any other subject"
}
},
"mentions_date": {
"type": "noul",
"instructions": "Does the text mention a day or date?"
}
}
}
JSON3. Read the result
HTTP 200 · response excerpt
{
"status": "completed",
"branch": "answer_o",
"model": "decisions-staging-v1",
"answers": {
"topic": {
"type": "choice",
"choice": "schedule",
"confidence": 0.9,
"probabilities": {
"schedule": 0.94,
"other": 0.06
}
},
"mentions_date": {
"type": "noul",
"noul": 0.98
}
},
"usage": {
"input_tokens": 148,
"output_tokens": 24
}
}The full native receipt also includes a decision ID, supplier cost and Arbiro charge. If you receive 202, follow the Location header instead of treating it as a completed answer. See Polling and retries.