{
  "error": "version mismatch: expected 2, got 1"
}

​
Error shape

Errors return a compact JSON object:
​
error
string
required
Human-readable error message. Agents should preserve this value with the route, HTTP status, entity ID, proposal ID, and user intent.

​
Status codes

Invalid email, invalid UUID, invalid constitution YAML, invalid state transition, missing spend fields, or unknown action/proposal kind.
Missing Authorization header, invalid bearer format, bad API key, inactive JWT, or unavailable platform token introspection.
Resource does not exist or is not visible to the authenticated account.
Version mismatch on a versioned entity update.
Constitution YAML exceeds the 64 KiB entity creation limit.
Internal server or persistence failure. Retry only when the operation is idempotent or after checking current state.

​
Agent retry policy

1

Preserve context

Keep the route, HTTP status, request intent, entity ID, proposal ID, and error value.
2

Re-read on conflict

For 409, fetch the latest entity, compare state, and re-evaluate the requested action.
3

Do not blind retry legal actions

For filing, treasury, hiring, amendment, or dissolution actions, surface the failure to a human when state is ambiguous.