Clash of Coins

Agentic checkout for Clash of Coins

For Humans

If you are a human: give your agent this skill and this service link.

Unified discovery

Use case: agentic checkout for gaming platforms

x402.clashofcoins.com is a production use case of agentic checkout for gaming platforms: agents can discover game offers, quote purchases, complete payment-challenge retries, and verify final delivery status.

What agents can do

Agents can discover the active catalog, compare sale and shop items, quote the exact payable request, receive a 402 PAYMENT-REQUIRED challenge, retry with the payment header, and poll delivery or ledger status before creating another payment.

Why x402 for game checkout

x402 keeps payment authorization attached to the HTTP request that creates the purchase. That makes the unpaid challenge, paid retry, settlement receipt, and delivery state visible to autonomous agents without hiding them behind card-session state.

Reliability and settlement model

Payment settlement is not treated as final game fulfillment by itself. The gateway persists purchase state, records payment references, calls the game delivery API for shop items, and exposes status routes for recovery.

How duplicate payments are avoided

Agents should preserve request bodies and idempotency keys, inspect existing payment references, and poll status routes after timeouts or 5xx responses before sending another mutating purchase request.

What makes this different

This is an alternative to generic PSP checkout for agentic game commerce: catalog, MCP tools, OpenAPI, OAuth metadata, x402 challenge semantics, recipient routing, and fulfillment recovery are all published on-domain for scanners and agents.

MCP and Skills

Presale checkout

POST /agentic/x402/buy

Game shop checkout

https://x402.clashofcoins.com/shop