Bittensor website screenshot

Bittensor

Bittensor is an open, decentralized machine-intelligence network built on a Substrate blockchain (subtensor). Contributors earn the TAO token by supplying useful work to specialized subnets — miners produce, validators score, and stakers back them — with emissions distributed by Yuma Consensus. Developers do not consume a hosted REST API; they interact with the chain through the official lean Python SDK (import bittensor) and the btcli command line, which together perform every user-facing operation: wallets and keys, staking and pools, subnet creation, mining, validating, weights, proxies, multisig, and an EVM layer. The developer surface is agent-native: machine-readable catalogs of write intents, chain reads, and errors are published for discovery, with a plan/execute model, Policy guardrails, and typed results.

Bittensor is listed with 1 API on the APIs.io network. Tagged areas include Company, Artificial Intelligence, Blockchain, Decentralized AI, and Machine Learning.

Bittensor’s developer surface includes documentation, getting-started guide, API reference, engineering blog, CLI, authentication, and 16 more developer resources.

21.9/100 emerging ▬ flat Agent 8/100 agent aware Front door AI 3/6 light library Full breakdown ↓
scored 2026-10-09 · rubric v0.23.0
1 API
CompanyArtificial IntelligenceBlockchainDecentralized AIMachine LearningCryptocurrencyWeb3SDKCLIDePIN

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-10-09 · rubric v0.23.0
Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/bittensor: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Bittensor Chain SDK & CLI

The unified Bittensor v11 package — a lean Python SDK (import bittensor) plus the btcli command line — for every operation on the subtensor Substrate chain: reading chain state ...

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Bittensor Authentication

substrate-keypair-signature · 0 schemes

SECURITY

Bittensor Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Bittensor Agentic Access

73 operations · 73 acting

73 operations · 73 acting

AGENTIC

Resources

Get Started 2

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Build 4

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Company 2

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: bittensor
name: Bittensor
description: 'Bittensor is an open, decentralized machine-intelligence network built on a Substrate blockchain (subtensor).
  Contributors earn the TAO token by supplying useful work to specialized subnets — miners produce, validators score, and
  stakers back them — with emissions distributed by Yuma Consensus. Developers do not consume a hosted REST API; they interact
  with the chain through the official lean Python SDK (import bittensor) and the btcli command line, which together perform
  every user-facing operation: wallets and keys, staking and pools, subnet creation, mining, validating, weights, proxies,
  multisig, and an EVM layer. The developer surface is agent-native: machine-readable catalogs of write intents, chain reads,
  and errors are published for discovery, with a plan/execute model, Policy guardrails, and typed results.'
url: https://raw.githubusercontent.com/api-evangelist/bittensor/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- polychain
x-tier: stub
x-tier-reason: portfolio-lead
deliveryModel:
  model: library
  open_source: false
  commercial: false
  callable_host: false
  label: Library · distributed through package registries, no callable service
  confidence: low
  source:
  - none
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-18'
image: https://github.com/opentensor.png
tags:
- Company
- Artificial Intelligence
- Blockchain
- Decentralized AI
- Machine Learning
- Cryptocurrency
- Web3
- SDK
- CLI
- DePIN
tags_raw:
- Company
- Ai
- Blockchain
- Decentralized AI
- Machine Learning
- Cryptocurrency
- Web3
- SDK
- CLI
- DePIN
- Machine-Learning
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- name: Bittensor Chain SDK & CLI
  description: 'The unified Bittensor v11 package — a lean Python SDK (import bittensor) plus the btcli command line — for
    every operation on the subtensor Substrate chain: reading chain state and submitting state-changing transactions (staking,
    registration, weights, subnets, proxies, multisig) against a mainnet or testnet RPC entrypoint.'
  humanURL: https://www.bittensor.com/docs
  baseURL: wss://entrypoint-finney.opentensor.ai:443
  properties:
  - type: Documentation
    url: https://www.bittensor.com/docs
  - type: GettingStarted
    url: https://www.bittensor.com/docs/quickstart
  - type: APIReference
    url: https://www.bittensor.com/docs/tx
  - type: LLMsTxt
    url: llms/bittensor-llms.txt
  - type: ErrorCatalog
    url: errors/bittensor-error-codes.yml
  - type: X-MCPServerCandidate
    url: mcp/bittensor-mcp.yml
    note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list
      derived from the published API contracts, not an existing server. The scorer already read the manifest and reported
      mcp_server correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
  - type: Packages
    url: packages/bittensor-packages.yml
  - type: SDKs
    url: packages/bittensor-packages.yml
  - type: CLI
    url: cli/bittensor-cli.yml
  - type: Authentication
    url: authentication/bittensor-authentication.yml
  - type: Conventions
    url: conventions/bittensor-conventions.yml
  - type: Lifecycle
    url: lifecycle/bittensor-lifecycle.yml
  - type: Conformance
    url: conformance/bittensor-conformance.yml
  - type: DataModel
    url: data-model/bittensor-data-model.yml
  - type: AgenticAccess
    url: agentic-access/bittensor-agentic-access.yml
  - type: AgentSkill
    url: skills/_index.yml
common:
- type: Website
  url: https://bittensor.com
- type: DeveloperPortal
  url: https://www.bittensor.com/docs
- type: Documentation
  url: https://www.bittensor.com/docs
- type: GettingStarted
  url: https://www.bittensor.com/docs/quickstart
- type: APIReference
  url: https://www.bittensor.com/docs/tx
- type: GitHubOrganization
  url: https://github.com/opentensor
- type: Blog
  url: https://www.bittensor.com/releases
- type: SDKs
  url: packages/bittensor-packages.yml
- type: Packages
  url: packages/bittensor-packages.yml
- type: CLI
  url: cli/bittensor-cli.yml
- type: X-MCPServerCandidate
  url: mcp/bittensor-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: LLMsTxt
  url: llms/bittensor-llms.txt
- type: ErrorCatalog
  url: errors/bittensor-error-codes.yml
- type: Authentication
  url: authentication/bittensor-authentication.yml
- type: Conventions
  url: conventions/bittensor-conventions.yml
- type: Lifecycle
  url: lifecycle/bittensor-lifecycle.yml
- type: Conformance
  url: conformance/bittensor-conformance.yml
- type: WellKnown
  url: well-known/bittensor-well-known.yml
- type: DomainSecurity
  url: security/bittensor-domain-security.yml
- type: DataModel
  url: data-model/bittensor-data-model.yml
- type: AgenticAccess
  url: agentic-access/bittensor-agentic-access.yml
- type: AgentSkill
  url: skills/_index.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/bittensor"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/bittensor/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/bittensor/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.