Skip to content
TAONIC
Ask TAONIC

How TAONIC works

Send a request. A subnet does the work. You get a receipt.

TAONIC is a gateway that sends each request to a Bittensor subnet able to do the job, returns the answer, and shows you which route did it and what it cost.

  • Port
  • Text generationREADING
  • Text generationREADING
  • Text generationREADING
  • Web searchREADING
  • Event forecastsREADING
  • Price forecastsREADING
  • Image generationREADING
  • Text to speechREADING
  • Speech to textREADING
  • EmbeddingsREADING

… of 10 routes connected

Free today · charging OFF · no token

Subnet field, 10 routes around one port. Route states are being read.

Three words, one sentence each

TAONIC
A gateway. You send a request; TAONIC picks a connected route that does that kind of work, waits for the answer, and returns it with a receipt of the route, the time and the reported cost. TAONIC is a customer of the services it routes to, and runs no part of the network itself.
Bittensor
An open network where independent operators run AI services and are paid in its token, TAO, under rules each subnet sets. TAONIC is not a Bittensor subnet and holds no validator, miner or emissions role.
A subnet
One service on that network, with its own number, operators and rules. Of the routes TAONIC has used, Chutes (subnet 64) serves text generation, and Numinous (subnet 6) serves event forecasts.

One request, six stages

Every request takes the same path. The violet line is the request; the graphite plates are the stages the gateway records.

  1. 01

    Question

    You ask once, in plain language.

  2. 02

    Intent

    TAONIC reads what kind of work the question needs.

  3. 03

    Route

    Only connected routes that do that kind of work are eligible. Declared rules pick one, with a fallback where a second connected route exists. Routes without a key are shown, never used.

  4. 04

    Execution

    The request goes to that route: a provider whose service runs on a Bittensor subnet. TAONIC waits, and you can cancel.

  5. 05

    Answer

    The result comes back with its provenance.

  6. 06

    Receipt

    The route, the time and the reported cost are written to a record. TAONIC’s records hold the request, its route and its cost, never the question or the answer.

What runs today

Routing plane, ten routes. Route states are being read.

Request port

  1. ChutesREADING
  2. EngyREADING
  3. OpenRouter to ChutesREADING
  4. DesearchREADING
  5. NuminousREADING
  6. SynthREADING
  7. Chutes imageREADING
  8. Chutes speechREADING
  9. Chutes transcribeREADING
  10. Chutes embedREADING
Route states: ….

What you can do now

  • Ask a question and receive a routed answer
  • See which provider and subnet answered, and how long it took
  • Inspect every route and its state
  • Read the request and cost accounting
  • Read the evidence for every component on Status
  • Read the documentation, including the proposed economic design

A route is connected only once a real request has completed through it. A route with an adapter and no key is shown on the plane and never used.

What is not real yet

Proposed · Not operating

0 of 8 token gates passed

Charging is not enabled yet, so customer charge, revenue and eligible surplus are real zeros. No TAO has been acquired, because no system that could acquire it exists. The TAON token is proposed and NOT DEPLOYED. A token would be reconsidered only if all 8 published gates pass at the same time, and passing them authorises an owner decision, never a deployment.

A healthy chain, bridged TAO and Uniswap v4 infrastructure are external facts. None of them means a TAONIC contract is deployed.

  • Charging is OFF
  • Customer revenue is $0
  • TAON NOT DEPLOYED
  • TAO reserve NOT DEPLOYED
  • No public audit
  • Token not yet justified
  • Economic model PROPOSED, NOT RUNNING

Pricing · PROPOSED · CHARGING IS OFF · NOT LIVE

Free today, within daily limits. These are the prices proposed for a trial when paid use opens; a request that fails would cost nothing.

What a receipt proves

TAONIC receiptWritten by TAONIC · unsigned record

It proves

  • Which route and subnet answered, as the gateway recorded it.
  • How long it took, from your request to the answer.
  • What the work cost TAONIC, with its class: reported by the provider, calculated from a published rate, or unknown.
  • What you were charged: nothing, while charging is OFF.
  • That the request was booked in TAONIC’s durable records under this ID. Activity shows this tab’s receipts and the service totals; it is not a lookup by ID.

It does not prove

  • That the answer is right. TAONIC routes the work; it does not check the result.
  • Which miner did the work. The connected text route names the model and its invocation, not a miner.
  • A signature. A receipt is a record written by TAONIC, not a signed proof.
  • The question or the answer. Neither is written to a record. A finished answer stays in server memory for 5 minutes, so an identical question can reuse it.
  • Anything financial. There is no payment, no token and no reserve behind a receipt.

No receipt on failure. A request that is cancelled, that the provider fails, that times out or that finds no eligible route shows no answer and issues no receipt.

Ask TAONICRoutes and evidenceDocsStatus