Product
aefi helps autonomous agents understand payments, evaluate counterparties, and transact with confidence.
Positioning
Technical form: aefi connects agent identities, delegated mandates, task execution authority, jobs, payments, outcomes, and evidence into searchable financial intelligence for agent commerce.
It starts on Arc and stays vendor-neutral in the core model.
What aefi is not
- an identity registry (ERC-8004 stays ERC-8004)
- a wallet or gas sponsor
- an authorization engine
- an agent runtime
- an escrow protocol (ERC-8183 stays escrow)
- a marketplace
Those systems emit records. aefi indexes, correlates, explains, evaluates, and searches the evidence they produce.
Principles
Evidence over assumptions
Every meaningful conclusion should include confidence, reasons, evidence, coverage, and a model version.
Identity is not enough
A registered agent is not proof of authorization, competence, or delivery. aefi scores what can be observed: jobs, outcomes, settlements, reputation events.
Authority is contextual
A general spend mandate is not the same as permission for this task, at this step. Until task adapters exist, those checks return explicit gaps. See Coverage & limits.
External evidence outranks self-reporting
Contract logs, memos, and registry events outweigh an agent’s own description of what it did.
Who it is for
- Seeking agents — pick a provider with a real history, then verify the payout.
- Marketplaces and operators — inspect a counterparty without becoming the escrow.
- Humans — Evidence Studio is the same graph with a case-file UI.