The three fields
The source that served this data, written as a display name: for example
CoinGecko,
GoPlus, or CCXT.
When Hive routes the same question to different providers on different days, the receipt
changes with it.When the data was retrieved from that provider. Compare it against your own clock to decide
whether a figure is fresh enough to act on.
Whether the provider was healthy for this call. A degraded or partially available provider
says so rather than returning a number that looks authoritative.
What the call cost
Since 1.7.0 the same receipt says what the call cost, on every surface:The price of the call. Discovery tools and
report_feedback are 0, and a catalog tool is 1.
Each of the nine root tools has a fixed price plus 1 per optional section, listed on
the tools page.What this call cost: the
credit_cost when the call succeeded, and 0 when it did not. A
call stopped by argument validation or a gate never reached the provider and was never
charged; a call that failed after that had its credits refunded, and warnings says so.
Refunds began in 1.9.0; before that, a call that reached a provider cost its credit even
when the provider failed.Your credit balance after this call.
null means an unlimited plan. Absent when the lane
has no notion of a balance, for example local stdio.doc_url, an anchor on the errors page for the exact code, next
to cause and next_action.
Receipts in a multi-part answer
The multi-part tools, such asresearch_token and market_positioning, run several catalog
calls. Each section of the answer carries its own source with provider, tool,
runtime_status, fetched_at and receipt_id. A section that failed is listed under
missing with its status and error. See how an answer is shaped.
Why this matters in practice
An agent doing token diligence might pull a price, a liquidity figure, and a contract risk score from three different providers within a few seconds of each other. Without receipts, the summary reads as one confident answer. With them, you can see that the price is four seconds old, the liquidity figure is two minutes old, and the risk score came back while its provider was degraded. That last case is the one worth designing for. Hive would rather tell you a source was struggling than quietly serve you a stale number.Normalization is a field, never a filter
When Hive knows something is off about a datapoint, it says so in the response instead of dropping the row. You will see fields like:
Your agent decides what to do with a suspect price. Hive does not decide for you by hiding it.
Reading receipts in your agent
Ask for them explicitly and models will surface them:Get the price of SOL and tell me which provider it came from and how old it is.The
hive skill builds receipt citation into the prompt, so you do not have to ask
every time.
