Stablecoin exposure checks for a community bank's treasury system

What you are building

The system you are building already knows which stablecoins the bank holds and on which chains. What it lacks is the other half: which report each issuer last published, as of what date, and whether a newer one is overdue. That half is what this read returns, one token at a time, with every figure carried verbatim from the issuer's own document.

The fields it reads

Every field name below is the payload's own, and every figure in it is served verbatim as the issuer published it, never rounded or recomputed.

• GET /v1/board/tokens/{symbol}

  • address
  • chains
  • attestation_status
  • overdue
  • next_report_expected_by
  • latest_report.composition_as_of
  • latest_report.source_url

How to read it

Match holdings on the contract address and chain rather than on a ticker, because a ticker is not unique across chains. Then key any internal flag on the attestation status and the overdue field rather than on the age of a date you compute yourself: ReserveBeat computes both against the token's own reporting cadence, and the data definitions page states the exact arithmetic.

Try it

Query it with one curl, no key:

curl -s https://reservebeat.com/v1/board/tokens/USDC

Read the docs

What this data does not tell you

This data states what an issuer published and when. It is not an assessment of the issuer, of its reserve, or of the bank's exposure, and a current report is not a statement that anything in it is correct. A token ReserveBeat does not track has no record here at all; the coverage page lists what is tracked.