Discovering BlockRun through x402scan and the Bazaar
BlockRun's endpoints are registered on x402scan and discoverable via the x402 Bazaar conventions: an OpenAPI document with x402 extensions plus a /.well-known/x402 manifest.
How it works
x402scan indexes sellers by reading their OpenAPI document first and the /.well-known/x402 manifest as a fallback; the Bazaar conventions add input schemas on paid POST operations so an agent can construct a valid request from the listing alone. BlockRun publishes both, derived from the same route table, with free operations marked so a strict-mode probe does not mistake them for paid.
Every paid BlockRun endpoint that a listing can cleanly probe is registered; the few templated poll routes are served but excluded from registration because a literal probe of a placeholder id has no real job behind it.
Behind it is the BlockRun catalog: 78 chat models plus image, video, music and speech generation, search, market data and multi-chain RPC, priced per call. 6 open-weight models are free and need no wallet.
Setup
1. What an indexer reads
curl https://blockrun.ai/openapi.json
curl https://blockrun.ai/.well-known/x402Questions
- Can an agent construct a request from the listing?
- Yes for the paid POST routes: the OpenAPI document carries request schemas and examples for them.
- Why are some routes missing from the listing?
- Templated poll routes are excluded from registration because a literal probe has no job to poll; they still work at runtime.