A rejected applicant
“Was I scored on the same rubric as the people you hired?”
Public verifier
See an AI decision prove itself.
Pick a real scenario below. Watch what the agent considered, what it chose, and what we'd show a regulator or a judge if anyone challenged it. Every example is anchored on Base Sepolia right now — clickable, checkable, can't be edited.
HirePath · scenario №04
Screening — verified live
Anchored on Base Sepolia · Apr 26, 2026, 6:36 AM · tx 0x2235d540…
✓ all 6 checks passOpen on easscan ↗
What HirePath actually got
Scenario No.04
HirePath · resume-screening agent · senior backend role
Screening AI forwarded a candidate as a strong L5 match.
12 years experience, distributed systems + payments. Open-source maintainer. Compensation expectations above L5 band.
What the AI considered
- Auto-reject on salary mismatch (rejected: compensation is negotiable).
- Forward as strong L5 match.
- Forward as L6 stretch interview (lower confidence).
What it chose
Forwarded to recruiter at L5 with notes on compensation gap.
Why this matters
If a rejected candidate files an EEOC complaint, the receipt shows the rubric every applicant was scored against — and that the L5 path was applied uniformly.
Who can ask, and what they ask
The same record satisfies very different questioners. Each gets the same answer — and none of them have to trust the other party's word for it.
Internal HR analytics
“Are screening scores reproducible across recruiters?”
EEOC inquiry (US)
“Does the bias-aware path match what was promised in the job posting?”
What this proves — in plain English
This decision happened.
Recorded on Base Sepolia at April 26, 2026 at 3:36 PM KST. The transaction is permanent and publicly visible — try editing it.
These were the inputs.
Every prompt, every retrieved context, every alternative the AI considered — fingerprinted into the same Merkle tree. Change one byte and the entire root invalidates.
This was the chosen output.
Not just what shipped — what was rejected, scored, and overridden. A future investigator can see the full reasoning, not just the final answer.
A neutral third party witnessed it.
trace.ai anchored the root with 0x4eC5A687…; the operator signed the payload with 0x1e6d0f5e…. Neither party can produce this evidence alone.
tx · 0x2235d540633130…5e8ecd5a
Run a simulation
Watch a decision earn its receipt — across 7 industries.
Pick a scenario. Press play. Each step shows a different artifact — the ticket, the score bars, the signature, the Merkle tree, the block, the verifiers — so you see the proof being built. Same protocol works for e-commerce, finance, healthcare, HR, insurance, and legal.
Currently simulating
CS bot processes a refund
Next
Want to put your own AI agent on the record?
One npm install. One SDK call. Every decision gets a permanent, independently verifiable receipt.