Evenbead docs
Contents

Evenbead developer docs

Evenbead is a double-entry ledger built for a company's own AI agents and its accountants. Every action in the web app is an API operation and an MCP tool, so an agent can do what a person can, inside the same rules: amounts in integer cents, an idempotency key on every write, a dry run before anything posts, and a proposal queue for anything above the agent's policy. Every change lands in a hash-chained audit log that names the person or agent, and for agents the model.

Base URLs

SurfaceURL
REST APIhttps://api.evenbead.com/v1/...
MCP serverhttps://api.evenbead.com/mcp
OpenAPI 3.1 documenthttps://api.evenbead.com/openapi.json (also here)
Web apphttps://app.evenbead.com

https://app.evenbead.com/v1/... answers too, so older integrations keep working; new ones should use api.evenbead.com, which serves the API and MCP only (no browser pages, no cookies).

Rules every client follows

  • Money is integer cents. 4299 is $42.99. Floats are refused.
  • Writes carry an Idempotency-Key. Repeat the same request with the same key and you get the original result; nothing posts twice.
  • Preview with dry_run: true. You get the exact balanced entry, the period, the policy verdict and the affected balances, and nothing is written.
  • Agents propose; people approve. An agent's write within its policy posts. Above its threshold, on a sensitive account, in a soft-locked period, at low confidence or for a new counterparty, it becomes a proposal for a person (or a supervising agent) to approve.
  • Agents say which model they are. Agent writes need the X-Agent-Model header; it is recorded in the audit log.
  • Errors are stable. Every error has error.type (for example period_locked, insufficient_scope, rate_limited) that code can branch on.

Reading and exporting your own data is never metered.

Start here