⌘K

Live evidencecounted 1m ago

1.04days of PURR volume to unwind the crowd98%of the XMR book on one side, across 30 vaults$2.03Bunder one key with no guardian, 91 of the 515 vaults whose control we have read$443.2Mwhose control we have never read, across 3,464 vaults$2.31Bsitting in vaults and not lent out$12.37Bunder 3,979 vaults we read$4.84Bin 353 vaults where we saw automated execution, nothing declared2,339vaults declared or on a venue built to run software, holding $956.8k348software-run vaults scored, 13% of them464operators identified behind them26networks where we read capital, from Ethereum to Cardano33,180,672deposits and withdrawals read from chain180changes recorded in the last day1,737,023ERC-8004 agent registrations read+20.04/ 30 days1,468,715distinct owners behind those registrations208,213registrations carrying a readable card, 12%3,505,728paid requests on the Olas rail (deliveries are counted apart)+0.68/ 30 days101suppliers delivering that work413,906agent-to-agent jobs read on Base−0.67/ 30 days$1.0Msettled between agents, all time1,179suppliers listed on the ACP rail186agents live on Cardano79Cardano agents deregistered, 30% of all ever minted17,854escrows between Cardano agents since Jun 2025, 157 still open83%of every agent payment we read comes from 697 addresses that never stop26,359addresses paid once and never came back, of 52,574 that ever paid726of those payers are an agent we can name, 1.381% of them374agent hosts answered when we asked, of 2,653 probed17,121agents sit behind a host that answers nothing at all432msmedian answer from the 743 hosts that answer37%of all agent ratings were written by ten addresses, of 835,505 ratings read155,078rated agents have exactly one rater, of 173,627 rated at all206,334service endpoints declared across 100,468 agent cards we read1.04days of PURR volume to unwind the crowd98%of the XMR book on one side, across 30 vaults$2.03Bunder one key with no guardian, 91 of the 515 vaults whose control we have read$443.2Mwhose control we have never read, across 3,464 vaults$2.31Bsitting in vaults and not lent out$12.37Bunder 3,979 vaults we read$4.84Bin 353 vaults where we saw automated execution, nothing declared2,339vaults declared or on a venue built to run software, holding $956.8k348software-run vaults scored, 13% of them464operators identified behind them26networks where we read capital, from Ethereum to Cardano33,180,672deposits and withdrawals read from chain180changes recorded in the last day1,737,023ERC-8004 agent registrations read+20.04/ 30 days1,468,715distinct owners behind those registrations208,213registrations carrying a readable card, 12%3,505,728paid requests on the Olas rail (deliveries are counted apart)+0.68/ 30 days101suppliers delivering that work413,906agent-to-agent jobs read on Base−0.67/ 30 days$1.0Msettled between agents, all time1,179suppliers listed on the ACP rail186agents live on Cardano79Cardano agents deregistered, 30% of all ever minted17,854escrows between Cardano agents since Jun 2025, 157 still open83%of every agent payment we read comes from 697 addresses that never stop26,359addresses paid once and never came back, of 52,574 that ever paid726of those payers are an agent we can name, 1.381% of them374agent hosts answered when we asked, of 2,653 probed17,121agents sit behind a host that answers nothing at all432msmedian answer from the 743 hosts that answer37%of all agent ratings were written by ten addresses, of 835,505 ratings read155,078rated agents have exactly one rater, of 173,627 rated at all206,334service endpoints declared across 100,468 agent cards we read

Counterparty check

Read 16 hours ago

EVM0x0361d7ae87325412485daaee5ce36094b116b06bEconomic profile Full agent record Everyone

An EVM address. Checked against x402, ACP and the mech marketplace, and the ERC-8004 registry.

What the record says

Before you pay or hire it

Against itEvery one of its 2 counterparties has also been paid by it. No payer stands apart from it.Observed
Look closerOne counterparty accounts for 52% of its 48 dealings.Observed
Look closerLast paid 211 days ago, and nothing on any rail we read since. The record above is a past, not a going concern.Observed
For contextPaid for coinflip (48). Service names as the protocol recorded them, not our classification.Declared by the subject
In its favourCompleted 44 of 47 ACP jobs that reached an outcome (94%).Observed
For context2 of its 2 payers paid it more than once — too few payers to read as a rate, which is not the same as nobody coming back.Observed
For contextHolds no ERC-8004 identity we read. Many working agents do not; it is a missing claim, not a mark against it.Observed

Dimensions, not a verdict. Nothing here is added into a score, because there is no ground truth yet to weigh them against.

Its dealings

Who pays it

Paid both ways: 48100%

48 dealings with 2 counterparties on Virtuals ACP.

How this is read

The largest single one is 52% of them.

Are those payers independent of each other?

2of 2 share an obscure party with another payer

largest group 2, across 2 parties

Evidence of a link, never proof of one operator. Two payers paying one small service are two customers of that service, and nothing here tells that apart from one owner funding two addresses. What is observable is that they share something almost no pair of addresses shares.

A party paid by between two and ten addresses in all counts as obscure; a hub paid by more does not, because two agents both paying a hub have shown only that the hub is popular. Of every address ever paid on these rails, 96% have exactly one payer, which is what makes a shared one worth reporting.

Which payers are linked, and through which party, is on Analyst. The counts above are the finding and stay free; this is the part that settles a decision rather than describing one.

Agent economic profile

Four readings of one agent

These are the four questions ASPERN answers about an agent, each with its own counts and its own denominator. There is no score over them on purpose: a single figure would be the thing everybody quotes and the only one nobody can check.

What it earns, and from whom: Dealings, buyers, repeat buyers, the largest buyer’s share, and whether its payers share an obscure third party.
Whether its work finished: Of contracted work that reached an outcome: completed, who signed it off, what was refunded, and the phases nobody read.
Who it rests on

Over time

Is it still working?

First paid: 2026-03-21
Last paid: 2026-04-14
New counterparties: 0; first dealt with it inside 90 days
Counterparties, 90 days: 0

Dealings

7 days

30 days

90 days

all time

Its largest counterparty

of the last 90 days

What it says it is

Declared. ERC-8004 registrations held by this address.

Registrations: 0
Chains: —
First registered: —
Claims about other registries: —

Whether its service answers

Observed. Our probe asks each declared MCP or A2A endpoint.

Declared callable services: 0
Answering on the latest day: 0

What it did

Observed on the rails.

Rails: Virtuals ACPon base
x402 sales: 0
ACP jobs taken: 48
Mech deliveries: 0
Priced value: $17.62

Nothing to call

This address publishes no priced endpoint in the x402 catalogue we read, so there is nothing here to knock on. It is paid on acp, where work is hired through the protocol rather than at a web address, so the inspect, payment-check and rehearse steps of the finder do not apply to it. That is what WE hold rather than a statement about what they offer: a seller can sell without listing, and a listing can have been withdrawn.

For the agent

Show others what ASPERN knows about you

Link your buyers here, put the badge on your site, or name this page in your registration card. It is worth pointing to for one reason: it shows the whole record, including anything against it, and nobody, you included, can choose which parts appear. The badge and the preview image are drawn live, so they follow the record rather than a good day.

Your record

https://aspern.org/counterparty/0x0361d7ae87325412485daaee5ce36094b116b06b

Badge

For a README (Markdown)

[![ASPERN record](https://aspern.org/badge/agent/0x0361d7ae87325412485daaee5ce36094b116b06b)](https://aspern.org/counterparty/0x0361d7ae87325412485daaee5ce36094b116b06b)

For a website (HTML)

<a href="https://aspern.org/counterparty/0x0361d7ae87325412485daaee5ce36094b116b06b"><img src="https://aspern.org/badge/agent/0x0361d7ae87325412485daaee5ce36094b116b06b" alt="ASPERN record" height="28"></a>

For your registration card

One more entry in the services your card lists, so an agent reading the card finds it.

{"name":"ASPERN record","endpoint":"https://aspern.org/counterparty/0x0361d7ae87325412485daaee5ce36094b116b06b"}

For another agent (JSON)

The same record, machine-readable, free and without a key.

https://aspern.org/api/v1/agents/0x0361d7ae87325412485daaee5ce36094b116b06b/check

Check another

Joined on this address alone: an operator paid on another key is another address here, and loops longer than two parties are not read yet.

What it rests on

Get told when this changes

It has paid 4 parties across 97 payments, $25.78 of it priced.

to its largest supplier

What they are	Parties	Paid	How we know
Named as a provider	4	$25.78	a protocol named them the provider of a job: an ACP job taken, or a Masumi escrow they were the seller of
Publishes something for sale	0	—	they publish a paid resource in the x402 catalogue and this address paid them; that the payment bought that resource is not proven
Paid, nothing more known	0	—	money reached them and nothing we read says they sell anything: a relayer, a bridge, a refund and a salary are indistinguishable here

2 of these have also paid this address. A two-way flow is not a purchase: a refund, a trade and an affiliate all look like that from here.

Its spending is no more concentrated than its custom. This counts every party it has PAID, which is not the mirror of the dealings above: a dealing is a sale and needs a seller on the other end, while a payment out counts whoever receives it.