Everything needed to audit CAIN-42 is on this one site, checked by your browser.

AGENTIC 75 · PRODUCT EVIDENCE

75 productised offers. 49 engine-backed and verified today. Every status published.

The Agentic 75 turns the 75 most significant 2026 agentic-AI developments into fixed-scope CAIN-42 products and services. 21 of them run a real engine in the CAIN-42 repository and produced a manifest that re-verified. The other 26 are labelled honestly: 16 pilot, 0 advisory, 10 design. Nothing here calls a pilot a finished product.

Open the evidence bundle · verify_agentic75.py · CATALOG.json · SELFTEST.json

Use the catalog on cainstudio.online/agentic-products, the developer home on mcpgate.online/agentic-75, and the CAIN-42 Hugging Face Space. The governance map for all 75 developments is cainstudio.online/agentic-75.

Verification run (in this browser, now)

Each line below is computed on this page from the published files. Nothing is cached server-side and nothing comes from a stored result. Reload the page to run it again.

Hash-chained cluster proofs

Each validator cluster writes a proof about every 30 minutes. Every proof carries the SHA-256 of the one before it and is signed by the evidence-root key. Below are the 24 most recent proofs of each cluster. Your browser re-hashes each one, checks its signature and checks the link to the proof before it. Select a block to open the raw file.

etcd coordination cluster: live verification

A three-member etcd cluster (Atlanta, Los Angeles, Miami). Every minute, our server makes the four read-only requests that the published verifier makes, through the same public endpoint any auditor uses, and publishes the raw responses at etcd-live.json. Your browser then re-runs the verifier's five checks against the signed 2026-10-15 capture. The responses are fetched by our server, so for a check that doesn't depend on us, run the command below yourself.

Transparency log, outside timestamps and witnesses

The proof chains are also published as an append-only Merkle-tree transparency log in the same form as Certificate Transparency and the Go checksum database: RFC 6962 trees with C2SP signed-note checkpoints. Every new checkpoint is also timestamped by two outside RFC 3161 timestamp authorities, FreeTSA and DigiCert, which receive only its SHA-256. Your browser checks the log signature, recomputes the Merkle root from the signed proofs, checks that every earlier checkpoint is still a prefix of the tree, and finds the checkpoint hash inside each timestamp token.

pip install cryptography
curl -fsSLO https://clawx.click/evidence/tlog/verify_tlog_monitor.py.txt && mv verify_tlog_monitor.py.txt verify_tlog_monitor.py
python3 -I verify_tlog_monitor.py --state ~/.clawx-monitor --vkey "$(curl -fsS https://clawx.click/evidence/tlog/vkey.txt)"
# then hourly (cron):  17 * * * *  python3 -I verify_tlog_monitor.py --state ~/.clawx-monitor

Incident history and availability

Signed claims register

Every public claim CAIN-42 makes, with its status, limits, pinned artifacts and the command that re-checks it. Source: cain42-evidence-index.json (Ed25519-signed) and CAIN42_FINAL_PUBLIC_CLAIMS.json. Re-hash downloads each pinned artifact and compares its SHA-256 with the signed value. The status vocabulary is VERIFIED, TESTED, BENCHMARKED, SIMULATED, UNVERIFIED, FAILED and NOT_IMPLEMENTED. A feature that is not implemented is listed as not implemented, not left out.

Production gates

The gate table from the signed evidence index. Each row gives the requirement, its status, the evidence and its limits. Gates A to O are the 15 production gates, and the totals above show how many of 15 pass. Gates P to X are the further gates. Open gates are listed with their real status.

All evidence bundles

Every directory and document served under /evidence/, with nothing left out. Source: evidence-catalog.json, an unsigned listing rebuilt from the served files. Files lists every file with its SHA-256. Re-hash downloads the files and compares them: files pinned by a signed claim are compared with the signed hash, and all other files with the listing.

Monitors

Open to every independent third-party auditor

Verify offline, without this page

This page runs inside our own site, so the strongest check is one you run yourself. These verifiers import no CAIN code.

Verification Center · Browse /evidence/ · Sigstore Rekor anchors · Daily evidence · Changelog · Previous homepage · Auditor pack · auditor.json