x402 on Base vs Solana: how buyers should choose
A buyer-focused comparison of network identifiers, wallet support, service availability and policy implications.
DIRECT ANSWER
Choose Base or Solana according to the service's advertised payment requirements and the signer your agent can operate safely. x402 clients select a supported scheme and network pair; the directory should not convert one network into another. Base has the largest share of the TOLL·402 curated catalog, while many bulk-discovered routes advertise Solana identifiers.
Key takeaways
- The live payment requirement, not a directory filter, supplies the authoritative network identifier.
- Your client must register a compatible signer and payment scheme for that network.
- Network choice changes wallet operations and facilitator compatibility, not the need for spend controls.
Network identifiers matter
Current x402 uses explicit network identifiers such as CAIP-2 forms. Human labels like Base or Solana are useful in navigation but should not replace the value the server returns. A client that supports one chain cannot safely assume it can satisfy a requirement for another.
| Dimension | Base | Solana |
|---|---|---|
| Signer family | EVM account and EIP-712 authorization | SVM keypair and Ed25519 signing |
| Common asset | USDC | USDC |
| Directory use | Large curated and registry presence | Large bulk-registry route presence |
| Decision rule | Use when requirement and policy allow | Use when requirement and policy allow |
Facilitator compatibility
A facilitator verifies and settles only the scheme, network and asset combinations it supports. The x402.org default facilitator is intended for specific test networks, while production facilitators advertise their own coverage. Buyers should verify facilitator and client support before authorizing a mainnet workflow.
A practical policy
Allow the smallest set of networks your workflow needs. Bind maximum payment, accepted asset and endpoint host to each tool. When a service changes its payment requirement, pause and review instead of silently switching networks or tokens.
Related directory entries
Sources and methodology
TOLL·402 distinguishes public claims, registry discovery, unpaid quote checks and settled paid-call verification. Sources below support the visible claims; presence in a registry is not treated as verification.
- x402 network and token support — Authoritative network identifiers and facilitator guidance.
- x402 buyer quickstart — EVM and SVM signer setup.
- TOLL·402 network filters — Curated network coverage.