Neuronto Payments: x402 facilitator and API gateway
RemoteAbout Neuronto Payments: x402 facilitator and API gateway
Neuronto Payments provides x402 examples and a facilitator for charging HTTP routes and paying for API access. Its starters cover Node, Next.js, and Python stacks, with USDC settlement on Base.
Key features
- 01Require x402 payment for an HTTP route
- 02Verify signatures and broadcast on-chain settlement
- 03Examples for Express, Hono, Next.js, and FastAPI
- 04Pay 402 requests from scripts or agents
- 05Check currently supported networks, schemes, and versions
- 06Test end to end with an automatically refunded merchant
Use cases
- 01Charge per request on an API endpoint
- 02Call a paid API from a script or agent
- 03Test an x402 payment flow with the echo merchant
- 04Check which networks the facilitator can settle
MCP support
The project does not state a relationship to MCP.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://pay.neuronto.com/mcpclaude mcp add --transport http com-neuronto-x402-payments-facilitator https://pay.neuronto.com/mcp{"mcpServers":{"com-neuronto-x402-payments-facilitator":{"type":"http","url":"https://pay.neuronto.com/mcp"}}}Open in Cursor{"servers":{"com-neuronto-x402-payments-facilitator":{"type":"http","url":"https://pay.neuronto.com/mcp"}}}Open in VS Code{"mcpServers":{"com-neuronto-x402-payments-facilitator":{"type":"http","url":"https://pay.neuronto.com/mcp"}}}{"mcpServers":{"com-neuronto-x402-payments-facilitator":{"serverUrl":"https://pay.neuronto.com/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
6This tool takes no parameters.
Details
From the project READMEx402 starters
The shortest working way to charge for an HTTP route, and to pay for one, using the official x402 SDKs. Every file here runs as it is; the only thing you must change is the wallet that gets paid.
x402 revives HTTP 402 Payment Required. Your server answers an unpaid request with 402 and
machine-readable terms, the client signs a stablecoin payment, and a facilitator verifies the
signature and settles it on-chain. Your server never holds a key and never talks to a chain.
Pick one
| Folder | Stack | What it is |
|---|---|---|
express | Node, Express | One paid GET /premium route |
hono | Node, Hono | The same route on Hono |
next | Next.js App Router | A paid API route |
fastapi | Python, FastAPI | The same route in Python |
client | Node and Python | Paying for a 402 route from a script or an agent |
Run one in a minute
cd express
npm install
export MERCHANT=0xYourWalletAddress # where the money goes, on Base
npm start
curl -i localhost:3000/premium # 402 with terms
Then pay it with a client from client, or point any x402 client at it.
The facilitator
These starters use https://pay.neuronto.com as the facilitator: the service that verifies the payer's
signature and broadcasts the settlement. It is one line in every file, and any x402 facilitator
can take its place:
new HTTPFacilitatorClient({ url: "https://pay.neuronto.com" })
Base mainnet (eip155:8453) is live there. GET https://pay.neuronto.com/supported lists every network,
scheme and version it settles right now; a network that cannot settle disappears from that list
before it starts refusing, so a server that reads /supported never advertises a price it
cannot take.
Testing without spending anything
https://pay.neuronto.com/echo is a live merchant that charges $0.001 and sends it straight back in the
same request, so a client can be run end to end for the cost of nothing:
curl -i https://pay.neuronto.com/echo # a real 402, with real terms
Point any of the clients in client at that URL. The refund is automatic; the gas is
not yours.
What you need
- A wallet address to be paid to. Nothing is installed on your side to receive money: payments
arrive as USDC transfers to the address you put in
MERCHANT. - For a paying client, a funded key. Never put a real key in a file: every example here reads it from the environment.
Licence
Apache-2.0.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.