BotsRated check — agent-tools.cloud

BotsRated: measured facts for one x402 seller host: probe counts, valid-402 count, latency p50/p90, quoted price and payTo vs listing, paid-test fields, last 5 receipt ids. $0.001 USDC on Base (first 25 per client IP per UTC day free).

Paid verification

How it works

No sponsored paid call yet.

Pay this endpoint once from your own wallet (Base USDC, up to $1.00) and we call it and record what came back. Your wallet pays the listed recipient directly; Agent Tools never holds funds. Sponsored checks prove delivery; they do not count as demand.

Quality grade

How grading works

A 72.6 / 100

Availability 20.0 / 20

Endpoint responded (HTTP 402)

Payability 15.0 / 15

✓ Answers a real HTTP 402 challenge
✓ Publishes a /.well-known/x402 descriptor
✓ Payment address on record
✓ Settlement network declared
✓ Price declared

Demand 10.8 / 35

8 distinct payers, 13 USDC transfers in the last 30 days

Performance 8.9 / 10

Last probe answered in 406 ms (full marks at 200 ms or less)

Readiness 13.0 / 15

Agent readiness 87/100

Owner verified 5.0 / 5

Operator proved control of this domain

Endpoint last checked 19 h ago. On-chain activity last read 3 d ago. Availability and on-chain demand are both re-probed daily; the grade updates automatically on the next pass. This grade sets search order and leaderboards; the readiness score below is shown for reference only.

x402 readiness

B · 87/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here A, 72.6/100), which weighs availability, payability and on-chain demand. How the two differ

Valid payment requirements	10/10	Payment requirements carry a payee, a mainnet network and a price.
Live 402 challenge	25/25	Paid endpoint answers with an HTTP 402 challenge (406 ms).
x402 version	n/a	x402 version not observed yet.
Signed descriptor	n/a	No x402 standard defines a signed descriptor.
Uptime (30 days)	12.95/15	19/22 probes succeeded over 30 days (86%).
Resource declaration	8/10	6 paid resources; 4 sampled lack a description.
Verified identity	8/10	Publisher descriptor (/.well-known/x402 or OpenAPI) on record and domain control verified on agent-tools.cloud (company-registry check not available yet).
Freshness + modern flags	1/5	declares x402.
Security declaration	n/a	Payment is the access control for an x402 resource.

Applicable criteria total 75 points, scaled to 100.

Responsiveness: Responsive (406 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Payment evidence: x402_challenge — We sent a request and got a live HTTP 402 challenge. Also: catalog_listing. Qualifies the payment claim; adds no points.

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily probe of the paid endpoint, its payment requirements and 30-day probe history. Signed descriptor and security declaration are n/a for x402 (payment is the access control), as is an x402 version we have not observed; the remaining points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. It also feeds 15 points of the x402 quality grade.

Compared with peers

Against 10,082 reachable x402 APIs in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness: Higher than 75% of peers; This listing 87 · peer median 78
Latency: Faster than 27% of peers; This listing 406 ms · peer median 205 ms

Where it loses the most points, and how to win them back

Freshness + modern flags −4 — Keep the listing current in the registry or source it comes from.
Now: declares x402.
Uptime (30 days) −2.1 — Stay reachable in our daily probes.
Now: 19/22 probes succeeded over 30 days (86%).
Resource declaration −2 — Declare each paid resource with its input and output schema.
Now: 6 paid resources; 4 sampled lack a description.

How many agent tools actually work · All statistics

Paid endpoints

6 resource(s) advertised by this origin. Each price below is that resource's own x402 price; the headline price is the range across them.

GET https://botsrated.com/v1/check?host=www.blockrun.ai $0.0010 / call

GET https://botsrated.com/v1/check?host=blockrun.ai

GET https://botsrated.com/v1/report/blockrun.ai

GET https://botsrated.com/v1/best?task=web%20search&sort=reliability

GET https://botsrated.com/v1/check

Measured facts for one x402 seller host: probe counts, valid-402 count, latency p50/p90, quoted price and payTo vs listing, paid-test fields, last 5 receipt ids.

GET https://botsrated.com/v1/best

Top 3 measured providers for a task keyword, sorted by reliability, price or latency, with the numbers behind the order.

How to call

Owner interface declaration: verified (checked 1793108216).

cURL · x402-fetch / x402-axios will auto-handle 402

curl -sS -i -X GET 'https://botsrated.com/v1/check?host=www.blockrun.ai'  # expect HTTP 402 Payment Required (about 0.001 USDC/call)

OpenAPI spec

https://botsrated.com/openapi.json

/.well-known/x402.json

https://botsrated.com/.well-known/x402

Listed in

Directories this entry was found in.

submission since 2026-10-23 mcp since 2026-10-23 a2a since 2026-10-23 x402scan since 2026-10-23