Base URL:
Send your API key as header:
Or Authorization: Bearer <key> / ?apikey= depending on your client.

Authentication

Main endpoints

Health

Returns service status and store mode (postgres in production).

Create mandate

Application API key. Body includes signed rules, agent_id, domain, owner_signature. Response includes id, status, and apiKey (mandate key — once).

Check (decision)

Mandate API key. Body is either:
  • a normalized action (agent_id, domain, action_type, value, …), or
  • a protocol envelope (protocol: raw | ap2 | vi | acp | spt + credential/session).
    KYI normalizes and crypto-verifies (AP2/VI) on the server, then runs Cedar.
Response:
See Protocol check & merchant verify.

Merchant verify

Application API key + mandate_id (or mandate API key). Same body shapes as /decisions.
Re-checks the cart/intent against the mandate and returns ALLOW/DENY + receipt (merchant shield).

List mandates (dashboard)

Via User-Service (authenticated dashboard user):

List decisions for a mandate

Public receipt key (auditors)

Returns Ed25519 public key for offline receipt verification.

Fetch receipt by id (auditors)

Returns full receipt JSON including on-chain fields when batch is published.

Verdict values

Common reason codes

SDK vs REST

Prefer @abstraxn/warrant for TypeScript backends — it handles canonicalization, seals, and error defaults. See SDK quickstart.

Next step

Verify receipts — prove a decision offline.