Skip to content
TAONIC
Ask TAONIC

01 / 14IN DEVELOPMENTLive parts and proposed parts, each tagged

Introduction

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.

One request, end to end

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

VERIFIED

  1. 01Question
  2. 02Capability
  3. 03Route
  4. 04Provider
  5. 05Answer
  6. 06Record
The request path, step by step
StepWhat happens
QuestionYou ask once, in plain language.
CapabilityTAONIC reads what kind of work the question needs.
RouteIt picks an available route for that work, with a fallback.
ProviderA provider or Bittensor subnet does the work.
AnswerThe result comes back with its provenance.
RecordThe request, its route and its cost are recorded.

What runs today

This table was written on 25 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.

Components that run today
ComponentStateEvidence
Intelligence gatewayVERIFIEDPOST /api/intelligence validates, plans, routes and answers. Production request 30e55018 answered on 2026-09-24.
Text answers, OpenRouter to Chutes (subnet 64)CONNECTEDAnswered in production; OpenRouter reported Chutes as the serving provider.
Event forecasts, Numinous (subnet 6)CONNECTEDEight named miners’ forecasts returned in production, each with uid and hotkey.
Search, price forecasts, images, speech, embeddings, engyCONFIGURATION REQUIREDAdapters exist and follow each provider’s documentation. No credential is set, so nothing is sent.
Durable request recordsVERIFIEDEvery served request is recorded in a Cloudflare D1 database; totals are public at /api/accounting.
Provider spending guardVERIFIEDA daily ceiling on TAONIC’s own provider spend, booked before each paid call. Fails closed.
Accounts and sign-inOFFBuilt and proven once in production, then switched off.
ChargingOFFNobody is charged. Charge and revenue are real zeros.

In development

Paid intelligence activity may create eligible surplus that can be used to accumulate TAO and fund better capabilities.

PROPOSED

  1. 01Paid requests
  2. 02Provider cost deducted
  3. 03Eligible surplus
  4. 04TAO reserve growth
  5. 05Better capabilities

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 loop is in 02 Product mechanism, the reserve in 07 TAO reserve policy, the token in 08 and the market in 09.

What TAONIC is not

  • 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.
  • 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.

How to read these pages

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. 02Product mechanismOne request from question to record, and the loop it is meant to start.
  2. 03Intelligence routingHow a question becomes a capability, a route and a fallback.
  3. 04Providers and subnet evidenceEach route, its subnet, its state, its terms and its evidence.
  4. 05Activity and accountingWhat every request records, what it cost TAONIC, and where to read it.
  5. 06Pricing and charging statusThe proposed price, the charging foundation, and why charging is off.
  6. 07TAO reserve policyReserve growth, the surplus allocation, and how TAO would be bought.
  7. 08Proposed TAON tokenWhy TAON would exist, its fixed supply, and what holding it does not give.
  8. 09Proposed direct-v4 launchA TAON / TAO Uniswap v4 pool with an eligible-swap fee under a 2% ceiling.
  9. 10Governance and securityWhat protects the gateway now, and what a financial layer would require.
  10. 11Risks and limitationsWhere a question goes, what is kept, and what can go wrong.
  11. 12Deployment statusEvery deployed and undeployed component, with addresses and evidence.
  12. 13API and referenceEvery public endpoint, with schemas, limits and failure states.
  13. 14ChangelogWhat changed, when, and what each state word means.

Every state on this page matches Status. Where they ever differ, Status is right and this page is a defect.