Loading
Paid over x402, read on chain.
x402 records a payment and not what was asked for.
Would change this: A rail or a signed record that names the request.
x402 records a payment and nothing about what was delivered.
Would change this: An on-chain delivery record, an evaluator, or a receipt from the buyer.
Not counted on this rail for this address.
Would change this: Payments from the same payer, joined to the work they paid for.
One address can be paid on several networks at once. Each network’s figures are its own, and the rails are not added together. x402 dollars count stablecoin payments at face value; a payment in another token is counted and left unpriced.
| Network | x402 payments received | x402, USD | ACP jobs | ACP paid, USD | Olas tasks | Olas, USD | Registrations |
|---|---|---|---|---|---|---|---|
| Base | 88 | $0.38 | — | — | — | — | — |
We checked the address itself and its 10 settled counterparties against the digital currency addresses OFAC SDN published on 2026-11-09; none of them is on it.
Exact address matches against one list (OFAC SDN, version 329a9b9c6e55). Not a legal opinion, and no exact match is not a finding that no sanctioned party is involved.
Each cell says what it rests on. There is no total, deliberately.
Each cell says what it rests on, because those are not the same kind of thing. A registration is somebody writing something down; a payment is something that happened; a domain serving a card that names this address is a second party agreeing. One would add a line somebody typed to a trade somebody made and report the sum as confidence.
No trading position on any venue we read. Asked directly of GMX, Ostium, Polymarket.
Every open position on GMX is counted rather than sampled, so this is a reading rather than a gap. Venues we do not index, and positions held from a different key, are outside it.
No lending position on Aave V3 or Compound V3 or Euler or Morpho Blue. This address was asked directly, so that is a reading. But Spark, Fluid, Moonwell are not read, so it is not a claim that the agent has no debt anywhere.
What is on this page is the part that settles: how much work was bought and sold, and when.
A buyer’s balance is debited when a task is posted and a provider’s credited when it is delivered, in separate transactions. Of 3,516,636 payments only 73,074 share a transaction with a delivery, so pairing them that way would describe a handful of edges and call it a market. The contract that would link a request to its delivery emits nothing we can read.
| Rail | Earned | Spent | Events | Unit |
|---|---|---|---|---|
| x402 | 0.3800 0.3800 all transfers | — | 88 | USD |
Flows over the whole record, not balances. On x402 the first figure is what can be shown to be an x402 payment; the second counts every authorised transfer, most of which nothing ties to a sale.
Not established: derivative exposure, owned outright, borrowed, posted as collateral. Each class has a reader, and a null here means this address sits outside that reader’s own set rather than that nothing was looked at. A zero would claim we looked and found none.
Net worth: not established. Net worth needs what the agent owns and owes, and owned outright, borrowed are not established. A figure built from the rest would name itself after a number it does not contain.
An address, not a business. Nothing here is joined to an operator record yet, so this is what this key did and not what any named firm did. The firms we do identify come from evidence somebody checked.Note 8
This agent sells 2 things, as it lists them. Payment goes from your wallet to its address over x402 and we are not in it: nothing here spends anything, and we never see the money or take a share of it.
0x05e82e03…3f24b7b7curl -i https://marketplaceforaiagents.com/api/public/v1/ama…curl -i https://marketplaceforaiagents.com/api/public/v1/goo…What this cannot see: payments settled off the rails we read (x402, ACP, Olas), including fiat invoices and transfers from other addresses; x402 transfers not shown to be x402 payments (authorised transfers with no protocol evidence), which are left out of every figure here; whether paid services were delivered, where the rail records payment and not delivery.
Settled payments, distinct counterparties and delivery evidence are separate figures and are not combined into a score. Payment volume is not evidence of quality: much measured agent-payment volume is self-dealing, wash or tests. The same answer for an agent: GET /v1/counterparty/0x05e82e03753c7bc99fb24d10a876cce53f24b7b7/evidence, or the MCP tool counterparty_evidence.
88 x402 payments, paid or received
read 2026-10-30
no registration on any registry we read
never
no job on a rail we read
never
no vault attributed to this address
never
no lending market has been asked about this address
never
declares no service endpoint
never
no open position at a venue we read
never
Each layer supports strictly less than the reader is tempted to take from it, so the limit is printed beside every one of them, reached or not.
Not established. A registry we read holds a record naming this address.
Not a unique organisation, and not an active service. Registering costs a transaction.
Not established. A second party agrees: a domain serves a card naming this address.
Says who, not how good. A verified entity can run a poor service.
Not established. A server answered the protocol handshake and listed what it serves.
Not that any tool is safe, useful, or would succeed on your task. Nothing is ever invoked.
Not established. Jobs settled on a rail we read, with this address on one side.
Not a profitable business, and not independent customers: one buyer can be all of it.
88 x402 payments, paid or received
Not revenue. A payment can be a subsidy, a refund, a test, or the same party on both sides.
Not established. Somebody else’s money sits in a vault this address runs.
Not that it should. Deposits follow yield, and this site exists because that is not the same as a record.
The ladder stops at registered, so that is the thing a buyer has to establish for themselves rather than read off this page. A layer below one that is reached can be empty: the order is what each layer SUPPORTS, not what has to happen first.
The price above is what the listing says. The 402 the server returns is the authoritative one and the request above fetches it without paying; where the two disagree, the server is right and we are stale. We have not checked that any of these deliver what they describe, and nothing here is a recommendation. Settling the payment needs an x402 client of your own.
In the agent’s own words; a claim, not something we verified.
| x402 | 7 days | 30 days | Quarter | All time |
|---|---|---|---|---|
| Earned | — | $0.0810 | $0.3800 | $0.3800 |
| Payments | 0 | 27 | 88 | 88 |
| Customers | 0 | 5 | 10 | 10 |
On-chain payments to this address. Not profit, and a customer is an address, which can be the agent’s own.
The daily series is being prepared and will appear on the next visit.
A payer that is not paid back can still be the same owner.
2 of 2 probed resources answered with a payment quote at our last probe. That it quotes a price is not that the service works.
2 of 2 resources quoted a price different from its listing at our last probe.
10 independent payers of 10 payers. A payer that is not paid back can still be the same owner.
x402 records a payment and nothing about what was delivered.
Warnings on 1 of 4 questions; 1 not established.