Wholesale tool data.
Build a product on these tools: one versioned JSON read per tool family gives each tool's price, the credit to keep with its answers, its measured success rate and latency, and the error codes your integration can branch on. Start at https://agent402.tools/api/wholesale/v1.
Families
Each family lists only sources whose answers may be passed on: public-domain government data, CC BY 4.0 weather data with its credit, and our own computation. Keep the family's credit line with every answer you pass on.
| Family | Source | Basis | Tools | JSON |
|---|---|---|---|---|
| Computation tools | our own code; no outside data source | own-computation | 176 | compute |
| SEC filings and company financials | SEC EDGAR (data.sec.gov, efts.sec.gov) | public-domain | 13 | sec-filings |
| US Treasury rates and debt | US Treasury (fiscaldata.treasury.gov and home.treasury.gov) | public-domain | 5 | us-treasury |
| Weather forecasts, history, air quality and risk | Open-Meteo (CC BY 4.0) and the National Weather Service | cc-by-4.0 | 12 | weather |
Price
Every price is the public route's own price, the same for every buyer; there is no wholesale discount. A route priced per request (the bundle products, priced per site, company or coin) lists its range and quotes the exact amount in each 402 from the body you send. Pay per call over x402 or MPP as on the public route; how to pay.
Reliability
Each tool reads measured or not enough data: measured, or not enough data when the tool had fewer than 20 calls in the window (its figures are then null).
Success rate: answers below 400 over answers below 400 plus answers of 500 or above, in the last seven days; a 4xx (the caller's input, a payment refusal) is not counted either way; floored to three places.
Latency: p50Ms and p95Ms: milliseconds inside the server, from the request reaching the tool to its answer, over the same calls.
The same figures, window and threshold as /api/reliability/tools.
Service-wide uptime, measured from outside production, is on /status and /api/reliability.
Error codes
Every tool error answer carries errorCode beside the message. Branch on the code; the message text may change. A paid call that ends in any status of 400 or above is not charged over x402, MPP or a prepaid credits key: settlement runs after the tool and only on a successful response. The exception is a Tempo push credential, a transfer the buyer sent before the call: it settles before the tool runs, so if the tool then fails the payment is recorded as a refund owed to the paying wallet. The refund terms, rail by rail, are at /.well-known/agent402-refund-terms.json.
| Status | errorCode | Meaning | What helps |
|---|---|---|---|
| 400 | invalid_input | The input is missing a field, has a wrong type or is out of range; the message names the field. Fix the input. | fix-input |
| 402 | payment_required | No payment, or a payment that was refused; the body is the payment challenge. | pay |
| 404 | not_found | The thing the input names does not exist at the source. | fix-input |
| 409 | conflict | The request conflicts with one already in progress (for example the same idempotency key with a different body). | fix-input |
| 410 | retired | The route is retired; the body names its replacement. | use-replacement |
| 413 | input_too_large | The input is over a size limit the body names. | fix-input |
| 415 | unsupported_media_type | The body's content type is not one the route reads. | fix-input |
| 422 | input_not_resolvable | The input is well formed but the source cannot resolve it (an unknown ticker, coin or place). | fix-input |
| 429 | rate_limited | Too many requests; wait the Retry-After seconds. | after-retry-after |
| 499 | client_closed | The caller closed the connection before the answer. | same-request |
| 500 | internal_error | A fault in our code. | later |
| 502 | upstream_error | The data source answered with an error or an unreadable answer. | later |
| 503 | unavailable | The tool or its source is unavailable for now. | after-retry-after |
| 504 | timeout | The source did not answer in time. | later |
Stability
This is v1. Within it, fields are only added, never renamed, retyped or removed; a breaking change ships as a new version beside this one. Each tool's input and output schema is in /openapi.json.