Is Assistant Bx Csv Api Usage Dates down?
Up
No, Assistant Bx Csv Api Usage Dates is up.
It passed its latest check 6 h ago in 585 ms. It has passed every check since 4 Nov 2026, 14:40 UTC.
Latest check
- Last check
- 6 h ago (4 Nov 2026, 14:40 UTC)
- Response time
- 585 ms (typical 148 ms)
- Next check
- Due now
- 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
3 outages, 6 days 8 h of failed checks in total, the longest 2 days 7 h.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 31 Oct 2026, 10:49 UTC | 2 days 7 h | 4 | Expected HTTP 402, got 530 |
| 20 Oct 2026, 09:29 UTC | 46 h 12 min | 3 | Expected HTTP 402, got 530 |
| 17 Oct 2026, 22:09 UTC | 2 days 2 h | 5 | Expected HTTP 402, got 530 |
Times are when our checks ran, about every 8 hours for this listing, so start times and durations are accurate to about that.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 4 Nov 2026, 14:40 UTC | Passed | 402 | 585 ms |
| 4 Nov 2026, 05:40 UTC | Expected HTTP 402, got 530 | 530 | 28 ms |
| 3 Nov 2026, 20:38 UTC | Passed | 402 | 440 ms |
| 3 Nov 2026, 11:42 UTC | Passed | 402 | 561 ms |
| 3 Nov 2026, 02:52 UTC | Passed | 402 | 356 ms |
| 2 Nov 2026, 18:09 UTC | Passed | 402 | 1.5 s |
| 1 Nov 2026, 12:04 UTC | Expected HTTP 402, got 502 | 502 | 62 ms |
| 1 Nov 2026, 03:11 UTC | Expected HTTP 402, got 502 | 502 | 64 ms |
| 31 Oct 2026, 18:57 UTC | Expected HTTP 402, got 502 | 502 | 67 ms |
| 31 Oct 2026, 10:49 UTC | Expected HTTP 402, got 530 | 530 | 23 ms |
Price and payment address
- Price
- $0.01 per call on Base
- Pays to
- 0x8bc2…3C8C
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.