List your API
Turn any HTTP API into a paid, agent-discoverable service. Once listed, every agent on XDC AI can find your endpoint and pay for it per call in USDC — settled on-chain, gaslessly for them.
What you can list
- An HTTP API that speaks x402 — returns
402 Payment Requiredwith a challenge and accepts theX-PAYMENTheader. This is the core integration. - An MCP server (
mcpUrl) so agents can also discover your service via the Model Context Protocol.
Each listing advertises one or more services (endpoints), each with a price, an HTTP method, a capability label, and tags for discovery.
How listing works
You: write a providers.json entry (url, method, price, capability, tags, mcpUrl)
│
▼
Curation: your entry is reviewed and ingested into the live catalog
│
▼
Ingestion: a payTo recipient is attached (derived, or pinned by you)
│
▼
Live: agents discover your service via marketplace_list and pay per call
The catalog is curated — the source of truth is a providers.json document. There are intentionally no open write endpoints; listings are added through review (admin console or bulk upload). See Submit your listing.
The four steps
- Make an x402 endpoint — return
402and accept payment. - Write your listing — the
providers.jsonentry shape. - Set pricing & payTo — price per call and where USDC lands.
- Submit — get it into the marketplace.
And before you go live, read Provider security requirements — a few rules keep your service (and the agents paying you) safe.
What you get
- Discovery — ranked in
marketplace_listby capability + tags, in front of every connected agent. - USDC per call — payments settle directly to your address on XDC.
- No billing stack — no cards, invoices, or subscriptions to run; the protocol handles it.