Loading
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.
18 x402 payments, paid or received
read 2026-11-01
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
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.
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,451,701 payments only 49,119 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.0180 0.0180 all transfers | — | 18 | 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.
No vault names this address as its strategy, its owner, its curator or its guardian, and no signed declaration claims one for it. That is an absence in what we read rather than a statement that it manages nothing.
Deposits into strategies this address does not run. Kept out of the figure above on purpose: adding capital managed to capital deposited elsewhere counts the same vault twice and credits a customer with their manager’s book.
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 one thing, 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.
0x2ab5a19a…56976661curl -i https://stakechain-api.vercel.app/v1/bestThe 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.
never
18 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.