What is x402?
x402 is a payment pattern that uses HTTP 402 Payment Required to advertise how a client can pay for an API request. An agent or application can inspect payment requirements, authorize payment through a compatible client, and retry the original operation with payment proof.
Understand the request sequence
First call the protected endpoint without payment. Read the server's 402 response and verify the network, asset, amount, recipient and resource against your own spending policy. Authorize payment only if the request is expected. Then retry with the appropriate payment information.
Control authorization separately
A successful payment is not a substitute for identity or permission checks. Some endpoints may require both a workspace bearer token and payment. Never send credentials to an untrusted URL merely because it advertises an x402 challenge.
Prevent double charges
Network failures can leave payment settlement ambiguous. Use request identifiers and idempotency controls where supported. If the client cannot determine whether payment succeeded, stop and reconcile rather than blindly repeating the charge. Establish maximum spend per request and per run.
Zorqelio's current pricing model
Zorqelio lists pay-per-request AI agent validation and freshness endpoints at $0.01 USDC on Base per request, subject to the live service configuration. Its Starter workspace subscription is separate; x402 purchases do not increase workspace quotas. Verify current terms on pricing.
When to use paid agent checks
Per-request payment can fit occasional stateless checks; a workspace subscription may fit recurring monitoring and contract management. Choose based on call volume, operational requirements and payment support—not merely whether an endpoint returns HTTP 402.
For implementation details and current capabilities, consult the Zorqelio documentation. Technical examples are illustrative and should be tested against your own policies and supported schema dialect.