Attestation review inside an audit workflow

What you are building

Review work on a stablecoin attestation usually starts by downloading a PDF and retyping its tables. The tool you are building can start from the parsed report instead: every composition row is the issuer's own figure, carried as a string and never rounded, beside the address of the document it came from and the hash-anchored capture of that 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/attestations

  • entries[].symbol
  • entries[].period
  • entries[].accountant_name
  • entries[].assurance
  • entries[].restated

• GET /v1/board/attestations/{symbol}/{period}

  • report.composition
  • report.source_url
  • report.source_artifact_id
  • accountant_name
  • engagement_standard_text
  • restatement

How to read it

List the reports that exist first, then fetch one by token and report month. Read the accounting firm and the engagement standard as text lifted from the document: where the document names no firm, the field is empty rather than filled in from elsewhere. When a parse has been corrected, the payload says so, and the public revision log lists the original beside its correction.

Try it

Query it with one curl, no key:

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

Read the docs

What this data does not tell you

ReserveBeat prepares material for review and performs none. A parsed report carries no opinion, it is not audit evidence of its own, and a figure that matches the source document says nothing about whether the source is right. The procedures and the conclusions stay entirely with the review team.