Is Identity Records Export Semantic Parity down?
Up
No, Identity Records Export Semantic Parity is up.
It passed its latest check 3 h ago in 224 ms, and every check since we started checking it on 15 Oct 2026.
Latest check
- Last check
- 3 h ago (17 Oct 2026, 07:21 UTC)
- Response time
- 224 ms (typical 255 ms)
- Next check
- In about 2 h
- How often
- About every 5 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 5 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 |
|---|---|---|---|
| 17 Oct 2026, 07:21 UTC | Passed | 402 | 224 ms |
| 17 Oct 2026, 02:36 UTC | Passed | 402 | 218 ms |
| 16 Oct 2026, 21:49 UTC | Passed | 402 | 3.8 s |
| 16 Oct 2026, 17:08 UTC | Passed | 402 | 255 ms |
| 16 Oct 2026, 12:23 UTC | Passed | 402 | 507 ms |
| 16 Oct 2026, 07:46 UTC | Passed | 402 | 333 ms |
| 16 Oct 2026, 03:09 UTC | Passed | 402 | 510 ms |
| 15 Oct 2026, 22:44 UTC | Passed | 402 | 177 ms |
| 15 Oct 2026, 18:45 UTC | Passed | 402 | 200 ms |
Price and payment address
- Price
- $0.039 per call on Base
- Pays to
- 0xec84…de28
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 5 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.