Loading
Every market this platform reads, and every market it does not, with the reason for each. The rows that claim coverage carry the live count that proves it; the rows that claim nothing carry the reason instead.
Most of what is missing here is missing from everybody. Card rails, bank transfers and centralised-exchange trading are not gaps in this dataset — they are markets no independent party can measure from public data. Stating that is more useful than estimating it, and an estimate would be a guess wearing a decimal point.
What agents control, and where we can and cannot see it.
Positions, fills, margin and equity come from the venue’s public Info API into our own store. The venue is not treated as an archive: the history below is ours, and would survive the endpoint being withdrawn.
Read from contracts and events on chain, with the protocol APIs used only for discovery. Share price, flows and underlying exposure are reconstructed rather than taken from a dashboard.
Concrete, Lista, Lagoon, Veda, ether.fi Liquid, Upshift, Makina, Krystal and twenty more, each read at vault level rather than as a protocol total. A protocol TVL figure cannot answer a question about one strategy’s risk.
Vault state and curator attribution from Kamino’s public data. Classified as software-managed allocation: automated rebalancing is not evidence of an AI deciding anything.
Depositor-level holdings where the venue exposes them, which is what concentration and redemption pressure are actually made of. A vault’s size says nothing about how fast it can be emptied.
Equity is computed for every vault we can decode and published for none of them. The decode cannot be checked against the chain — the market’s token account holds nothing, and net deposits match no field in the account struct — so the figure is stored and waits for an external comparison against the venue’s own published return.
The accounts are on chain and readable. Which of them an agent platform operates is not, without an address list from that platform — so their balances are not counted as agent-controlled capital.
We measure the on-chain leg. Exchange exposure, off-chain derivatives, hedges and unregistered accounts stay invisible, so every risk figure here is a floor on the risk taken and never a complete picture.
Positions, balances and execution live inside each exchange and are never published. No independent party measures this, and an estimate would be a guess wearing a decimal point.
What they buy and sell, and which rails settle out of sight.
Settlement indexed directly from Base and Solana rather than through a third-party tracker, so the normalised history is ours. What the log proves is that a transfer was authorised — not that software authorised it.
Requests, deliveries, providers and fees from marketplace contracts. Chain shares here describe the covered Olas sample in a stated window, and are not a statement about the agent economy at large.
The commercial lifecycle from public events: client, provider, evaluator, budget, settlement, rejection and expiry. Deliverable contents are private and are not inferred from a job succeeding.
What they claim about themselves, and what a claim is worth.
Registration events across every chain where the registry is deployed, with the deployment itself checked rather than assumed. A chain whose endpoint refuses a historical call is recorded as unreadable, not as empty.
Both registries beyond identity are read. The feedback is not a crowd — on the best-covered chain the entire rating population is a handful of accounts — so it is described rather than averaged into a score.
Registered identities with their declared wallets and endpoints, which is what makes later Solana activity attributable at all.
Coverage counted in dollars rather than in platforms, with the backlog ranked by the factors that decide what is worth building next.
Almost none of the unread capital is unread because nobody built it. Capital staked into a distribution contract has no strategy to measure, and a platform that gives every customer a smart account of their own has no shared contract with a share price. Publishing those as strategies would inflate the perimeter with things that are not strategies — which is the exact failure that ranking by platform count produces. 16 platforms have never had their size established, and unknown is not zero.
| Platform | Capital | Score | What stands in the way |
|---|---|---|---|
Theoriq agent-native | unknown | 9/15 | One vault on Ethereum, not Base as previously recorded. It implements neither ERC-4626 nor ERC-20, so its balance cannot be read the way every other vault here is; the address is registered and the reading is not done. |
Comparing our figures against what other sources publish is a different question, and it has its own page: us vs other sources.
Escrow creation, settlement and refund from transactions and datums. One Cardano transaction can carry several application actions, so chain transactions, payment actions and jobs are counted as three separate things.
Channel opening, use and closing. A channel is a relationship rather than a payment, and is never added to a payment count.
Coinbase’s discovery service lists what sellers say they offer. A listing is a claim, exactly as a registration is, and it is stored apart from payments so the two can be joined — which is how “listed” becomes “has ever earned anything”.
A specification is not a market. Nothing enters an economic total until a deployed contract, a network, an observation window and the meaning of its events have all been verified.
Transaction data is shared among Visa, agents, merchants, issuers and approved participants. There is no public market-wide feed to index.
Runs on closed payment infrastructure. Nothing about individual transactions is published.
The records belong to the relevant Stripe account, platform and merchant. Access requires their consent, one account at a time.
Banking and open-finance data requires customer consent and commercial access, per customer. No aggregate view of this exists for anyone outside the banks.
Any share requires a denominator, and the card, banking and off-chain rails that would form most of it are absent from public data. We publish what settles where we can see it, and never a percentage of a total nobody can measure.
Signed, versioned and never deleted, including after a strategy fails or closes. A declaration that vanished on failure would rebuild the publication bias the register exists to remove.
Model identity is not recorded on chain and cannot be inferred from execution. Known only where an operator signed a declaration naming it — which is one of the reasons the declaration register exists.
Private off-chain data. We hold hashes where an operator supplied them, which can show the instructions did not change and proves nothing whatever about what they say.
An agent framework produces ordinary protocol transactions and adds no marker. A transaction cannot be traced to the software that composed it, so any count of “built with X” would be invented.
Infinite Trading Protocol agent-native | $232,929 | 8/15 | We have not established whether a readable vault exists here. |
Yield AI agent-native | $42,946 | 8/15 | We have not established whether a readable vault exists here. |
Mind Network agent-native | $29,079 | 8/15 | We have not established whether a readable vault exists here. |
Gud.Tech agent-native | $24,744 | 8/15 | We have not established whether a readable vault exists here. |
TermiX agent-native | $3,940 | 8/15 | We have not established whether a readable vault exists here. |
Calculus agent-native | $3,320 | 8/15 | We have not established whether a readable vault exists here. |
Glorb agent-native | $779 | 8/15 | We have not established whether a readable vault exists here. |
Vaultfire agent-native | $40 | 8/15 | We have not established whether a readable vault exists here. |
ZyFAI agent-native | $10m | 7/15 | Every user gets their own smart account and the agent rebalances inside it, so there is no shared vault with a share price to read. Their own API publishes capital and flows for the whole platform, which is what we carry; a list of fifteen thousand user wallets would not be a list of strategies. |
Finder Bot agent-native | unknown | 7/15 | We have not established whether a readable vault exists here. |
Cookie DAO agent-native | unknown | 7/15 | We have not established whether a readable vault exists here. |
Five factors, not seven. Measurable capital, whether an independent reading is possible, execution transparency, relevance to autonomous decision-making and engineering cost are all computable from what we already hold. Historical depth and the uniqueness of the analysis we could produce are the other two the method calls for, and neither is knowable until a platform is integrated. Folding a guess at them into the total would make it look exactly as objective as the five real ones, so they are named and left open instead.
The difference between the last two and the rest is not difficulty. It is that the records exist only inside a closed system, and reach an outsider — if ever — through a commercial agreement rather than through measurement. Treating that as a gap in our coverage would be the same error as reading an unreachable chain as an empty one, which is a mistake this codebase has made and corrected four separate times.