Skip to main content
Rail402 turns any HTTP endpoint into a paid resource on Stellar. A buyer sees the price, pays per request, and gets access, with no checkout page, no API key, and no account. The buyer is usually an agent. Rail402 settles the payment, catalogs the paid service into a searchable Bazaar, and lets agents discover and pay for services they have never seen before. It runs on stellar:testnet today at facilitator.rail402.dev, free and with no API key.

​
Why Stellar

A settlement costs a fraction of a cent, so a per-request micropayment is worth settling even when the amount is tiny. USDC and other stablecoins are reachable from Soroban through the Stellar Asset Contract, and the facilitator sponsors the network fee, so a buyer needs only the payment asset and no XLM.

​
What Rail402 gives you

Facilitator

verify, settle, and supported for the exact and upto schemes. Sponsored fees, non-custodial settlement, any SEP-41 asset.

Bazaar

A catalog and natural-language search over paid services. A resource is listed automatically when its first payment settles. No registration step.

SDK, CLI, and MCP

One SDK for buyers and sellers, a rail402 command-line tool, and an MCP server so an agent can discover and pay from inside its runtime.

​
Choose your path

Buyers and agents

Discover a service and pay for it per request, from code, the terminal, or an agent runtime.

Sellers

Put a paid, x402-protected endpoint online and make it discoverable in the Bazaar.

Operators

Run the facilitator, hosted for others or self-hosted for your own services.
New to x402 on Stellar? Read How Rail402 works first. It defines the payment loop, the exact and upto schemes, and the four addresses in play, in one page.

​
Install and search in one minute

Every package is published under the @rail402.dev scope. The SDK is the front door for buyers and sellers. Search needs no account; paying needs a funded testnet account (see the buyer quickstart).
See Install and first payment for the full five-minute walkthrough, or the Packages reference for the map of every package and which to use.

​
What the facilitator advertises

The /supported endpoint is the ground truth for what a facilitator can do. This is the live response from facilitator.rail402.dev:
areFeesSponsored: true means the buyer needs no XLM. The bazaar extension means the facilitator catalogs the services it settles. The upto kind carries the on-chain contract that enforces the metered scheme.

​
Built for interoperability

Rail402 builds verify and settle on the Apache-2.0 @x402/stellar package and speaks the x402 v2 wire format. A stock x402 client pays a Rail402 endpoint with no Rail402-specific code, and reads the Bazaar through the same interface it uses for any facilitator. The @rail402.dev helpers add convenience on top. You never have to use them to interoperate.

​
See it live

The Explorer shows x402 payments settled on Stellar across facilitators, not only Rail402’s, with the facilitator that settled each one. It is the fastest way to watch a payment you just made land on chain.