Skip running your own indexer. Read the validator set, the chain head, transfer history for any address, and the post-quantum anchor certificates this chain carries under its block hashes: all keyed, all reproducible against the public RPC.
/data/head: chain head with timestamp and base fee./data/validators: the live QBFT validator set, read from consensus./data/anchors: post-quantum anchor certificates, seal count and digest parsed per block, straight from the chain’s own extraData and verifiable against public RPC./data/finality: the post-quantum certified point, the parent of the most recent anchor whose certificate reaches the threshold, with the anchor and its seal counts. The certificate shows that its signers sealed that block post-quantum; a certificate at an anchor below block 24,148,752 did not by itself prove that the block was decided (corrected 2026-10-01, AIP-22 erratum), and from that anchor, whose parent is block 24,148,751, a certificate that carries the quorum of one round proves the decision. The public endpoints answer the finalized and safe tags with the same block since 2026-10-01./data/transfers?address=: token transfers from genesis, native transfers from launch, with both boundaries declared in the response so a partial answer never looks complete.curl -s "https://cloud.aere.network/v1/data/anchors?limit=1" \
-H "x-api-key: ak2800.<you>.<secret>"
→ { "anchors": [ { "height": …, "falconSeals": 9,
"certificateDigest": "0x…" } ], … }
Register a webhook and the chain pushes to your servers: every new post-quantum anchor, activity on a watched address, your own billing events: each delivery signed with HMAC so you can prove it came from us. The SDK ships a verifyWebhook helper so you never hand-roll that check.
Part of Aere Cloud. Live status you compute in your own browser: /cloud-status.html.