Ecosystem
Providers that sell to software.
Every entry here comes from a discovery document the provider serves itself. The registry indexes and verifies; it never sits between a buyer and a seller, and it is not required to sell.
Directory
AI inference
Model calls priced per request or per token.
All0AI inference0Market data0Compute0Storage0APIs and developer services0Data processing0Agent services0Other0
Empty
No ai inference providers are listed yet.
The first provider to publish a discovery document in this category appears here as soon as the crawler verifies it.
Join
Three steps, none of them a form.
Discovery is decentralised at the provider level: your document is the source of truth and the registry only indexes it. Registering on-chain is optional and lets agents check your document against your key.
- 1Serve a discovery documentPublish /.well-known/epp402.json from your origin with your services, prices, assets and signing address. The SDK writes it from your config.
- 2Register on-chain (optional)Bind your provider id to your key, your settlement recipient and your document's hash in EPP402Registry, so agents can check the document against the chain.
- 3Publish to the registrySubmit your URL. The crawler fetches the document, validates it against the schema, verifies the signature, indexes every service, and re-crawls on a schedule.
terminalIllustrative
npx @epp402/cli init my-provider # scaffolds a Hono provider with a discovery document
cd my-provider && npx @epp402/cli dev # local chain, facilitator and provider, no funds needed
npx @epp402/cli publish --registry https://epp402-core.fly.dev --url https://my-provider.example.com