I want to sell DApp/MCP services#
This page demonstrates the fastest integration path for HTTP Sellers via One-time payment — drop middleware onto an existing HTTP service and enable pay-per-call in a few lines of code.
Want the full integration (including Batch and Pay-as-you-go)? Jump to Payment Methods.
Pick your integration path#
Two paths, identical business outcome — the difference is whether you "let AI write it for you" or "call the SDK yourself".
FAQ#
If a Buyer doesn't pay, will my resources be wasted?
No. The SDK intercepts unpaid requests and returns HTTP 402 immediately, never entering business logic. Only requests whose signatures pass verification trigger resource delivery.
Do I need to run my own node?
No. The Broker handles all on-chain interactions (RPC connections, gas management, transaction submission) on your behalf. You only need a recipient address.
Why isn't KYC / merchant onboarding required?
The x402 protocol inherently requires no registration — the payer's identity is determined by an on-chain signature (EIP-3009) and cannot be forged. Onchain OS performs transaction-level compliance screening at the Broker layer via KYT (see Core Concepts · KYT), keeping anonymity while filtering illicit funds.