Is Services Cross Source Contradiction Resolver down?
Down
Yes, Services Cross Source Contradiction Resolver is down.
It has not passed a check since we started checking it on 11 Oct 2026. Latest error: Amount "0.25" is not in atomic token units.
Latest check
- Last check
- 19 h ago (15 Oct 2026, 15:37 UTC)
- Response time
- Not measured
- Next check
- In about 2 days
- 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 |
|---|---|---|---|
| 15 Oct 2026, 15:37 UTC | Amount "0.25" is not in atomic token units | 402 | 242 ms |
| 15 Oct 2026, 10:44 UTC | Amount "0.25" is not in atomic token units | 402 | 268 ms |
| 15 Oct 2026, 05:48 UTC | Amount "0.25" is not in atomic token units | 402 | 287 ms |
| 15 Oct 2026, 01:00 UTC | Amount "0.25" is not in atomic token units | 402 | 231 ms |
| 14 Oct 2026, 20:12 UTC | Amount "0.25" is not in atomic token units | 402 | 208 ms |
| 14 Oct 2026, 15:27 UTC | Amount "0.25" is not in atomic token units | 402 | 206 ms |
| 14 Oct 2026, 10:52 UTC | Amount "0.25" is not in atomic token units | 402 | 192 ms |
| 14 Oct 2026, 06:29 UTC | Amount "0.25" is not in atomic token units | 402 | 551 ms |
| 14 Oct 2026, 02:06 UTC | Amount "0.25" is not in atomic token units | 402 | 207 ms |
| 13 Oct 2026, 21:45 UTC | Amount "0.25" is not in atomic token units | 402 | 688 ms |
Price and payment address
- Price
- $0.25 per call on Base
- Pays to
- 0x7d9C…CB5b
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.