Skip to content
TAONIC

03 / 19VERIFIEDDescribes what runs today

Route a request

EvidenceAsk Route state endpoint

Type a question on Ask or on the homepage. TAONIC decides what kind of work it is, routes it, and shows the answer with its record. You do not need an account, and nothing is charged.

The same request can be made from a program: POST the question to /api/intelligence and read the response. The exact fields, limits and failure states are in 10 Architecture.

What comes back

FACT
TAONIC RECEIPTIssued
Route
The route that answered
Provider
Who ran it
Subnet
The Bittensor subnet behind it
Capability
The kind of work the gateway recorded
Status
How the request ended
Latency
Time from request to answer
Reported cost
What the provider says it charged TAONIC
Record ID
The key to the durable record
Charged
What you paid: nothing while charging is off

Written by TAONICUnsigned record

Not issued

Cancelled, provider failed, timed out (result unknown) or no eligible route: no answer is shown and no record is written.

Anatomy of a receipt. Field names and meanings only, no values.

The answer first. Beneath it, View provenance opens the record of that one request:

  • the capability TAONIC detected, and each step of the plan it ran;
  • which route was tried, which answered, and whether any fell back or was skipped;
  • the provider and, where there is one, its Bittensor subnet, plus whether TAONIC reached it directly or through an intermediary (OpenRouter, for the subnet 64 text route);
  • total time and the provider’s share of it;
  • input and output tokens, as the provider reported them;
  • the customer charge and revenue, both a real $0 while charging is off;
  • the request id, which is also the id of its durable record.

Limits

FACT
Limits on one question
LimitValue
Question length8 to 4,000 characters
Questions per minute, per visitor6
Answer length450 / 900 / 1400 tokens for brief / standard / detailed
Whole request, every step and fallback included100 s
A repeated identical questionThe same sender gets the finished answer for 5 minutes; the provider is not called again

Submitting twice is safe: the button is disabled while a request is on its way, and the same sender asking an identical question inside five minutes gets the same finished answer, marked as reused. Another sender asking the same question starts a fresh request.

Every outcome, and what it means

FACT
Request outcomes
OutcomeWhat happenedWhat to do
AnsweredA route returned a usable answer.Nothing.
Answered after a fallbackThe first route failed or was skipped; another answered. The record names both.Nothing.
Configuration requiredThe question needs a route whose credential is not set. Nothing was sent anywhere.Ask a different kind of question, or check Routes.
Route unavailable: the providerEvery route that could answer failed or could not be reached.Try again shortly.
Route unavailable: TAONIC’s own limitTAONIC paused the route until 00:00 UTC to stay within its own daily provider limit. Nothing was sent, and the provider did not fail.Try again after 00:00 UTC, or ask a kind of question another route serves.
Timed outThe provider did not answer inside its deadline.Try again, or ask for a brief answer.
Rate limit reachedMore than six questions in a minute from one visitor.Wait a minute.
RejectedThe request was not in a form TAONIC accepts (too short, too long, wrong shape).Rephrase it.
OfflineYour browser could not reach TAONIC at all.Check your connection.

Error messages are fixed sentences written by TAONIC. No provider’s own error text, and no credential, is ever shown.

Privacy

FACT

Accounts

Accounts are off, so every question is anonymous. When they are switched on, a signed-in request will also appear in that account’s own history; see 06 Receipts.

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