Edge and developer platform · Integration · New in 0.3.0

Cloudflare cost tracking: Workers, R2 and plan fees

See Cloudflare's usage charges per day and service, such as Workers and R2, next to your other bills, with your plan fees added as an estimate.

What Burnstack tracks

  • Usage charges in USD per service and day from Cloudflare's Billable Usage API (Cloudflare API), per zone or, for account-wide services, per account
  • Plan fees, such as a zone's Pro plan or Workers Paid, from your subscriptions' prices, spread over the days and marked est.
  • Usage inside free allowances is kept as a quantity at $0

Alerts

  • Vendor spend spike: a day above 2.5× Cloudflare's 14-day median

The key you'll need

A custom API token with one permission, Account → Billing → Read: at dash.cloudflare.com → My Profile → API Tokens, choose Create Token → Create Custom Token, add that permission and pick the accounts to track under Account Resources. Billing Read is the permission Cloudflare requires for billable usage (Cloudflare docs). The Global API Key isn't accepted, because it can do everything.

Burnstack checks the key with Cloudflare, shows the account it belongs to when Cloudflare lets the key see it, and stores it in your computer's keychain (macOS Keychain or Windows Credential Manager). It only reads billing and usage.

Connect it: Cloudflare

About 3 minBilled

Need

  • Key: API token
  • Plan: Pay-as-you-go accounts (Free, Pro, Business); Enterprise contracts get plan fees only.
  • Permissions: Account → Billing → Read

Create a Custom token with one permission, Account → Billing → Read, and under Account Resources include the account(s) to track. Not the Global API Key. Usage charges come from Cloudflare's Billable Usage API, which is in alpha and covers pay-as-you-go accounts only (not Enterprise contracts). Plan fees (Pro, Workers Paid…) are estimated from your subscriptions' prices.

Steps

Open Cloudflare's key page ↗

  1. Open My Profile → API Tokens and click Create Token → Create Custom Token.
  2. Name it Burnstack and add one permission: Account → Billing → Read.
  3. Under Account Resources, include the account(s) to track; set the TTL.
  4. Click Continue to summary, then Create Token.
  5. Copy the token and paste it into Burnstack.

Paste it

In Burnstack: Connectors → Cloudflare → Add key → paste → Validate & save. The key goes straight into your computer's keychain.

If it fails

Invalid request headers
That's the Global API Key, which isn't supported. Create a Custom token with Account → Billing → Read.
This token can't see any Cloudflare accounts
Under Account Resources, include the account to track, then create the token again.
Cloudflare API error 403
The token needs Account → Billing → Read on that account.

Let your AI do the clicking

Paste this into an AI assistant that can use your browser, such as Claude in Chrome. It opens Cloudflare's key page and sets only the permissions above, then stops before the final button that creates the key.

Open https://dash.cloudflare.com/profile/api-tokens in my browser. Choose 'Create Token', then 'Create Custom Token'. Name it 'Burnstack'. Under Permissions add one row: Account → Billing → Read. Under Account Resources include only the account(s) I want to track. Leave Client IP Address Filtering empty. Then click 'Continue to summary'. Set the TTL to 90 days (or the closest shorter option). Stop before clicking 'Create Token' (the final button that creates the token) and tell me it's ready. I'll click it, copy the token and paste it into Burnstack myself. Don't copy, read or paste the token, and don't grant broader access or change any other setting. If Cloudflare asks me to sign in or confirm with 2FA, wait for me.

The key never passes through the AI: you click that last button yourself, copy the key and paste it into Burnstack.

What you'll see

  • Billed: Billed cost, as Cloudflare charges it.
  • History: Not documented. not yet verified
  • Delay: Not documented (the Billable Usage API is alpha); plan fees are estimated at sync. not yet verified

Good to know

  • Cloudflare labels its Billable Usage API alpha (Cloudflare API), so it may change. If it fails, the sync shows Cloudflare's error instead of quietly showing only plan fees.
  • Pay-as-you-go accounts only, such as Free, Pro and Business. Cloudflare doesn't cover Enterprise contract accounts in its billable usage data (Cloudflare docs).
  • Plan fees are an estimate from your current subscriptions: a plan bought last week counts for the whole period shown. Add-ons, taxes, credits and domain renewals aren't included; import invoice lines as CSV for exact totals.
  • Accounts billed in USD only.
Burnstack Connectors, Add cost source tab: a search box, category filters and one card per vendor with its key steps

One bill, not a dashboard per vendor

Burnstack puts Cloudflare next to the rest of your spend and lets you group it by product with applications. Other integrations: Vercel, Neon, Supabase, OpenAI, Anthropic, GitHub, OpenRouter, DigitalOcean, Twilio, Stripe fees, Netlify, AWS, Datadog, Sentry, Cursor, PlanetScale, Azure, Google Cloud, MongoDB Atlas, Railway, Render, Heroku, Akamai (Linode), Vultr, Fastly, Runpod, xAI, Together AI, fal.ai, Runway, Upstash.

Cloudflare questions

Why are some Cloudflare costs marked est.?
Cloudflare's usage API reports metered charges in dollars, but not fixed plan fees. Burnstack adds those from your subscriptions' prices, spread evenly over the days, and marks them est. so you know they're not from an invoice.
Can one token cover several Cloudflare accounts?
Yes. Include each account under Account Resources when you create the token; one connector covers all of them.

Start watching back.

Five minutes to connect your first vendor. Free for Mac, forever, and every byte stays yours.