Introducing the Brainis API

The Brainis API is live. External tools can now read your organization's data and perform actions through the same governed pipeline the in-app AI uses.

What it does

Reads. GET /v1/tasks, /v1/deals, /v1/candidates, /v1/employees, /v1/invoices, /v1/agents, /v1/agent-runs, /v1/deliverables, and more. Org-scoped, cursor-paginated, with an updated_since filter for incremental syncs.

Writes. A single POST /v1/actions endpoint taking a verb from the governed registry. GET /v1/verbs lists every available action with its module, risk class, credit cost, and required fields.

Governed, not a side door

This is the part worth emphasizing. An API write runs the full pipeline: verb validation, risk scoring, your authority contract, credit accounting, and the audit chain. Depending on your settings, a call returns executed, pending_approval, or denied with a reason.

The API cannot do what your configured autonomy would not allow the AI to do. That is deliberate: an integration should not be a way around the governance you set up.

Two flags make integration safe. dry_run: true returns the decision without doing anything, and an idempotency key makes retries safe.

Authentication

Generate a scoped key in Admin, API Keys. Keys begin with br_live_ and are shown once. Send them as Authorization: Bearer br_live_….

Keys are generated server-side with a cryptographic random source. Any older keys with the brn_ prefix have been deactivated: they were generated in the browser with a non-cryptographic source and were predictable.

Limits

60 requests per minute per key by default, returning 429 with Retry-After. Actions consume credits at each verb's listed cost.

Not in v1

Stated plainly: no outbound webhooks, no file upload, and no per-user permissions for key callers (scopes replace them). Poll with updated_since where you would otherwise want webhooks.

Full reference at /api-docs, and a getting-started guide in the help center.