Interoperability
The goal is to work alongside these standards instead of replacing them. Naming a protocol here is not a compatibility claim. Last checked 2026-11-02.
| Label | Meaning |
|---|---|
| Used in prototype | Dial prototype code calls it today |
| Possible adapter | A plausible integration with no code |
| Adjacent | Solves a related problem, and integration is an open question |
Agent and machine payments
| Standard | What it does | Possible relationship | Status |
|---|---|---|---|
| x402Â | HTTP-native payment authorization | Payment as activation or settlement evidence, with replay protection | Possible adapter |
| MPPÂ | Machine payments over HTTP 402, from Tempo and Stripe | Payment route adapter | Possible adapter |
| AP2Â | Signed agent payment mandates | Bind an approved mandate to a SPORE authority reference | Possible adapter |
| MCPÂ and A2AÂ | Agent tools and agent communication | Expose program invocation to agents | Possible adapter |
| ERC-8004Â (Draft) | Agent identity, reputation and validation registries. Payments are out of its scope | Optional identity and validation evidence | Possible adapter |
Cross-chain and execution
| Standard | What it does | Possible relationship | Status |
|---|---|---|---|
| ERC-7683Â (Draft) | A solver-facing format for cross-chain intents | Order generation and settlement adapter | Possible adapter |
| Chainlink CCIPÂ | Cross-chain messaging and token transfer | Transport adapter, with no need to rebuild it | Possible adapter |
| CreateXÂ | A shared CREATE2 and CREATE3 deployer | Deployment strategy | Used in prototype, blocked |
Invoicing and agreements
| Project | What it does | Possible relationship | Status |
|---|---|---|---|
| Request Network | Crypto payment requests and reconciliation | The EVM invoice pattern creates Request invoices today | Used in prototype |
| Accord Project | Computable legal agreement templates | Agreement terms referenced from a SPORE | Adjacent |
Cardano
| Project | Notes | Status |
|---|---|---|
| CIP-0157 Cardano URIs: Enhanced Payments | Open pull request, not merged. It covers payment URIs, and invoice metadata would be separate | Possible adapter |
| Masumi | An agent network on Cardano, with its own payment layer | Adjacent, current status to be confirmed |
| x402 on Cardano | Support not verified for this page | Possible adapter |
Any invoice metadata format Dial proposes for Cardano would be a standards goal: optional, versioned and publicly implementable. A public format can’t require anyone to route through Dial. Fees apply only on routes that enforce them.
Explore invoicing: Programmable Invoicing
Last updated on