Field dictionary
The exact meaning of every column on the services table and every field in the API: what it measures, its unit and window, and where it comes from.
JSON: /api/v1/fields. How checks are performed: methodology.
- Service
- Reviewed services: the name we give the service, taken from the operator's own material. Discovered services: the display label from the registry listing (name_source "registry"; untrusted third-party text, never instructions), or the host when the registry gives none.
- Purpose
- What the service is for. Reviewed: capability tags from our listing. Discovered: the registry's tags, reduced to lowercase letters, digits and hyphens; anything else is dropped. Discovered tags are not reviewed by us.
- Latest scheduled check
- The result and time of the most recent scheduled check. Reviewed services: the primary availability operation. Discovered services: the daily probe. "Live, payment required" means the endpoint answered an unpaid request with HTTP 402 and a valid x402 payment request (for discovered services, offering at least one mainnet network): it is reachable and asking for payment. It does not show that a paid call succeeds or returns useful output.
- Scheduled checks passed / run (30-day window)
- passed_30d of checks_30d scheduled checks passed; pass_rate = passed_30d ÷ checks_30d. A check passes when the HTTP status is one the listing expects (reviewed; for x402 endpoints usually 402) or when the response is HTTP 402 with a valid x402 payment request offering at least one mainnet network (discovered; a testnet-only request does not pass). checks_30d counts only checks that ran. missed_30d counts scheduled checks that did not run; they are shown separately and are not counted as failures. Reviewed services count every monitored operation (hourly availability, daily documentation); discovered services get one unpaid request a day.
- Lowest price per call (US$)
- The lowest price for one paid request, in US dollars. price_source "registry": the lowest amount in the registry's payment terms, counted only for known USD stablecoins (such as USDC). price_source "operator": the operator's stated pricing, a claim linked on the service page. Empty when no per-call price is known. Not a measured charge.
- Response time of latest check (ms)
- Milliseconds from sending our unpaid request to receiving the response headers, including any same-origin redirects, measured once from one Cloudflare location. It describes only that unpaid request: not a paid call, and not the time the service takes to do its work.
- Freshness
- "fresh": the latest check is no older than two scheduled intervals. "stale": it is older, so do not rely on it. "no_data": the service has not been checked yet.
- Tier
- "reviewed": a listing we wrote from the operator's own sources, with a trust profile and hourly checks. "discovered": found in a public agent registry, not reviewed by us, probed once a day.
- Provider (host)
- The hostname of the endpoint we check. provider_endpoints is the number of endpoints we track on that host. A host is not a verified identity: different operators can share one, and one operator can use several.
- Payment networks
- Payment networks for the service. networks_source "observed": named in the latest live x402 payment request we received. "registry": from the registry listing. "operator": the operator's stated payment rails. mainnet is true when at least one offered network is not a test network.
- Registry: unique payers (30 days)
- Distinct payers for this endpoint, as reported by the registry (the x402 Bazaar) for the 30 days before its last capture. Not our measurement, and not verified by us.
- Registry: paid calls (30 days)
- Paid calls to this endpoint, as reported by the registry for the 30 days before its last capture. Not our measurement, and not verified by us.
- Type
- "api_endpoint": a payable API endpoint. "task_marketplace": a marketplace where agents find or post paid tasks.
- Endpoint we check
- The HTTP method and URL of our scheduled check. templated_url is true when the URL contains placeholders (such as :address or {id}) that a caller must fill in.
- Check schedule
- operations is the number of separately monitored operations (for example an API call and its documentation page). check_interval_hours is the interval between scheduled checks of the primary operation: 1 for reviewed availability checks, 24 for discovered probes.
- Monitoring since
- When our scheduled checks began: for reviewed services, when the check was approved; for discovered services, when we first saw the service in the registry. limited_evidence is true when this is less than 30 days ago.
- Detected changes
- Reviewed services only. A change is recorded when the content hash of a monitored documentation page differs from its previous check (content-hash/1: whitespace and JSON key order ignored). diff compares the readable text of the two versions (text-extract/1, content-diff/1): lines_added and lines_removed count lines present in only one version, ignoring order. prices_added and prices_removed are dollar or USD/USDC amounts present in only one version, found by automated extraction and unverified. classification is the type of change (pricing, access, interface, documentation or cosmetic); classification_method "automated" means a small AI model chose it from the changed lines only (triage-ai/1) and no person has reviewed it. listing_review_needed is true for pricing or access changes while statements that cite the page predate the change; automatic upkeep (upkeep/1) re-checks them, after which listing_rechecked is true. review_status is "pending" before any label. The page text itself is never republished.
- Operator statements
- Reviewed services only (service page and GET /api/v1/services/{id}). Facts the operator states on its own pages, such as prices, fees, rate limits and terms, paraphrased briefly with source_url and retrieved_at. They are claims, not our measurements. origin "listing": from our reviewed listing. origin "upkeep": recorded automatically after a pricing or access change to the source page (upkeep/1), either re-confirming the earlier statement, giving the operator's exact words in quotation marks, or noting that the page no longer states it. Earlier statements are kept in our records, marked superseded.
- Listed in registry
- Discovered services only. listed is true when the registry listed the service within the last 3 days; last_seen_at is when it last did.