Start here

TAONIC routes intelligence across specialized providers and Bittensor subnets.

You ask once. TAONIC works out what kind of work the question needs, sends it to a route that does that work (a provider, or a service running on a Bittensor subnet), and returns the answer with a record of where it went, how long it took and what it cost TAONIC. These pages explain each part, then the public API, then the economic layer that is still in development.

Every question takes the same path. Each step is live today.

This table is a record, last checked on 30 September 2026 (UTC), and is not live. The live state of every component is on Status; if this table and Status ever disagree, Status is right.

The recommended path is product first, token later. Paid routing comes first; a token is reconsidered only if published conditions hold. The loop that paid usage could start is drawn, separately from the routing, in 11 Economic proposal. Charging is not enabled, so there is no paid usage, no surplus and no TAO accumulation today. Every value in this flow is a real zero.

The reserve is in 12, the token in 13 and the market in 14.

• Not a Bittensor subnet. It runs no miner or validator and earns no emissions.
• Not a clone of any one provider. Each provider is one route among several.
• Not a generic wrapper around one model: the route is chosen per question, with a fallback where a second connected route exists.
• Not a deployed financial protocol.
• Not an official Bittensor product, and not an official Robinhood product.
• Not a partner of any provider it routes to. TAONIC uses public APIs as a customer; no partnership, endorsement or allocation has been agreed with anyone.

Each section is classified at the top: ✓VERIFIED describes what runs today, ◇IN DEVELOPMENT mixes live parts and proposed parts with each one tagged, and ◇PROPOSED is a design only. Values are exact where they exist; where one does not exist, the page says so rather than showing an example figure.

Contents

1. 02What TAONIC doesOne job: route a request to the right Bittensor service and hand back a record.
2. 03Route a requestAsk in the browser or call the endpoint. What is sent, what comes back, what fails.
3. 04CapabilitiesThe seven kinds of work you can ask for, and which routes serve each.
4. 05Route selectionHow a question becomes a capability, a selected route and a fallback.
5. 06ReceiptsWhat every request records, what it cost TAONIC, and where to read it.
6. 07Pricing and accountsPARTLY PROPOSEDCharging is off. The proposed price, the accounts foundation, and why neither is on.
7. 08Provider integrationEach route, its subnet, its terms and its evidence, and what adding a provider takes.
8. 09Service intentsPROPOSEDA proposed machine-readable layer: discover, preview and run a route under a spending policy.
9. 10ArchitectureThe gateway, the router, the ledger, and every public endpoint with its limits.
10. 11Economic proposalPROPOSEDProduct first, token later: the recommended path, one separate loop, and what must come first.
11. 12TAO reserve proposalPROPOSEDHow eligible surplus could become a published TAO reserve. No reserve exists.
12. 13TAON token proposalPROPOSEDWhy a token is not recommended now, and what a gated design would look like.
13. 14v4 launch proposalPROPOSEDA TAON / TAO Uniswap v4 pool and fee hook, studied and gated. Nothing is deployed.
14. 15Governance proposalPARTLY PROPOSEDWho could change what, with what notice, and what protects the gateway today.
15. 16RisksPARTLY PROPOSEDWhere a question goes, what is kept, and what can go wrong in the product and in the proposal.
16. 17StatusPARTLY PROPOSEDEvery deployed and undeployed component, with addresses and evidence.
17. 18GlossaryPARTLY PROPOSEDThe words used here, the state words, and what changed and when.
18. 19Mechanism and sourcesPARTLY PROPOSEDThe proposed mechanism in four steps, the five accounting classes, the contracts status and the source register with every claim classified.