bittensor.com valid
Automatically discovered from public files. Ownership management is optional. Inclusion does not imply endorsement or publisher participation.
Manage this listing — optional · Visit publisher ↗
What verification unlocks
See how your site is discovered—and control what agents see.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for bittensor.com:
1. POST https://agentwebmap.com/v1/sites/bittensor.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://bittensor.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/bittensor.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/bittensor.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory. Ownership management is optional.
Bittensor
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-22T06:29:57.919Z. Cached copy · Source on bittensor.com
# Bittensor
## Searching these docs
Every docs link in this file is already raw markdown. Fetch it directly;
do not scrape HTML. Grep the corpus as if it were local:
- This index: `https://www.bittensor.com/llms.txt`
- Full corpus (for `rg`, not for stuffing into context): `curl -s https://www.bittensor.com/llms-full.txt | rg -n '<pattern>'`
- One page: https://www.bittensor.com/llms.mdx/docs/<slug>/content.md
- JSON catalogs: https://www.bittensor.com/catalog/intents.json, https://www.bittensor.com/catalog/reads.json, https://www.bittensor.com/catalog/errors.json
(each entry has `markdown_url` for prose and, where known, `sources`/`hits` with `raw_url`)
- Chain source search: `curl -s 'https://www.bittensor.com/code/search.json?q=<literal>'`
- Chain source by path: `curl -s https://www.bittensor.com/code/index.json` then `curl -s https://www.bittensor.com/code/raw/<repo-path>`
- Clone for heavy exploration (docs in docs/): `git clone --depth 1 https://github.com/RaoFoundation/subtensor`
## Reference catalogs
Per-op and per-query pages are omitted here (they dominate the tree).
Prefer the JSON catalogs; each entry carries `markdown_url` (raw prose),
`docs_url` (HTML), and often `sources` / `hits` with `raw_url` into `/code`.
- Transactions: https://www.bittensor.com/catalog/intents.json
- Queries: https://www.bittensor.com/catalog/reads.json
- Errors: https://www.bittensor.com/catalog/errors.json — semantic codes under `.codes`, chain names under `.chain_errors` (see `.note`)
- Hyperparameters landing: https://www.bittensor.com/llms.mdx/docs/hyperparameters/content.md
- Full prose dump: https://www.bittensor.com/llms-full.txt
- [Bittensor Documentation](https://www.bittensor.com/llms.mdx/docs/content.md): Do anything on the Bittensor chain with the Bittensor SDK and CLI.
- [Quickstart](https://www.bittensor.com/llms.mdx/docs/quickstart/content.md): Install, connect, read chain state, and submit your first transaction.
- [The SDK](https://www.bittensor.com/llms.mdx/docs/sdk/content.md): The five core primitives — Subtensor, Wallet, Balance, intents, and results — and their one-line constructors.
- [For agents](https://www.bittensor.com/llms.mdx/docs/agents/content.md): How an agent discovers, previews, and safely executes any Bittensor operation.
- [The CLI](https://www.bittensor.com/llms.mdx/docs/cli/content.md): Configuration, global options, generated commands, and non-interactive use.
- Concepts
- [The network](https://www.bittensor.com/llms.mdx/docs/concepts/network/content.md): Subnets, miners, validators, stakers, TAO and alpha, emissions, and epochs.
- [Emissions](https://www.bittensor.com/llms.mdx/docs/concepts/emissions/content.md): TAO and alpha issuance, halvings, subnet emission shares, the per-tempo split, and Yuma Consensus.
- [Emission weights](https://www.bittensor.com/llms.mdx/docs/concepts/emission-weights/content.md): How a subnet owner divides alpha emission between owner, validators and miners, and how root TAO
…
Help agents understand your site
Optionally manage your description, publish terms for agents, review file health, measured discovery requests, publisher clicks and score history. Confirm domain control in your browser using a fresh token in your llms.txt, DNS, meta tag or well-known file. No backlink is required.
Manage this listing → · Agent and API instructions
Machine-readable: GET /v1/resolve?q=bittensor.com · GET /v1/domain/bittensor.com · this page as Accept: application/json or text/markdown · MCP lookup_domain