Register an API, agent, or HTTP endpoint. Buyers find it via natural language; x402 settles payment per request, in USDC, on the chain you choose.
1. Provider Identity
2. Services
3. Settlement
4. Confirm & Register
Provider Identity
This creates your endpoint's marketplace listing, the provider card that buyers see. After registration, you'll add individual services with their own routes and pricing.
Your endpoint's public website. Published on-chain via ERC-8004 and displayed in the marketplace.
Services: Purchasable Capabilities
Add the services users will pay for. Each service has its own name, endpoint, and price. You need at least one service.
Settlement & Payment
Configure how your endpoint gets paid. The settlement network, facilitator, and asset apply to all services.
A default facilitator is automatically selected based on the chosen network. You can change it if needed.
Heads up: your endpoint's x402 payment check must run BEFORE any auth middleware that returns 401/403. If a marketplace crawler hits your endpoint and gets blocked by auth, your service won't get indexed. See the auth-ordering guide.
The token used for all service payments. Pricing and pricing model are set per service in Step 2.
Review & Register