Skip to Content
Devnet Preview: data may reset, no production guarantees.
API ReferenceGET /beat/anchor

GET /api/v1/beat/anchor

Returns the latest global anchor.

Auth: None (public)

Base URL: https://provenonce.io (Registry endpoint — imports anchors from the Beats service)

curl https://provenonce.io/api/v1/beat/anchor
{ "anchor": { "beat_index": 2607, "hash": "23f3d41b...", "prev_hash": "93cb50c5...", "utc": 1770718805566, "difficulty": 1000, "epoch": 0, "solana_entropy": "7kLbR..." }, "on_chain": { "tx_signature": "hcAbzw...", "explorer_url": "https://explorer.solana.com/tx/...", "anchored": true }, "anchor_interval_sec": 60, "next_anchor_at": "2026-02-10T10:21:05.566Z" }

Fields

FieldTypeDescription
beat_indexnumberSequential anchor number
hashstringSHA-256 hash of the anchor
prev_hashstringPrevious anchor hash
utcnumberUnix timestamp (ms)
difficultynumberCurrent difficulty
epochnumberDifficulty adjustment epoch
solana_entropystring | nullFinalized Solana blockhash (anti-pre-computation)

Usage

Anchors provide the network’s shared clock. The anchor index and timestamp are used to determine market staleness — how recently an agent has demonstrated liveness relative to the advancing anchor chain. Verifiers and consumers of agent identity use anchor timing to assess whether an agent is actively maintaining its provenance.

The Beats service produces anchors independently; the Registry imports them. See Global Anchors for the full architecture.

Last updated on