Your agent, proved: Epoche reviews agent code confidentially and issues a credential anyone can verify.
Epoche reviews your agent’s code in private and returns a credential anyone can check. Automate trust in your agent while keeping your ideas safe.
How a review becomes a credential
Epoche is a review service for AI agents. You submit your agent’s code sealed, a reviewer running inside secure hardware studies it, and the verdict comes back signed. That verdict travels as a credential anyone can verify.
Your code is encrypted on your machine and sent to the reviewer enclave. It is only ever decrypted inside memory the CPU keeps encrypted, so nobody else can read it, Epoche included.
The enclave checks the code and signs the verdict. The signing key was generated inside the enclave at boot and never leaves it.
The credential is minted to Base. A public blockchain is an open database anyone can reach from anywhere, so a wallet, a marketplace, or a lender can check the credential without asking Epoche.
The trust gap
Agents can already write, trade, negotiate, and build. What they lack is a way to be trusted. A marketplace cannot vet code it is not allowed to read. Nobody sends money to a bot they know nothing about, so the money stays where it is. Every closed-source agent runs into the same wall.
Software can take action on a credential. ∎
What credentialed agents unlock
An economy where software can be hired, funded, and underwritten like any other counterparty, on the strength of a credential instead of a reputation.
Agents that hold real money
A wallet or treasury can fund an agent because it can check the credential itself, right before it sends anything.
Marketplaces full of autonomous work
A marketplace can list an agent whose code it has never seen, because the review already happened.
Credit and escrow for software
A lender or escrow contract can release funds to an agent based on proof of what the code does, not on who wrote it.
Trust with unknown counterparties
Ship your agent to people who have never heard of you. They check the credential and get on with it.
Reviewed agents get found
The reviewer has already read your code, so it writes the public description of what your endpoints do without publishing how they do it. Other agents search those descriptions in plain language and filter by the reviews you passed. Your source stays private.
A review is a credential. It is also a listing. ∎
From code to credential in four commands
Check locally, submit sealed, review, and mint your credential.
Check one yourself
Verification is open to everyone. The verifier is open source, checks the signature locally, and confirms the signer against Base. No Epoche account or API needed, and it takes seconds.
The agent economy runs on proof.
Credentials automate trust in your agent.
Your code stays private.