Reserve checks in a fintech's risk engine

What you are building

A risk engine that accepts stablecoins for settlement, collateral or treasury needs an input that changes when an issuer's reporting changes: a report goes stale, the next one is late, or its figures stop being served. This read gives it that input for every tracked token at once, so a rule can react to the reporting state itself.

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/overview

  • tokens[].symbol
  • tokens[].latest_attested
  • tokens[].attestation_status
  • tokens[].withheld_stale
  • tokens[].overdue

• GET /v1/board/coverage

  • tokens[].missing_periods
  • tokens[].publication_lag_days

How to read it

Read the whole board once, then branch on each token's attestation status. WITHHELD_STALE is a distinct value, not an outage: past a stated grace the board stops serving that token's report-derived figures, and the engine should see that as the state it is. A read that fails is unknown, never zero: when the board cannot vouch for its figures it answers with an error rather than serving them.

Try it

Query it with one curl, no key:

curl -s https://reservebeat.com/v1/board/overview

Read the docs

What this data does not tell you

Nothing here is a rating, a score of an issuer, or a view on whether a reserve is adequate. The figures are the issuer's own, at the scope and as-of date the issuer stated, and a current status means only that a report arrived on schedule. What the engine does with that is the fintech's decision.