x402 & agent payments
Programmatic HTTP payments are a future access path, not a shortcut around metering or settlement correctness.
In this chapter
What x402 adds#
x402 lets a resource server communicate payment requirements through HTTP 402. A compatible client can select an accepted payment option, authorize it, and retry the request with a payment payload. Verification and settlement then follow the selected scheme.
For IdleAI, this could let agents purchase bounded inference without first completing a conventional prepaid-account flow. It complements wallet accounts and API keys; it does not replace supply, accounting, privacy controls, abuse protection, or compliance requirements.
Payment schemes#
| Scheme | Fit | Boundary |
|---|---|---|
| exact | A known fixed charge for a bounded task. | The price must be known and accurately represented before execution. |
| upto | Usage-based requests where the buyer authorizes a ceiling. | Actual metering must be trustworthy; authorizing a maximum does not prove reported usage. |
| Batch/channel approaches | High-volume repeated payments where per-request settlement overhead matters. | Additional lifecycle, solvency, recovery, and protocol complexity. |
Support varies by network, facilitator, token, SDK, and protocol version. Streaming and partial settlement need explicit handling; charging each streamed chunk is not automatically the right design.
Robinhood compatibility is a release gate#
The Coinbase facilitator support matrix reviewed for this project did not list Robinhood Chain. Third-party Robinhood/USDG implementations were identified as candidates, not audited production dependencies. EVM compatibility alone does not prove an x402 integration works.
- Confirm the deployed token's signing domain and authorization behavior.
- Confirm the facilitator actually verifies and settles
eip155:4663for the intended scheme. - Test expiry, nonce replay, amount/recipient binding, retries, timeouts, and reconciliation.
- Review the implementation, service terms, screening requirements, signing custody, and gas responsibility.
- Do not silently settle on another chain while claiming Robinhood-native payments.
What x402 does not provide#
x402 is not prompt encryption, model verification, seller payout distribution, or an automatic refund/dispute system. Wallets, amounts, and transaction timing can be linkable. Payment authorization also does not make every execution or settlement failure disappear.