BotsRated
Paid API · botsrated.com · found in a public list · checked since 2026-10-23
Client error (4xx) · latest check
Returns the full payment and measurement history of one seller host, receipt by receipt.
Our summary of what its own text says it does: automated, not reviewed by a person (placement-ai/6). What this means
Placed in Verify AI agents: Identity, reputation and track-record checks on AI agents and agent sellers.
GET https://botsrated.com/v1/report/:host$0.005 per call · from the registry's payment termsThe name is the registry's label, not ours. Not reviewed by a person. See 4 endpoints from botsrated.com. The URL contains placeholders (such as :address) that callers fill in. We check it with a sample value of the right form in each placeholder (a documentation value such as example.com, a null value such as the zero address, or a common sample such as 1), and each check records the address we requested. If the service rejects that address (400, 404, 410 or 422), the check is recorded as "couldn't test as listed": neither a pass nor a failure, and left out of pass rates.
Our checks
An unpaid request daily, from eastern North AmericaLast 2 checks, oldest to newest; room for 28 more
1 passed, 1 failed, 28 not run.
Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.
Response times
| Window | Checks | Timeouts | Median | 90th | 95th | 99th | Fastest | Slowest |
|---|---|---|---|---|---|---|---|---|
| 24 hours | 0 | 0 | — | — | — | — | — | — |
| 7 dayssince 2026-10-23 | 1 | 0 | — | — | — | — | — | — |
| 30 dayssince 2026-10-23 | 1 | 0 | — | — | — | — | — | — |
Milliseconds, from eastern North America, timing an unpaid request answered with a payment request (HTTP 402). Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.
Details
Payment terms
- Price per call
- $0.005
- Protocols
- none seen yet
- Networks
- eip155:8453
- Terms changes, 90 days
- 0 in 2 days tracked
Price from the registry's payment terms; protocols and networks as the registry states. Current terms first seen 2026-10-23; 0 receiving-address changes. Definitions
Reported by the registry
- Payers, 30 days
- 1
- Paid calls, 30 days
- 1
The registry's own figures, not our measurements.
Access
- Our latest check
- not observed
- Stated
- not stated
- Payment model
- not known
- Currency
- USD (USDC, in its payment terms)since
"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions
What it says about itself
- Takes
- Seller host namefrom its listing's description, read 2026-10-24
- Returns
- Every receipt with timestamp, status, latency and hashesfrom its listing's description, read 2026-10-24
From the service's own text, put in short words by a small AI model and shown only where its own words support it (stated-facts/2): its claims, not checked by us. Anything not listed, it does not state. Definitions
Calls it declares
GET
From the payment request it sent our check (request-shape/1). * marks a required parameter; after → the fields it says it returns. What it declares, not that a call works.
Listing
In the capability tree: Identity, security and compliance / Verification / Verify AI agents (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/6, tree/3) on 2026-10-24. Wrong place? Tell us.
In the index only: does not meet every one of our listing criteria (listing-criteria/6): ✓ says what it does; ✗ its latest check did not pass.
Purpose tags: x402trustratingsmonitoringagents
Recent probes
We check it with a sample value of the right form in each placeholder (a documentation value such as example.com, a null value such as the zero address, or a common sample such as 1), and each check records the address we requested. If the service rejects that address (400, 404, 410 or 422), the check is recorded as "couldn't test as listed": neither a pass nor a failure, and left out of pass rates.
| When | Result | Networks offered | Time to headers |
|---|---|---|---|
cloudflare:MIA |
Client error (4xx) HTTP 400 expected 402 payment challenge |
— | 2749 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 196 ms |
What these figures do not show
- A passing probe means the endpoint answered an unpaid request with a valid payment request on a production network (x402 on a mainnet network, or MPP on Tempo mainnet). It does not show that a paid call succeeds or returns useful results.
- Payer and call counts are the registry's own figures, not our measurements.
- The registry's description is not republished.
- Limited evidence: monitored for 2 days (less than 30).
Something wrong here?
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.
Machine-readable: /api/v1/services/cand_00541f25190be439