Skip to main content
Every error has the same JSON body. doc_url in each error links to its code’s row in the table below.
That came from POST /v1/proposals with "policy": {"goal": "harvest_losses", "tracking_error": "abc"}. Errors are free: they cost no credits. These are answers, not errors: a proposal with outcome: "infeasible" or "clarify" (HTTP 201), and a trade check with status: "rejected" (HTTP 200).

Codes

Idempotency

POST /v1/analyze, /v1/proposals, /v1/trades/check and /v1/accounts accept an optional Idempotency-Key header (MCP: the idempotency_key argument). Send a new UUID per request and the same one on a retry:
  • Same key and body within 24 hours: the first answer comes back with the same status and body, the header Idempotent-Replayed: true and Abacus-Credits-Charged: 0. Nothing is charged again.
  • Same key, different body or route: 409 idempotency_key_reused.
  • Same key while the first request still runs: 409 idempotency_in_progress.
  • Only 2xx answers are kept. After an error the key is free again, so fix the cause and retry with the same key.
POST /v1/commits always needs a key (see idempotency_conflict above).

Versioning

v1 is frozen. Send Abacus-Version: 2026-11-15 to pin it; every response has Abacus-Version with the version used (the current one when you send none). Later changes get a new date; a pinned date keeps its behaviour.

Proposals that fail in the background

A proposal that answered 202 and then failed has status: "failed" and the same error object on GET /v1/proposals/{id}. It costs nothing.

Over MCP

An API error is a tool result with isError: true whose text is the same JSON. The text starts with Error executing tool <name>: . See MCP server.