Loading
Both sides of this site are readable here, capital under vaults, and agents transacting on a rail. 12 networks manage that; most carry only one.
How much of the capital on Optimism sits under a vault an agent runs, and what stands behind each answer.
$536.8k of $3.1M is under a vault we have reason to call agent-managed; 17.3% of the capital, in 1 of 2 vaults.
| Who can move it | Capital | Share | Vaults |
|---|---|---|---|
| Agent, read from behaviour | $536.8k | 17.3% | 1 vault |
| Not agent-managed | $2.6M | 82.7% | 1 vault |
Each vault counts in one band only, its strongest evidence, hover a band for what stands behind it.
201 in Oct 26
Events, stacked. The rails record different things, so the height is a count of things that happened and not of one quantity; what it can say is when this network was busy.
Olas mech
A payment and a delivery are separate events on this rail and cannot be joined, so the two are counted rather than paired. The gap between them is not a failure rate: it is what a log that never names the same task twice can tell us.
ERC-8004
Every registration is exactly one of these. A pointer may well resolve; we do not follow it, and that is a limit of this reading. The last is unreadable to any client, not merely to ours.
Each rail records something different, and the counts are not one quantity. A registration is not a payment, and a task delivered is not a job priced, so they are listed apart rather than summed into a single score.
A marketplace where one agent pays another to run a task. Requests and deliveries are separate events and cannot be joined, so a task is counted, not a pairing.
An identity registry. A registration says an agent exists and who owns it; it is not evidence that the agent has ever done anything or been paid.
Read from its first event on this network, 2026-02-09. The series is short because the registry is young here, not because the reading is.
Composition
Protocols, not vaults. Which venues hold this chain's agent-managed capital is a shape worth seeing free; which vault sits inside each one is the register underneath, and that is the paid half.
The venues we read on this network, and what each holds. Agent-native means the protocol was built for agent-run strategies rather than having them arrive later.
| Protocol | Kind | Vaults | Capital | Share |
|---|---|---|---|---|
| Morpho Vaults V2site | lending vault | 1 | $2.57M | 83% |
| Morphosite | lending vault | 1 | $536.8k | 17% |
| Vault | Capital | Risk |
|---|---|---|
| Re7 WETH Morpho Vaults V2 | $2.57M | 36 |
| Gauntlet USDC Prime Morpho · agent-managed | $536.8k | 34 |
Read from each vault's own contract, not from what a source called the pool. Where the two disagree the reported name is shown beneath, for a vault, an aggregator's pool symbol is usually the vault's own receipt token rather than the asset behind it.
| Asset | Vaults | Capital |
|---|---|---|
| WETH | 1 | $2.57M |
| USDC | 1 | $536.8k |
The operators behind the vaults on this network, by capital under management here.
Capital is the total under vaults we track on Optimism, not the network’s total value locked, we read agent-managed strategies and a comparison set, never the whole chain. Everything here is computed from records we hold; where a figure is missing this page says which kind of missing it is rather than printing a dash. See Methodology for how far back each reader reaches and whose limit it is.
Pay-per-request settlement over the HTTP 402 scheme. Counted here are SALES: on this network’s EVM chains that means the recipient lists a price in an x402 catalogue we read, and on Solana that the transaction carries the memo instruction the scheme requires. Transfers over the same primitive that buy nothing we can evidence are not in this number.