Is Context Crossmatch Compatibility Typing Check down?
Up
No, Context Crossmatch Compatibility Typing Check is up.
It passed its latest check 2 h ago in 348 ms, and every check since we started checking it on 25 Oct 2026.
Latest check
- Last check
- 2 h ago (7 Nov 2026, 09:25 UTC)
- Response time
- 348 ms (typical 344 ms)
- Next check
- In about 7 h
- How often
- About every 8 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 8 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 |
|---|---|---|---|
| 7 Nov 2026, 09:25 UTC | Passed | 402 | 348 ms |
| 7 Nov 2026, 03:06 UTC | Passed | 402 | 334 ms |
| 6 Nov 2026, 22:01 UTC | Passed | 402 | 374 ms |
| 6 Nov 2026, 16:59 UTC | Passed | 402 | 397 ms |
| 6 Nov 2026, 11:17 UTC | Passed | 402 | 438 ms |
| 6 Nov 2026, 04:13 UTC | Passed | 402 | 388 ms |
| 5 Nov 2026, 18:46 UTC | Passed | 402 | 360 ms |
| 5 Nov 2026, 09:23 UTC | Passed | 402 | 344 ms |
| 5 Nov 2026, 00:09 UTC | Passed | 402 | 113 ms |
| 4 Nov 2026, 14:56 UTC | Passed | 402 | 324 ms |
Price and payment address
- Price
- $0.005 per call on Base
- Pays to
- 0x7a48…6A61
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 8 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.