The Atlas of Agentic Stablecoin Compliance
The cartography
of compliance.
Mapping how stablecoin payments meet regulation — from protocol to policy. Two visual models, one classification legend, and the compliance-depth thesis that explains why stablechains exist.
Two Models, One Legend
How we map compliance
Protocols
The agentic payment stack
Agent Commerce Kit — Identity
W3C DID + Verifiable Credential framework for autonomous agent identity. Establishes principal→agent delegation chains with cryptographic proof.
Catena Labs
HTTP 402 Payment Required Protocol
HTTP-native micropayment protocol using the 402 status code. Server declares price, client pays in stablecoin, server delivers content.
Coinbase / x402 Foundation
Agent Commerce Protocol
Coinbase protocol for agent-to-agent commerce. Builds on CDP AgentKit for wallet-native authorization and multi-step transaction flows.
Coinbase
Machine Payments Protocol
Tempo network protocol for machine-to-machine payments. Dedicated payment lanes with TIP-403 Policy Registry for compliance routing.
Tempo (Stripe/Paradigm)
Regulatory Landscape
Global regulatory regimes
The Network
Satellite sites across the Atlas
Skills Ecosystem
The compliance interoperability layer for fintech AI skills
Four published skills ecosystems tell developers how to write stablecoin code. Atlas maps where that code lives in compliance architecture — which Stack layer, which STP stage, which checkpoint type, and whether it's code-enforced or policy-enforced.
How Atlas maps fintech skills to compliance coordinates
circlefin/skills bridge-stablecoin → S5 Transport · Travel Rule Gate · VASP Obligation at S8 Finality coinbase/agentkit Authenticate → S2 Identity · T6 blue · code-enforced Gate at L3 Execution coinbase/agentkit Send + Trade → S6 Authorization · T3 orange · code-enforced Gate