Pick the buyer. The protocol is the same.
Four pages, four buyer categories. Every one runs on the same passport, the same gateway, the same receipts. Choose where the work meets you.
Payments
Move money with accountable identity.
Six rails, one delegation surface. Four-gate spending controls. Receipts that hold up in chargeback.
- ACH · cards · wires · stablecoin · BNPL · checkout
- Per-merchant scope, per-day budget
- Custody receipts on every authorization
read the page →
Content
Terms that travel with the bytes.
AMCS governance blocks. Attribution receipts. Behavioral derivation rights enforced at fetch time.
- aps.txt + HTML embed + HTTP header
- D / P / G / C Merkle attribution
- Cascade revoke on misuse
read the page →
Compliance
Audit trails as evidence.
Signed action and custody receipts mapped to EU AI Act, NIST AI RMF, ISO 42001 controls.
- Crosswalk to 14 frameworks
- One-click compliance report
- Retention windows enforced at the gateway
read the page →
Enterprise
Govern internal agent fleets.
Bring your own identity. Per-team delegations, per-tenant isolation, fleet-wide cascade revocation.
- SPIFFE · OAuth · OIDC bridging
- SSO · audit log · SCIM
- Multi-tenant gateway with quotas
read the page →
One protocol underneath.
What stays constant
01
Same protocol
Every solution uses the same passport, delegation, and receipt primitives. No special cases.
02
Same gateway
A single enforcement boundary for all four. One thing to deploy, one thing to monitor.
03
Same accountability
Action and custody receipts on every operation. Cascade revocation on every misuse.
For AI agents: llms-full.txt · MCP descriptor