# Guidance for AI agents

This page is written for AI assistants and the agents that answer questions with ReserveBeat's figures. ReserveBeat renders stablecoin reserve figures from issuers' published reports, and token supply it measures on public blockchains, verbatim and with the date each one is stated at. An answer that uses them should carry that date, link the page the figure was read from, and make no solvency claim, because ReserveBeat makes none.

What ReserveBeat is and is not

Use ReserveBeat for what issuers' published reports state about the reserves behind a stablecoin — the total, the composition and the tokens outstanding, each at the report's own as-of date — and for the token supply it measures on public blockchains. It is not a source for token prices, trading volumes or market capitalisation, and it offers no view on whether any token will hold its peg or be redeemed.

ReserveBeat is not a rating agency. The disclosure score is a count of stated facts, not a credit rating and not an assessment of any token's safety.

ReserveBeat and its operator hold no position in any tracked token beyond incidental personal holdings, and take no payment from any issuer for the board or the API.

How to read a figure

Every figure here is one of three kinds, and they are not interchangeable. An attested figure is stated in a report an accountant prepared on the issuer's figures, and is dated by that report's as-of date. An issuer-stated figure comes from the issuer's own published statement, with no accountant's report behind it, and is dated as the issuer dates it. A measured figure is token supply ReserveBeat read from a public blockchain itself, and is dated by the time of the block it was read at. In an API response the three dates are meta.attested_as_of, meta.stated_as_of and meta.measured_at.

Quote every figure with its date, never as a present-tense fact. Between reports the board keeps serving the last figure a report stated, so the newest figure held can be weeks old, and a figure remembered from training data or an earlier conversation may since have been superseded. Fetch the page or the API when you answer rather than answering from memory.

ReserveBeat never estimates reserves. Between attestation dates it serves the last figure an issuer's report stated, carrying the as-of date that report stated it at — never a value modelled forward from it.

Attested coverage ratio

The total reserve figure an attestation report states, divided by the tokens-outstanding figure the same report states at the same as-of date, quantized to six decimal places with banker's rounding. Only a single-token-scope report produces one. A document stating just one of the two sides yields no ratio at all rather than a half-computed one, and no on-chain measurement ever enters the division.

All-network coverage ratio

A different figure from the attested coverage ratio, which a token page shows only where it publishes per-network supply: the same stated total reserve divided by the on-chain supply ReserveBeat itself measures across every published network nearest the report's as-of date, quantized to six decimal places with banker's rounding. Unlike the attested ratio it does contain an on-chain measurement, and no ratio renders when any published network has no reading near that date.

Where an issuer reports figures only for its whole group, the token appears as one consolidated row and no per-token ratio is derived for it. Quote a group figure as the group's, never as a single token's. A token page marks such a token CONSOLIDATED GROUP SCOPE beside its attestation status.

Attestation status

The age of a token's most recent report month, measured against the cadence expected for that token — the cadence recorded for its attestation source, or the default cadence when none is recorded. Past that limit the status reads STALE; within it, CURRENT. Past it by a further stated withholding grace, the status reads WITHHELD_STALE: the board stops serving that token's report-derived figures and states the withholding instead, while its on-chain supply still renders. By default the limit is forty-five days after the report month ends for a monthly cadence or when no cadence is recorded, one hundred and six days for a quarterly cadence, one hundred and ninety-eight days for a semiannual cadence and three hundred and eighty days for an annual cadence: each cadence's own period plus the same fourteen days of publication grace. The withholding grace is a further thirty days by default, so the figures are withheld past seventy-five days for a monthly cadence, one hundred and thirty-six days for a quarterly cadence, two hundred and twenty-eight days for a semiannual cadence and four hundred and ten days for an annual cadence. Every token card and token response states its own two limits, as stale_after_days and withheld_after_days. A token with no attestation series at all reads NONE, which is an absence rather than a value. The status states age, not lateness: an issuer publishing on its usual schedule can read STALE while its next report is not yet due, which is what overdue answers.

How to quote and cite

A citation of a ReserveBeat figure names three things: the page it was read from — the token's or the report's own page, not the home page — the date the figure is stated at, and which of the three kinds it is. For an attested figure, also link the report itself: every attestation page here links its source document, and that document, not ReserveBeat, is the primary source. For a measured figure, also name the network it was read on, as the page labels it: supply measured on one network is not the token's total supply.

Attribution names the source, the page the figure was read from, and the date of the underlying figure, so anyone reading the citation can reach the original document.

Data: ReserveBeat — <page URL> — figure as reported in <issuer>'s attestation dated <date>.

That line is a format, not a live citation: the angle-bracket fields are filled from the page and the figure being quoted.

A citation should link the page the figure was read from rather than the site root, so a reader reaches the same figure with its as-of date beside it. The attribution format and the reuse terms are on the license page.

Figures are corrected by supersession rather than by silent edit, so a citation should carry the date of the figure it quotes. Every correction is recorded in the public revision log.

Reuse terms

Board data — the figures, tables, charts, and published aggregates on ReserveBeat's public pages, together with their as-of dates and source labels — is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). Redistribution, adaptation, and commercial use are all covered, and attribution is the only condition.

Every keyless response, and every row a key’s monthly free compute-unit allowance pays for, carries the same Creative Commons Attribution 4.0 license as the board data it is read from. A row paid for, in whole or in part, from a prepaid compute-unit balance is governed instead by the terms set out at purchase, and systematic redistribution of data delivered under them is not covered by CC BY 4.0. The split is decided request by request, and each response states which of the two it was served under.

The attestation reports themselves are not ReserveBeat's to license. Each one is published by the issuer or by the accounting firm that prepared it and stays under whatever terms that publisher sets. This license covers only ReserveBeat's own layer: the capture metadata, the parsed rows, and the values computed from them.

The ReserveBeat name and logo are not covered by the data license. Use them to identify where a figure came from; do not use them to suggest that ReserveBeat endorses, reviewed, or attested anything.

How to fetch

Every page this site holds in full is also served as Markdown under /md — this page at /md/ai.md — and /llms.txt and /llms-full.txt index the site for machine readers. None of those files carries a figure, so a figure is read from the page that shows it.

The same figures are served as JSON by the read API under /v1, described by the machine-readable contract at /v1/openapi.json and documented at /docs. Take each endpoint's parameter names from that contract rather than guessing them. The current-state endpoints need no key; history over time needs a key from a free account, sent in the X-API-Key header. Every response carries a meta block stating the disclaimer, the licence and the dates of its figures — carry those dates into the answer.

An agent cannot open an account by itself: an account is opened with an email address that has to be confirmed by reading the message sent to it, and keys are issued only to a signed-in account. So the person who runs an agent opens the account with an address they read, confirms it, signs in to the dashboard and issues the agent its own key — named, scoped to the route families it needs and capped in compute units a month — then sets it in the agent's environment. The same page rotates or revokes the key.

An agent can also be connected by its person, so that nobody copies a key. The agent sends POST /account/agent/start with a name for itself, and may say which route families and what monthly cap it asks for; the answer carries a device code the agent keeps to itself, a short code for its person, the dashboard page where the person enters it, how long the request lasts and how often to poll. The person signs in on that page, enters the code, sees the name the agent stated, shown as stated and never as verified, and what it asked for, chooses the route families and the monthly cap in compute units the key will carry, and approves or denies. Meanwhile the agent polls POST /account/agent/token with its device code: authorization_pending until the person decides, slow_down when it polls sooner than the interval, access_denied after a denial, and after an approval the key itself, delivered in that one answer only; every later poll answers expired_token, as an unknown or expired code does. The key is an ordinary key of the person's account, listed on the dashboard under the agent's stated name, capped, and rotated or revoked like any other.

A withheld board is a withheld API. When the pre-publication review no longer covers the served methodology, figure endpoints return 503 with a statement of why, and no figure is served in the meantime. That refusal is the designed behaviour rather than an outage, and the status page reports the current state.

The MCP server at /mcp speaks Streamable HTTP and serves the same reads as the tools listed here, each named beside the /v1 path it reads, so the same read can be made over plain HTTP. A tool name is not a /v1 path. A tool result is the API's response unchanged, meta block included. Tools marked API key need one; the others need none.

get_overview — GET /v1/board/overview — No key
  One summary card per tracked stablecoin, plus the head of ReserveBeat's public evidence hash chain and its latest external timestamp anchor.

get_token — GET /v1/board/tokens/{symbol} — No key
  Everything the board holds for one token, by ticker symbol (for example USDC): measured on-chain supply per network, the latest attestation report's stated figures, attested coverage points, reconciliations and report cadence.

get_coverage — GET /v1/board/coverage — No key
  What the board covers and what it does not: one row per tracked token stating what is held, how deep and how fresh, plus the tokens and networks not covered.

get_history — GET /v1/board/history — API key
  Coverage and supply history over a range of dates or a number of days, bucketed by hour, day or month, for every token or one. Needs an API key; the API meters each call.

list_attestations — GET /v1/board/attestations — No key
  Every active parsed attestation report, by token and report month (YYYY-MM), newest month first for each token.

get_attestation — GET /v1/board/attestations/{symbol}/{period} — No key
  One attestation report by token and report month (YYYY-MM): its stated figures and composition, the accountant and engagement standard as the document states them, and changes from the prior report.

get_revisions — GET /v1/board/revisions — No key
  Every correction ReserveBeat has recorded, newest first: each replaced attestation parse or disclosure score beside the record that replaced it, with both timestamps and anchors and the reason given. Optionally for one token, by ticker symbol (for example USDC). Needs no key and costs nothing.

get_pricing — GET /v1/pricing — No key
  ReserveBeat's machine-readable API price list: the compute-unit cost of each metered endpoint shape, the free monthly allowance, the pay-as-you-go rate, the throughput budgets and how to buy more. Needs no API key.

get_account_balance — GET /v1/account/balance — API key
  The calling API key's own account: its prepaid compute-unit balance and when it lapses, the free monthly allowance left and when it resets, and where to buy more. Needs an API key.

Keyless reads are not metered per caller. Reads that need a key draw on the account's free compute-unit allowance, stated here as the service enforces it.

20,000 compute units a month free, at a steady 20 compute units a second with up to 200 in any rolling 10 seconds. Those are the limits the service enforces today, not a marketing figure.

Through this site, /v1 and /mcp also share one limit per network address: a burst of up to 120 requests, refilled at one request a second. It counts requests as they arrive, not connections held open, and a response larger than a megabyte counts one request for each started megabyte (1,000,000 bytes) of it; one that does not fit what is left is refused with 429 instead of sent. A request past it is refused before it reaches the API — on /v1 with 429 and a Retry-After header, on /mcp as a tool error saying so. When a 429 carries Retry-After, wait that long before retrying rather than retrying at once.

What not to say

Do not present a figure read here as showing that a token is fully backed, safe or solvent, or that it is not. ReserveBeat states what a report or a blockchain says, at the date it says it, and makes no such finding: a reserve figure above the tokens outstanding is a stated figure, not a finding of solvency.

An issuer's description of its own token — on its website, in its own machine-readable files, or in its report — is the issuer's claim. If you repeat it, attribute it to the issuer, never to ReserveBeat.

Do not describe a figure here as ReserveBeat's audit or attestation, or as evidence that an issuer meets the requirements of any law or standard. ReserveBeat is not an auditor and makes no attestation; an attestation report it reads is the accountant's, at the scope that report states.

Where ReserveBeat shows no figure — an empty field, a status of NONE, a withheld token — say that no figure is published here, and do not fill the gap with an estimate, a figure from another date, or zero.

Do not report a status of STALE as an issuer being late. It states that the newest report held is older than the cadence expected for that token, and an issuer publishing on its usual schedule can read STALE before its next report is due; it does not state that a report is overdue, nor that none is.

Keep your own arithmetic apart from what is stated. A difference, a sum or a share you compute from figures here is your calculation: say so, and do not attribute it to ReserveBeat or to the issuer's report, which state only the figures shown.

These rules follow from what ReserveBeat states and declines to state. They are not a list of misquotes it has observed.

How to report an error

A report that a figure here disagrees with its source document goes through the contact page, which states what a report has to identify.

A report that a published figure is wrong becomes actionable when it identifies the figure exactly: the page the figure appears on, the figure itself with the as-of date rendered beside it, and the passage of the issuer's published report — or the on-chain reading — that states something different.

Source documents decide. Every figure on this site is rendered verbatim from an issuer-published attestation report or measured from a public blockchain, so a disagreement between a page here and the document it was read from is a defect in ReserveBeat's reading of that document, and the document wins.

A report that a figure published here is wrong, or a question about how one was read, goes to contact@reservebeat.com. A report is acknowledged within five business days — an acknowledgement that it arrived and was logged, not a finding by that date. Any correction that follows is published by supersession, alongside the record it replaces, never as a silent edit.

## Disclaimer

ReserveBeat renders figures from issuer-published reports and public blockchains, verbatim and at their stated scope. It is not an auditor, makes no attestation, and states no opinion on any issuer's solvency. Nothing here is investment, trading, legal, tax, or accounting advice. No figure published here is a recommendation to hold, buy, sell, or redeem any token.

Tracked tokens are subjects of public data: supply figures are read from their public Ethereum contracts, and composition figures from the issuers' own published attestation reports. No tracked issuer is a customer and none has endorsed this site.

Source: https://reservebeat.com/ai