Cloudflare in ninedot.
Domains, plans and Pages projects. Zones with their status and plan, and Pages projects with their latest deploy.
Read-only · the key itself can be limited to read · disconnect any time
What you get
- live statusZone status (active, pending nameservers, moved)
- estimate to confirmZone plan list price, as an estimate for you to confirm
- live statusPages production deploy status and custom domains
Exact is read straight from Cloudflare. Measured is derived from usage or a rolling 30-day window. Only those two are ever counted. Where Cloudflare can't report a bill, ninedot suggests the plan's list price and you confirm what you pay. That figure counts in your own totals, marked Confirmed by you, and is never shown as verified.
Connecting takes a few minutes
- Create a API token (read-only)Zone Read, Cloudflare Pages Read and Account Settings Read, scoped to the zones you choose. Create it at dash.cloudflare.com.
- Paste it in the VaultIn ninedot, open Vault → Cloudflare → Connect. The key is checked, encrypted at rest and only ever read by ninedot's servers.
- Put it on a productninedot suggests which product each service belongs to, by domain or name. Accept it in one click, or link it by hand.
Limits, honestly
- Pages needs the token's Pages Read permission; without it domains still work.
- Nothing is ever changed in Cloudflare.
Questions
- Can I track a Cloudflare domain and a Pages site on the same business?
- Yes. Both appear as services; the Pages site is matched to the business by its custom domain.
- Can an AI agent read this too?
- Yes. Claude, ChatGPT, Cursor and Claude Code connect through ninedot's MCP server and get the same figures with the same trust levels. Agents can never change your Cloudflare account.
Get started freeNo card needed · read-only access · disconnect any time