An operational diagnostics API isn't a hype launch — it's the connective tissue between monitoring, reporting, and your existing infrastructure tooling. This guide explains what's coming, how to prepare integrations, and how to join the developer waitlist calmly.
The most useful diagnostics integrations are not single calls — they're recurring workflows: nightly SSL sweeps, hourly DNS drift checks, weekly blacklist audits. The API surface is shaped around those patterns, with stable run IDs that flow into the reporting layer.
Access uses scoped API keys per workspace. Quotas are tracked per diagnostics surface rather than as a single "request budget," so a monitoring-heavy team doesn't compete with a reporting-heavy team for the same pool.
Each diagnostics run can emit a webhook with a compact payload — useful for routing alerts into existing on-call tooling. Reports can be generated server-side and returned as signed URLs for client hand-off.
Run through these steps in order. Each step links to the right diagnostic tool.
We open access in waves, prioritized by integration interest. Joining the waitlist with your intended use case puts you in the relevant cohort.
Yes — sandbox endpoints will land first, with the same response shapes as production so you can build integrations before access is generally available.
Operational plans will follow the diagnostics surfaces you use: DNS, SSL, blacklist, uptime, latency, and reporting. Pricing favors continuous monitoring workflows over one-off calls.
Yes. Agency and MSP plans support multi-target workflows and white-label reporting hand-offs.
Monitor it continuously
Save this check, get alerts on changes, and track multiple domains in one dashboard.