Skip to main content
Every SDK is a thin wrapper over these HTTP endpoints. Use them directly from any language, or when you want fine-grained control. The full endpoint reference lives under API Reference.

Authentication

1. Mint a mandate

Validates the requested scope against the intent card, then returns a signed, short-lived mandate JWT.

Response

If the requested scope exceeds the intent card, the gateway returns 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 as X-Inviolet-Mandate and post the action to the decision engine.
The response 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.
See GET /v1/mandate/jwks.

Revoke a mandate

Adds the 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.
  • API Reference — every endpoint in detail
  • Node SDK — the typed client for JavaScript / TypeScript
  • Python — the same REST flow from Python