Agents are a demand channel your storefront cannot serve
An assistant asked to book a trip, restock a kitchen, or buy a dataset has to get through a page built for human hands: a cart, a signup, a card form, a one-time code. Most of the time it gives up and picks whoever it can actually pay.
A customer that cannot abandon a cart
An agent does not get distracted, bounce on a signup form, or need a card on file. It asks the price, pays it, and takes delivery in one exchange.
Paid before you deliver
The payment is verified before your system is asked to do any work, so you are never shipping on trust or chasing an invoice afterwards.
No chargebacks
A USDC settlement on XDC is final the moment it confirms. Nobody can reverse it 60 days later, and you are not carrying card-dispute risk on every order.
The money is yours, not ours
Payments land at an address only you control. We never hold your balance, and there is no payout schedule to wait on.
Nothing to rebuild
Your API, your database, your own upstream keys, all unchanged. The paid layer sits in front of what you already run.
Priced per request, down to cents
Charge a fraction of a cent for a lookup and a few dollars for a booking. Settlement is cheap enough that small amounts still make sense.
Let us run the payment, or run it yourself
The difference is who owns the payment code, and therefore how we get paid. Both are free to begin and you can change your mind later.
List on the gateway
We put a paid front door on the API you already have.
- No code changes. Point us at your endpoint and the key it already uses.
- Set a USDC price per route, and keep any route free.
- Your service gets listed where agents actually look for it.
- An agent is only charged when your API answers successfully.
- Up to 5 services, 50 priced routes each, on the free plan.
- Payouts split on-chain to a wallet you control, per payment.
Best when you have an API or a booking system and want the shortest path to being paid by agents.
Start listing, freeUse the public facilitator
You host the x402 endpoint. We verify and settle the payments.
- The payment logic lives inside your own application.
- No cut of your revenue. You pay per confirmed settlement instead.
- Seller API keys, usage, and a settlement record with every hash.
- Verify calls and health checks never draw down credit.
- Gasless EIP-3009 settlement in USDC on XDC.
- Top up in USDC from a wallet you already hold, no card, no invoice.
Best when payment is part of your own product logic and you would rather pay per transaction than share revenue.
See the facilitatorFrom an existing API to an agent-payable service
This is the gateway path, which is where most merchants start. It takes minutes and your own systems do not change.
- 1
Connect what you already run
Give the gateway your existing base URL and the auth it expects. Your key is encrypted at rest and injected upstream on every call, so it never reaches the buyer.
- 2
Price your routes
Add the paths you want to charge for and set a USDC price on each one. Metadata and health routes can stay free so agents can look before they buy.
- 3
Publish to the marketplace
Make the service public and it appears in the catalog agents search through the CLI, the MCP connector in Claude and ChatGPT, and the API.
- 4
Get paid per request
Each call settles in USDC on XDC in seconds, straight to your address, with the transaction hash on the record.
Prefer to see the mechanics first? How x402 payments work, or read the developer docs.
If an agent can describe what it wants, you can sell it
Anything an assistant might buy on someone's behalf works here, whether the unit is a booking, a lookup, a license, or an order.
Travel and stays
Agents plan and book on a traveler's behalf. Charge for a live availability search, then for the booking itself.
Tickets and events
Sell seats to an assistant that is arranging someone's evening, without putting it through a checkout built for human eyes.
Digital goods and licenses
Reports, datasets, templates, model access, a one-off license key. Delivered on payment, no account to create.
Food, delivery and local services
Let an agent place a real order against your live menu and prices instead of scraping a page and guessing.
Catalog, stock and pricing
Charge per lookup for live inventory and prices. It replaces the bulk feed nobody wants to negotiate and keeps the data fresh.
Quotes and bookable capacity
Price a quote, hold a slot, confirm a job. Each step is its own paid call with its own record.
You keep the customer, the keys, and the money
Selling through an agent channel should not mean handing over your business.
Non-custodial by design
Payments settle to an address you nominate. There is no balance of yours on our books and we cannot move your funds.
Your upstream key stays secret
Credentials for your own API are encrypted at rest and injected server-side. A buyer never sees them and cannot call around us.
Paid only on success
We verify the payment first, call your API, and settle only on a successful response. A failed call charges nobody.
Be the merchant an agent can actually pay.
Listing is free and takes minutes. Price one route, publish it, and see what an agent pays you for it.
Questions merchants ask
Do my buyers need an account here, or a crypto wallet?
Not with us. The agent pays, and whoever runs it needs USDC on the XDC network and nothing else: no account on this site, no card, and no gas to cover. That keeps the friction on the buying side close to zero, which is the point.
What does it cost to start selling?
Nothing to list and nothing monthly. On the gateway a 30% platform fee applies to each payment and the rest goes straight to your wallet. If you host the endpoint yourself and settle through the public facilitator, you keep the whole payment and draw down prepaid credits per confirmed settlement instead.
Do I have to change my API or my checkout?
No. The gateway sits in front of the service you already run and forwards each call with your own upstream credentials. Your code, your data, and your existing customers are untouched.
Can an agent get my product without paying?
No. The payment is verified before your API is called, and it is only settled once your API returns a success. If your upstream fails, nothing is charged and nothing moves.
What about refunds and disputes?
A settlement is final on-chain, so there are no chargebacks to defend. Refunds stay entirely yours: you send them from your own wallet, on your own terms, when you decide one is due.
How do agents find me?
A public service appears in the XDC AI marketplace, which agents reach through the CLI, the MCP connector in Claude and ChatGPT, and the public catalog API. They can search it by tags and capability, and see real usage on each listing.
Which path should I pick?
Start on the gateway. It is the shortest route to a working paid endpoint and you can move later. Reach for the public facilitator when the payment belongs inside your own application logic, or when you would rather pay per settlement than share revenue.
Where does the money actually land?
At an address you nominate, per payment, with the split handled on-chain. We are non-custodial by design: there is no balance of yours sitting on our books, and we cannot move your funds.