Reports / week to date

This week so far

2026-10-19 00:00 UTC to 2026-10-19 11:30 UTC. Provisional figures for the week in progress, computed just now. They change until the week ends and are not stored. JSON: /api/v1/reports/current

Services from public registries

102,977 services from 23,990 providers, found in public agent registries. 27,404 were probed during the week: 24,399 of 27,581 probes passed (88.5%); 3,182 failed; 283 missed of 506 scheduled.

Across the week, 24,222 passed every probe, 0 passed some, 3,182 passed none, and 75,573 were not probed. Of the 15,198 that answered with a valid x402 payment request, 14,987 offered at least one mainnet network and 211 offered only testnets. 1 stopped being listed by their registry during the week.

Latest result in the week

Payment networks offered

Networks named in live x402 payment requests, by number of services offering each.

Price per call

12,310 services with a valid payment request had a price in a known USD stablecoin: lowest $0.00, lower quartile $0.004, median $0.01, upper quartile $0.02, highest $1000.00.

Payment-terms changes

359 changes to observed payment terms across 359 services: receiving address 169, price 120, network added 66, network removed 14, scheme 3, token 2, x402 version 1.

By purpose

The 15 most common purpose tags. Registry columns are the registry's own figures; payers are summed across services.

Services from our listing files

Hourly checks of services with sourced listings. Changes are detected changes to their monitored pages.

Our own monitoring

12 of 11 hourly runs recorded (0 missing): 12 completed, 0 failed, 0 paused. Checks ran from 1 Cloudflare locations.

How to read this report

• A passing probe of a discovered service means the endpoint answered with HTTP 402 and a valid x402 payment request offering at least one mainnet network: it is reachable and asking for payment. A valid request offering only test networks is counted as a valid payment request but not as a pass. Neither shows that a paid call succeeds.
• Missed checks are scheduled checks that did not run. They are counted separately from failures. Discovered services are probed hourly to monthly depending on usage (schedule/1), and expected probes are counted against the schedule in force at the time.
• Our hourly runs are counted from when our monitoring began, so a week that started before then expects fewer runs.
• The latest-result table counts every HTTP 402 response, whether or not it carried a valid payment request; the headline counts only valid x402 payment requests.
• Services first seen during the week are counted from when we first saw them, so their expected checks cover only part of the week.
• Registry usage (calls and unique payers) is the registry's own figure for the 30 days before its last capture, not our measurement. Payers are summed across services, so a payer who used several services is counted once per service.
• Prices are the lowest per-call price in a known USD stablecoin, from the registry's payment terms at the time of the report.
• Payment-terms changes compare each valid x402 payment request with the previous one for the same service (terms-diff/1): price, network added or removed, token, receiving address, scheme, version. A change can carry several kinds.
• Discovered services are counted as of report generation. Services that opted out of monitoring or were removed are not included.
• This report is a fixed snapshot. Corrections are listed with it and never change the original figures.

Spotted an error? Email hello@agentservicedirectory.com with the report date. Corrections are published with the report.