| meta | No | How current this answer is and what it was read from: `freshness` and the ages behind it. Present on every answer from this server, whatever the tool. | |
| says | Yes | How much of the question we could answer, and which parts we could not. | |
| limits | Yes | The four conclusions the data invites and this refuses. An ADDRESS is not a customer (one customer can hold twenty). A PAYMENT is not a delivery (the busiest agents settle on rails that carry money without carrying a job, so “no delivery record” there is our reach and not a finding). A SHARED FUNDER is not an identity (an exchange funds thousands of strangers), so a link is published as demonstrated or as merely co-occurring and the second is never promoted. A COST we cannot see is not a cost that is not there. | |
| address | Yes | The agent this is about, read back. | |
| answers | Yes | One per question: `asks` in a person’s words, `answered` as measured/partial/unmeasured, `says`, and the `figures` behind the sentence so you can do your own arithmetic. Measured once and not refreshed since, on two live agents: one takes $2,388 a month from 4,772 payers of whom 97% are repeat, the other $932,414 from 7,220 payers of whom 12% are — two completely different businesses that a counterparty count reports identically. | |
| commerce | No | Settled, of that service-linked, of that delivery-evidenced, nested and never added; plus the payments whose rail cannot evidence delivery (x402). Read `says` before quoting any of them as revenue. SINCE 2026-10-28 `settledShownToBeX402` and `rails.x402.usdShownToBeX402` sit beside `settled` and `rails.x402.usd`, which count every authorised transfer: the ShownToBeX402 figures count only payments shown to be x402. Quote those as x402. | |
| coverage | Yes | How many of the six are measured, partial and unmeasured. A count, never averaged into a grade. | |
| evidence | No | The common payment record (TODO-07): `state: built` with `facilitator` (who submitted, never credited), `onChainRecipient`, `listedPayee`, `facilitatorIsRecipient`, `recipientIsListedPayee`, `settlement`, `delivery`, `deliveryEvidence`, `says`; or `state: not-applicable` with `says` naming why no single payment is described. | |
| warnings | No | Anything the server wants a caller to know about THIS answer before acting on it. Empty is the normal case and is not a guarantee. | |
| recordAsOf | No | When the nightly record behind most figures was computed. The revenue months are read live. | |
| economicChain | No | SINCE 2026-10-11. The four links of the chain an agent has to complete to be a working economic subject: a customer paid it, it ordered or did work, the result was demonstrably delivered, a customer came back. Each link is `evidenced`, `unevidenced` (we read the rail and found nothing — a statement about the agent), `unread` (THE RAIL RECORDS IT AND WE DO NOT READ IT — a statement about us, and the only one of the four that closes by our building something) or `unevidenceable` (the rail does not record it at all, so no reading by anybody will change it — a statement about the rail). Those three silences are never folded together, because they call for three different acts. Masumi settles work through an escrow whose release or refund is on chain, and SINCE 2026-10-11 WE READ IT: a release to the seller is the buyer letting the escrow go, which is the closest thing to an accepted delivery this chain can show, and it counts alongside an ACP completion. A CLOSURE does not count — over all 29,088 settled escrows at the time this was measured once, 5,819 refunded to the BUYER against 4,659 released, so counting closures would publish a refund as delivered work more often than not. An agent whose escrows the step reader has not walked yet is `unread` rather than `unevidenced`, per agent, because the chain carries the answer and we have not asked for that one. THE FOURTH STATE is the one to read carefully: x402 is 91% of the volume and records payment, never delivery, so for an x402-only agent link three is unevidenceable and reporting it as missing would blame the agent for the rail. NO SCORE: the worst link governs, because averaging lets a strong payment record carry an absent delivery record. Measured once and not refreshed since, over all 3,135 addresses we held then: paid 3,048, hires 432, delivered 684, returned 2,412, and **185 with all four**. | |
| answeredStates | No | What measured, partial and unmeasured each mean. | |