Status
Is the platform answering?
A live check against the bitpull.ai health endpoint, run from this server. Not an official status page - an honest one.
What this checks, and what it does not
One unauthenticated GET against https://api.bitpull.ai/health from this server, cached for twenty seconds. It tells you whether the API is reachable and answering. It does not tell you whether voice sessions connect, whether telephony is routing, or whether the dashboard is up - those run on infrastructure this check never touches.
| Component | Covered here | How to check it |
|---|---|---|
| REST API | Available | This page. |
| Voice sessions (LiveKit) | Planned | Create a session and connect. A green health check with failing sessions is entirely possible. |
| Telephony | Planned | Call your own number. Nothing on the web side can tell you the carrier path is healthy. |
| Website widget | Planned | Load a page carrying it. The runtime is served from bitpull.ai, not from the API host. |
| Dashboard | Planned | Open it. |
Monitoring it yourself
/health needs no credential, which makes it the right target for your own uptime monitor. Point one at it if the platform is on your critical path - a check you own beats a page you have to remember to open.
# No credential needed - suitable for an uptime monitor.
curl -sS -o /dev/null -w 'status %{http_code} total %{time_total}s\n' \
https://api.bitpull.ai/healthIt is a probe run by bitpull.io. There is no incident history, no subscription and no commitment behind it. For an outage that is affecting you, support@bitpull.ai reaches the people who can say what is happening.