Integration Guides Overview
These guides explain how to integrate AgentTrust Gateway in front of an agent-facing API. They cover identity, policy, payment, receipts, audit, and proof.
How to use these guides
Each guide is independently readable, but the gateway is a pipeline. The recommended order matches the order requests flow through the runtime:
- Start with the request lifecycle. Understand the 401 → 402 → 200 + receipt + audit + proof flow before choosing components.
- Choose an identity model in Agent identity. Wallet schemes, DID resolution, and VC profiles are independent; pick what your providers can produce.
- Choose a payment mode in Payment lifecycle. x402 sandbox, public_x402 wire, and emulator-backed pilots are the three starting shapes.
- Decide proof and audit requirements in Receipts & proof and Audit & SIEM. Receipts ship by default; SIEM presets and retention are operator choices.
- Run the no-credential demo before any external verification. Every design-partner pilot starts with the credential-free path.
If you are not sure where to start
Three paths lead to a productive first conversation:
- No-credential demo — see the gateway run end-to-end without any operator credentials. Good for a 30-minute call. Demo tracks.
- Local x402 / emulator pilot — wire the gateway in front of one sandbox endpoint. Real receipts, real audit chain, sandbox payments. Payment lifecycle.
- Design partner pilot checklist — bring one paid endpoint, acceptance criteria, and (optionally) operator credentials. Design partners.
What this documentation does not claim
Every page on this site enforces the same boundary register. None of the following are claimed:
- Not enterprise GA.
- Not officially certified for Okta, Entra, or Google SAML.
- Not officially certified for SCIM 2.0 conformance.
- Not SOC 2, ISO 27001, HIPAA, or PCI certified.
- Not externally operator-verified end-to-end until operator credentials run.
Reading order
Continue with Agent identity, then Payment lifecycle, then Receipts & proof, then Audit & SIEM, then Enterprise SSO.