Publish an endpoint. Get found by machines.
Listing pushes your price and input schema to the x402 Bazaar, where an agent that has never met you can discover the service, construct a valid request and pay for it — with no signup, no sales call and no key.
Discovered through the Bazaar — no signup, no sales call, no API key issued.
What it does
The schema is the documentation
A published input schema is what lets a caller build a correct request unaided. It is the single biggest driver of whether machines can use you.
Ranked on behaviour
Success rate, latency at p50 and p95, price against comparable endpoints, and settled volume. Placement is not for sale.
Earn on every call
Settlement is direct to your address per request. No payout run, no minimum threshold, no waiting on a cycle.
Private when it should be
A private endpoint still takes x402 payments but never enters the index — useful for metered billing between internal teams.
Discovery without a relationship
Every other API marketplace assumes a human evaluates, signs up and integrates. Here the evaluation is a schema read and the signup does not exist, so an agent can go from needing a capability to having paid for it inside a single task.
Questions
- How do I price something new?
- Start flat — it is easy to reason about and easy for a caller to budget against. Move to metered once your own receipts show where the cost actually lands.
- What stops a bad endpoint listing itself?
- Nothing stops the listing; ranking is what reflects reality. Callers should still set a maxPrice and validate responses — listing is not endorsement.
- Can I change the price later?
- Yes, and quotes already issued are honoured until they expire. Breaking an input schema needs a new version instead.