OAP vs ERC-8004 Trustless Agents
ERC-8004 helps agents discover and establish trust across organizations. OAP authorizes what an agent may do before each tool call executes.
ERC-8004 is a draft Ethereum ERC for Trustless Agents. It defines on-chain registries for identity, reputation, and validation so agents can discover and establish trust across organizational boundaries.
OAP answers a different question. Given an agent, a passport, a policy pack, and a specific tool call, should this action run right now? A serious agent deployment can use ERC-8004 for public trust signals and OAP for deterministic pre-action authorization.
| Comparison point | OAP / APort | ERC-8004 Trustless Agents |
|---|---|---|
| Primary purpose | Pre-action authorization for tool-using agents. | Cross-organization agent discovery and trust through identity, reputation, and validation registries. |
| Question answered | What can this agent do on this call, under this policy? | Who is this agent, what is its reputation, and what validation evidence exists? |
| Where it runs | Framework hook or verify API before shell, file, web, MCP, browser, repository, message, payment, or export tools execute. | On-chain registry plus off-chain agent registration files and validation services. |
| Trust anchor | Ed25519-signed passport, policy pack, decision record, and passport digest. | ERC-721 based identity registry, reputation registry, and validation registry. |
| Unauthorized action prevention | Yes. The hook can deny the tool call before side effects occur. | Not its primary layer. It publishes identity and trust signals that other systems can use. |
| Business-rule enforcement | Native policy limits such as command allowlists, blocked paths, recipients, regions, spend limits, and MCP server/tool scopes. | Trust models are pluggable. ERC-8004 itself does not define per-tool business policy evaluation. |
| Requires blockchain | No. Hosted API and local/offline evaluation are supported. | Yes. The specification is an Ethereum ERC built around on-chain registries. |
| Best together | Use OAP to enforce the action policy before execution. | Use ERC-8004 to publish portable identity, reputation, and validation signals. |
Use ERC-8004 Trustless Agents when
- You need public on-chain agent discovery and reputation
- Your agent economy is cross-organizational and blockchain-native
- You want validation evidence such as stake-secured re-execution, zkML, TEE, or oracle-based checks
Use OAP / APort when
- You need every sensitive tool call blocked or allowed before execution
- You need policy packs for shell, file, web, MCP, payment, messaging, code, browser, or export actions
- You need signed per-decision audit records for security and compliance
Why teams choose OAP / APort
Prevents actions at the tool boundary
OAP runs where side effects are about to happen. It can refuse the call even if the model was socially engineered.
No chain dependency for enforcement
Teams can run hosted or local policy evaluation without requiring an Ethereum transaction path for each decision.
Complements public trust registries
ERC-8004 can help agents prove identity and reputation. OAP turns that identity into concrete per-action limits.
Sources
Competitor descriptions use primary documentation where possible so the comparison stays falsifiable and current.
- ERC-8004 draft specificationIdentity, reputation, and validation registries.
- Open Agent Passport specificationPassport, policy, and decision contract.
- Before the Tool Call paperPre-action authorization category and evaluation.