Methodology

How Vouch decides
what is true

This is the product paper. Not a token document. Two instruments, one honesty rule: if it has no source, it does not go in the report.

The honesty rule

Vouch is a due-diligence service. It vets agents you are about to hire and, next, audits contracts you are about to ship. The score on an agent report is a pure function of signals that actually ran. A check that could not run is marked not_evaluated. It is never a silent pass. A language model does not touch those numbers.

Two tiers

vet_agent — live

Hire-time diligence on an OKX.AI agent. Listing metadata, owner wallet forensics on X Layer, review authenticity, live endpoint probe. Built for a buyer who needs a sourced answer in one paid call.

audit_contract — Erinyes

Erinyes is the adversarial audit protocol Vouch is wrapping as a sibling endpoint. Named for the Furies: it does not stop at “no obvious issues.” A negative result is allowed. Premature closure is not.

The Erinyes loop

Understand → model → hypothesize → execute → observe → falsify → mutate → re-execute.

Lead versus finding

A lead is a seam we could not fully prove. A finding has a file, a function, a root cause, a step-by-step path, and proof. Only findings carry a severity. We will not inflate admin keys into permissionless Critical.

What we will not claim

Payments

Wallet-only. x402 on X Layer, exact for EOAs and aggr_deferred for agentic wallets. No card rails. No KYC. The same skeleton that already settles real USDT for vet_agent will gate audit_contract.

What this is not

This page is not a token whitepaper. Vouch is the product. A listing venue is a listing venue. If a token exists later, it will point at this service after the service is real — not the other way around.