Authentication
1. Mint a mandate
Validates the requested scope against the intent card, then returns a signed, short-lived mandate JWT.Response
403 with
code: "mandate_violation" and a suggested_narrower_scope. See
POST /v1/mandate/dispense for every field.
2. Guard a tool call
Attach the mandate asX-Inviolet-Mandate and post the action to the decision
engine.
kind starts with allow when the call may proceed. Other kinds
map to actions: approval (queued for a human — poll status), step_up (run
the IdP challenge and retry), deny_with_reroute (fall back to the rerouted
handler), or a hard deny. See POST /v1/mcp-proxy/call
for the full list of decision kinds and status codes.
3. Verify a mandate
The gateway publishes its public keys as a JWKS document. Verify the RS256 signature locally with any JWT library.Revoke a mandate
cred_id to the blocklist and propagates to any downstream credential
broker.
Full OpenAPI spec
The complete OpenAPI spec powers the API Reference tab — use it to auto-generate clients in any language.Read next
- API Reference — every endpoint in detail
- Node SDK — the typed client for JavaScript / TypeScript
- Python — the same REST flow from Python