Crypto API status
The REST API answered its health check, which round-trips the database and the cache. The MCP package and the agent-backed jobs run on the same API.
Last checked . This page refreshes at most once a minute.
Components
One probe covers all three: the package and the jobs sit behind the same API, so their status follows it.
- REST APIapi.blockchainacademics.combuild 352bb2aOperational
- stdio package, calls the REST APIOperational
- Agent-backed jobsapi.blockchainacademics.com/v1/agent-jobsasync research, due diligence, tokenomicsOperational
Uptime and support by tier
Pro and Team carry an uptime commitment on the REST API; Enterprise sets its own in contract. Free and Starter are best effort.
| Tier | Uptime | Support |
|---|---|---|
| Free | Best effort | Community |
| Starter | Best effort | Email, 48 hour response |
| Pro | 99.9% | Email, 24 hour response |
| Team | 99.9% | Slack, 4 hour response |
| Enterprise | 99.99%, contractual | Dedicated engineer and Slack Connect |
Uptime is measured monthly on the REST endpoint. Questions about an SLA or data residency go to [email protected].
How this page works
Our server calls GET /v1/health on the API with a three second timeout, at most once a minute. The probe exercises the database and the cache, so a green dot means a real request round-tripped, not a label. When something breaks, the API answers 503 and the dot turns amber. There is no incident history yet; the changelog records releases, and the docs and the API explorer cover every endpoint.