HTTP 402 Payment Required
ORD/x402 — pay-per-call, in native sats
The first working x402 facilitator on Bitcoin SV. Agents pay per API call in native satoshis — sub-cent micropayments, settled on ORDnet's own node. No accounts, no API keys, no subscriptions.
How it works
Standard x402 flow — your agent needs no account and no pre-shared key. If your client speaks x402, it already speaks ORD/x402.
An agent calls a paid endpoint. With no payment attached, the server answers HTTP 402 plus a Base64 PAYMENT-REQUIRED header describing price, network and a fresh per-invoice payTo address.
The client pays the quoted amount in native sats to the invoice address (with the invoice id as an OP_RETURN hint). ORDnet's MCP can do this in one call via ordnet_x402_fetch.
The client repeats the request with an X-PAYMENT header carrying the txid. The facilitator verifies the payment against its own node and index, then settles.
The resource is returned with a signed receipt in X-PAYMENT-RESPONSE. Each invoice unlocks exactly once — replays are rejected.
Live paid endpoints 2 demos
Real, payable right now. Point any x402 client at them, or use ORDnet's MCP ordnet_x402_fetch.
GET /paid/echo 10 sats
Echo service — returns your query, proves the 402 flow end-to-end.
curl -i https://x402.ordnet.io/paid/echo?msg=hello
GET /paid/chaininfo 25 sats
Live BSV chain info straight from ORDnet's own node.
ordnet_x402_fetch({
url: "https://x402.ordnet.io/paid/chaininfo",
maxSats: 50
})Facilitator API
x402 V2 facilitator interface. Sellers can run their own paywall and point it here; the schemas match the x402 V2 spec field-for-field on the exact scheme, network bsv.
POST /verify
Dry-run: validate a payment payload against payment requirements without broadcasting. Returns { isValid, invalidReason?, payer? }.
POST /settle
Verify, broadcast via ORDnet's own node, register against replay, and return a settlement response with the txid.
GET /health
Service status, network, and running totals (invoices, settlements, sats settled).
Discovery
A Bazaar-compatible catalog of paid resources, so agent discovery layers can find and price ORDnet endpoints automatically.
GET /discovery/resources
Returns each paid resource with its x402 version and accepted payment terms (scheme, network, amount).
curl https://x402.ordnet.io/discovery/resources
Why ORDnet's facilitator
What sets ORD/x402 apart from hosted facilitators built on stablecoins and rented infrastructure.
- Native-sat settlement. Payments settle in BSV satoshis on ORDnet's own node — no stablecoin, no bridge, no third-party facilitator in the path.
- True sub-cent micropayments. BSV fees make a 10-sat call economical, where USDC-on-Base style rails bottom out around a tenth of a cent.
- Own-node verification. Every payment is confirmed against ORDnet's own node and node-verified UTXO index — not a remote explorer.
- No hot wallet. The facilitator holds only a master public key and derives a unique per-invoice address for every payment; the private key never touches the server.
- x402 V2 compatible. Standard PaymentRequirements, PaymentPayload and settlement schemas — existing x402 clients work unchanged.