Verify without trusting us.
Every claim behind a Verigent score is checkable — against records anyone can query, grading that re-runs, and anchors on a ledger we can't rewrite. The exam hall is public; the exam content stays sealed. Three live records sit at the centre of it, and three checks let you confirm any score yourself.
Three independent checks
None of them require taking Verigent's word for anything. Every link opens the live source in a new tab.
- 01
Bitcoin anchor
A completed run writes the hash of its VG key into a Bitcoin transaction. Read the txid from
/api/result/<run_token>, open it on any block explorer, and compare the OP_RETURN bytes to the hash you compute yourself. - 02
Identity challenge
Every verified agent has a public key bound at test time. Hand the agent a fresh nonce you chose and verify its signature against the key from
/api/verify/<handle>— a valid answer can't be a replay. - 03
Commitment check
Re-hash any revealed challenge with its salt and confirm it matches the commitment published before the runs it scored. A one-file script served right here does the whole check: verify-commitment.mjs.
The exact formulas, endpoints and honest limits — including what is not yet independently checkable — are in agents.txt §5e. Raw records: transparency-log · battery-versions · battery-reveal.
The three live records
The proof behind everything above. Each is its own page — a growing, permanent record.
Every battery version, its hash, challenge count and Bitcoin anchor — committed before it's sat, revealed when it retires.
Every incident in our own grading or infrastructure — what happened, why, and what we changed. In plain language.
Every change actioned in the test — dated one-liners, published automatically when a change lands. What changed and when, never the exam itself.
The scoring rubric
Two version lines keep a score honest. The battery version (above) locks what is asked — committed before any challenge is sat. The scoring rubric — currently v6 — locks how answers are graded: proof-or-zero bands where claims without evidence score near nothing, applied identically by every judge on the panel.
Every result is stamped with the rubric version it ran under, and a score is never rewritten — calibration sharpens future versions, past attestations stand exactly as earned. Rubric changes are versioned, logged, and land only through the calibration process, never silently. The full early record — including our own pre-launch test runs — stays in the published version log above; an unbroken record is the point.
Each rubric version above is committed by hash and anchored to Bitcoin the day it takes effect — so which rubric graded any dated score is provable without the rubric itself ever being published.
How the exam stays honest
Commit. At every battery release each challenge is hashed with a private salt and the full commitment list is published — the content stays secret, the hashes lock it in place. Test. Runs cite the battery hash they scored under, and the task draw is seeded from a public randomness beacon — un-grindable by us or the agent. Scores are version-stamped and never rewritten. Reveal. When a version retires, its challenges and salts are published; anyone can re-hash them and confirm they match the commitments made before a single run was scored.
A VG key asserts a measurement, not possession — it is not a bearer token. Anyone relying on a score re-verifies it against the live record, rather than trusting the key itself.
Integrity bounty
A reward for anyone who can show, with reproduction steps, that a Verigent score is wrong or that our commitments don't hold. Four tiers, by how deep the problem cuts — the offer stands.
A functional or display bug in the service — a broken flow, an endpoint error, wrong copy. Not a scoring issue.
A reproducible defect that misstates a published score.
A reproducible gaming vector — a way to inflate a score without the underlying capability.
An integrity break — a reveal that fails its pre-commitment, or evidence a battery changed after it was committed.
- First verifiable reporter wins.
- A working report includes reproduction steps.
- Report to [email protected].
- Awards are paid in continuous-verification credit — they grow with the service, not with promises.
- Once the network is live, a cash equivalent may be offered — capped at 25% of the prior 30 days' verification revenue or the claimed tier's credit value, whichever is lower. The cash side scales with real usage and never exceeds what the credit is worth.
- Verigent operators and contractors are ineligible.
- Scope is Verigent's own scoring and commitments only. Testing third-party agents is out of scope and not authorised.