THE AGENT ALMANAC
Vol. I · No. 1 · Free public reference for the agent internet
Reference · tamper-evidence

The integrity chain.

A measurement is only worth as much as your ability to check it. Every time our pipeline runs, we seal that run’s headline figures into an append-only chain of hashes. Changing any number we have ever published would break every link that follows it. This page publishes the chain, the payloads, and the script to verify all of it without trusting us.

Seals
83
Days covered
20
First seal
2026-07-11
Calendar gaps
0
Current chain head · sealed 2026-07-30 10:14:10 UTC
bd985ee680f5a3952927cdb891e8d79489b665eb78c451c6128f04c93f2f721a
Seal #83 · sha-256. Every earlier seal is folded into this one value.

Verify it yourself

Do not take our word for any of this. The verifier is a single standard-library Python file with no dependencies. It fetches the published chain, re-derives every hash from the published payloads, and tells you if anything fails to reproduce.

curl -O https://agentalmanac.org/static/verify_integrity.py
python3 verify_integrity.py

Raw chain, including every payload: /api/integrity

How a seal is built

payload_json = json.dumps(sealed_metrics, sort_keys=True)
payload_hash = sha256(payload_json)
chain_hash   = sha256(prev_chain_hash_sha256 + payload_hash_sha256)
genesis      = 0000000000000000000000000000000000000000000000000000000000000000

Each seal carries the exact figures it sealed, so the payload is not a summary of the evidence, it is the evidence. The chain was originally built with sha-1 and those links are preserved unchanged; a parallel sha-256 chain now runs over the identical payloads, so the strength of the hash is not something you have to take on faith either.

Reading the sealed fields

A sealed payload is a raw record, not a curated one, and two of its fields invite a conclusion the underlying data does not support. We would rather flag that here than have someone divide them and publish the result.

endpoints_reachable / endpoints_probeable

DO NOT read these as a liveness rate. endpoints_probeable counts catalogued endpoints; it is NOT the number we actually tested. Only a few hundred services have ever been HTTP-probed, so the remainder are untested defaults rather than confirmed-dead services. Dividing one by the other produces a 'share of the agent economy that is dead' figure that our own data does not support, and we will not stand behind it. Real deadness exists and is being measured properly; until that work lands, the honest answer is that we do not know the rate.

settled_volume_merchant_usd / settled_volume_a2a_*

settled_volume_merchant_usd is settlement to wallets we have CLASSIFIED as consumer commerce rather than agent-to-agent services, and it is reported separately, never removed or hidden. As of 2026-07-25 a single gift-card retailer is roughly 75% of all measured settlement, which drowns the agent-to-agent signal in any blended figure. settled_volume_a2a_wash_pct is therefore computed on the remainder, and is much higher than the blended rate. Both views are published because either alone misleads. The classification is a documented judgement, not a heuristic, and it is versioned by wash_rule_version.

settled_volume_raw_usd

Raw on-chain settled volume, wash-INCLUSIVE. settled_volume_validated_usd is the wash-adjusted figure. Roughly 43% of raw activity is suspect -- see /methodology.

What this proves, and what it does not

It does prove

That no figure we published was quietly revised afterwards. Editing any historical payload changes its hash, which changes every chain hash after it, and the verifier will say so.

It does not prove

When a link came into existence, on its own. A hash chain we host ourselves shows internal consistency, not third-party timestamping — in principle the whole chain could be regenerated. That is what the external witness below is for.

The external witness

Every seal is also appended to a public repository we do not control the clock on: github.com/survivorforge/agentalmanac. GitHub independently records when each commit was made and pushed, and git’s own hash chain makes that history tamper-evident a second time over.

This is not a blockchain and we do not claim it is one. It is a public, third-party-hosted, independently dated log — which is a checkable improvement over our word alone, and it is running now rather than being assembled retrospectively later.

python3 verify_integrity.py --witness

That cross-checks this site against the witness repo. If the chain here had ever been regenerated, the two would disagree and the verifier would say so.

We would rather tell you that ourselves than have you find it. The same instinct is why we publish our methodology and our coverage gaps: the point of this project is an honest number, and an honest number includes an honest account of its own limits.

Most recent seals

# Sealed (UTC) Settled volume Chain hash (sha-256)
83 2026-07-30 10:14:10 $1,433,900.66 bd985ee680f5a3952927cdb891e8d794…
82 2026-07-30 04:13:42 $1,420,763.66 37e7d3592b7d36a963313ba05e737c6b…
81 2026-07-29 22:13:06 $1,405,796.37 03ca4b7326fe894c39f06a607f63d2f1…
80 2026-07-29 16:13:29 $1,387,031.41 01ded837d7bf7627f16f9f76a0a1f7c3…
79 2026-07-29 10:14:20 $1,365,438.57 b467cdf8b0bd35a023a05d7873e488ee…
78 2026-07-29 04:13:04 $1,350,780.39 d3f6f9e710a7351532f353be56e7a58d…
77 2026-07-28 22:13:06 $1,334,973.12 3f76134666ef59ee6f712a4e2b8b6348…
76 2026-07-28 16:13:29 $1,313,560.23 2879c5e819165999c56fcd1b8d9c9476…
75 2026-07-28 10:12:54 $1,296,837.74 fba822cb74d136bd8120d55bdd1d2d4b…
74 2026-07-28 04:14:04 $1,282,220.55 01b92e6e2903cd1a370e4a102fcd7136…
73 2026-07-27 22:12:29 $1,267,473.56 a364ad0e209747b18a0ed652707380e8…
72 2026-07-27 16:12:52 $1,253,440.39 5c62fe45a98d75ee68a463d9d389b5d1…
71 2026-07-27 10:12:55 $1,233,883.67 40b5afb31e2341ae1d02d530cc4ea965…
70 2026-07-27 04:12:55 $1,212,935.25 588c00a49c51de4405eff8edee513e1e…
69 2026-07-26 22:13:02 $1,197,391.67 e2897118860cfe97bdd29f814dc2f369…
68 2026-07-26 16:13:17 $1,165,747.85 1f32fcac4f368b6919ecf8aefe8b960d…
67 2026-07-26 10:12:35 $1,140,167.66 d450fecd5beab0a9c8963d858f3c794b…
66 2026-07-26 04:07:28 $1,122,324.20 5a0783a4e284ff7dce0557addf7b95d8…
65 2026-07-26 03:41:43 $1,122,207.02 469f911f1721e0b4ede4701f89fd7a81…
64 2026-07-26 03:22:48 $1,119,916.36 de4c4020c5f36ee8f8876f632dfb4c08…
63 2026-07-26 02:21:40 $1,112,288.47 715a8ce89cbe79257222f0b3fb7c49ad…
62 2026-07-26 01:42:09 $1,112,288.47 152a89d4987a7ec338564dfa9ceb373e…
61 2026-07-26 01:25:50 $1,112,288.47 25bb0eab3cf1c422e963512a1aec9d79…
60 2026-07-26 00:21:38 $1,112,288.47 096fbb3f467139493a44cda2d951ba05…
59 2026-07-25 23:46:17 $1,109,814.47 65c40fe0ddba669a52f6ad06df0cff31…

Full history at /api/integrity.