Mutual Trust documentation

Mutual Trust gives an API owner one place to decide which partner workloads may call a service, enrolls those workloads with private client certificates, and shows whether the decision is actually enforced at each gateway.

Documentation menu

Getting started

  • Create a sandbox space, pair a gateway, enroll a workload and see one allowed and one denied request, then withdraw access.

  • Trust spaces, services, route templates, invitations, grants, workloads, issuers, policy revisions, manifests, receipts and operations.

  • What differs between environments, how the two are kept unmistakable, and how to request production access.

Guides

  • Sandbox tokens and OIDC workload identity (including Kubernetes service accounts), challenge, proof of possession and 202 polling.

  • Two-thirds renewal with jitter, the key-continuity proof, reload confirmation and recovering from an expired leaf.

  • Suspend, resume and revoke grants, revoke a single leaf, CRLs, the deny set, gateway acknowledgments and offline behaviour.

  • Scoped invitations, accepting and claiming an organization, and previewing scope changes before you publish them.

  • What counts as a production connection, plans, Stripe Checkout, the grace period and the customer portal.

  • The role matrix, explicit billing administration, API credentials, support access grants and audit export rights.

  • Every gateway deny reason, every API problem code, and how to use request IDs.

Gateways

Mutual Trust enforces at your ingress. The gateway guides cover Envoy, Istio, Kubernetes ingress-nginx, NGINX, Traefik, HAProxy, Kong, Caddy, AWS API Gateway, AWS ALB, Cloudflare and the standalone mTLS proxy. Every gateway applies the same verification rules.

Reference

  • Authentication models, conventions and every endpoint with request fields, response examples and errors.

  • Every mt command and flag, the files it writes and its exit codes.

  • Event envelope and types, manifest JWS, policy document, acknowledgments, receipts, proofs, certificate profile and IDs.

  • RFC 9457 problem details and every stable code the API returns.

  • Threat model, trust boundaries, tenant isolation, key custody and staff access controls.

  • Connect Claude and other MCP clients to your organization with a scoped, revocable credential.

  • Passkey sign-in for customers and staff, enterprise SSO through OIDC, and how sessions and assertions are verified.

  • What changed in the docs, API, CLI, enforcer and gateway integrations.

Machine-readable resources

Origins

Mutual Trust origins
OriginPurpose
https://mutualtrust.ioPublic product site and these docs (static).
https://app.mutualtrust.ioCustomer portal. Serves /v1 with session cookies and /auth/* sign-in.
https://api.mutualtrust.ioAutomation API for API credentials, gateway credentials, workload proofs, CRLs and Stripe webhooks. Cookies are ignored here.
https://admin.mutualtrust.ioSectigo staff and finance console behind Cloudflare Access with MFA. Not a customer surface.
https://mcp.mutualtrust.io/mcpMCP server for Claude and other MCP clients.