For providers
How your Bittensor service gets listed here, and how it moves up to "Endpoint verified". There is nothing to sign up for: bittensor.market reads what you publish on chain.
We only point agents to you
1. Publish a service document
Host a JSON document (format version 1) at a public https URL. Every field is optional except the version, and unknown fields are ignored. Serve it with Access-Control-Allow-Origin: * so web apps can read it too.
{
"version": 1,
"name": "My Service",
"description": "What it does, in one or two sentences.",
"publishers": [{ "netuid": 1, "hotkey": "<your service hotkey ss58>" }],
"services": [
{
"type": "openapi",
"endpoint": "https://api.example.com",
"spec": "https://api.example.com/openapi.json"
}
],
"payments": [{ "type": "gamma", "max_spend": "2" }, { "type": "x402" }]
}services:openapi(endpoint plus optional spec) ormcp(endpoint).payments:gamma(optionalmax_spendas a decimal string, optionalsignature, e.g. "btauth/1") orx402. We show these as your claims; prices stay with you.
2. Register it on chain
A service record links a hotkey on a subnet to your document URL (at most 256 bytes). The hotkey needs a validator permit on the subnet, or must be the subnet owner's hotkey. An empty URL removes the record.
btcli tx set-service --netuid <netuid> --url https://example.com/services.json --dry-run
# when the dry run looks right, submit it (signed by your coldkey):
btcli tx set-service --netuid <netuid> --url https://example.com/services.json -w <your_coldkey>Details and the Python SDK variant: Bittensor docs – Services (opens the provider's site in a new tab).
3. What we check
| Service document | HTTPS, public address, HTTP 200 without redirects, within 5 s, at most 256 KiB, Content-Type application/json |
|---|---|
| Endpoint | One request per sync; only the status line is read. Any answer below HTTP 500 counts as reachable (authentication is fine) |
| OpenAPI description | One download per sync, at most 2 MiB, JSON or YAML, OpenAPI 3.x or Swagger 2.0 with "info" and "paths". Validated, never executed |
Checks run with every sync (about every 30 minutes). A single failure changes nothing. Your listing page shows what we found and how to fix it.
Common problems we have seen
The registered URL points to a web page or a Markdown guide
Register the URL of the JSON document itself. Two of the first seven records on finney returned HTML or Markdown.
No OpenAPI "spec" link
Without a spec, a listing cannot become Endpoint verified. Add "spec" to the endpoint.
Hotkey missing from "publishers"
If you include "publishers", list the exact netuid and hotkey of the record, or readers ignore the document.
Find your listing via Subnets.