Is Read down?
Up
No, Read is up.
It passed its latest check 21 min ago in 1.1 s. It has passed every check since 19 Oct 2026, 04:30 UTC.
Latest check
- Last check
- 21 min ago (19 Oct 2026, 10:47 UTC)
- Response time
- 1.1 s (typical 1.1 s)
- Next check
- In about 3 h
- How often
- About every 4 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 4 hours over the last 7 days.
Outages in the last 30 days
No outages in the last 30 days. An outage starts when two checks in a row fail and ends at the next passing check.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 19 Oct 2026, 10:47 UTC | Passed | 402 | 1.1 s |
| 19 Oct 2026, 07:40 UTC | Passed | 402 | 1.5 s |
| 19 Oct 2026, 04:30 UTC | Passed | 402 | 1.2 s |
| 19 Oct 2026, 01:42 UTC | Served content without asking for payment | 200 | 1.8 s |
| 18 Oct 2026, 22:29 UTC | Passed | 402 | 981 ms |
| 18 Oct 2026, 17:53 UTC | Passed | 402 | 1.0 s |
| 18 Oct 2026, 12:51 UTC | Passed | 402 | 1.3 s |
| 18 Oct 2026, 07:39 UTC | Passed | 402 | 964 ms |
| 18 Oct 2026, 02:35 UTC | Served content without asking for payment | 200 | 1.7 s |
| 17 Oct 2026, 21:20 UTC | Passed | 402 | 1.0 s |
Price and payment address
- Price
- $0.003 per call on Base
- Pays to
- 0x9a62…b563
No price or payment address changes recorded.
How we check
Up means the endpoint answered an unpaid test request with a valid x402 payment challenge. We never pay, so we can't see whether the paid response works.
Checks come from our server, about every 4 hours for this listing over the last 7 days. A failure can also mean the service blocks our checks. Two failed checks in a row count as an outage, which ends at the next passing check.
If you think a check is wrong, contact hello@toolvet.app. More on how we check and score. To see what an agent gets right now, check it yourself.