Free · Source available · macOS 14+

See your API spend before the bill does.

Today’s and this month’s spend for every provider, one click from your menu bar. Kill Cord says honestly how fresh each number is, and walks you through turning on the caps each provider already offers, since those are what actually stop a runaway bill.

Or install with Homebrew

brew install --cask coreyhaines31/tap/killcord

Free with no account · Keys stay in your Keychain · macOS 14 Sonoma or later

KILL CORDLocal monitoring↻
Today$25.47*
This month$338.38*

* Includes numbers that aren’t live: Cloudflare.

Today leaves out Vercel, Cloudflare, and Twilio (not reported yet or not read).

Each provider’s day and month follow its own billing clock.

Sample dataAPI spend monitor
AnthropicChecked

Checked 9:23a

Today$18.42This month$212.07
Google Cloud and GeminiChecked

Checked 8:46a

Today$4.90This month$61.33

Google Cloud and Gemini data current through 2:26a.

Google’s billing export runs hours behind, typically up to a day, with no guarantee. Today’s number usually reads low.

OpenAIChecked

Checked 9:23a

Today$2.15This month$37.80
Settings… ⌘,Quit Kill Cord ⌘Q
Kill Cord’s panel with sample data: totals up top, then each provider with when it was last checked.
The problem

The bill arrives after the money is gone.

Usage-billed APIs don’t send a bill until it’s too late to matter. An agent loop, a leaked key, or a forgotten batch job can run all night, and you find out from an invoice.

Every provider already offers some kind of spend cap. They’re just easy to leave unset, spread across a different console for each one. Kill Cord puts the spend in one glance and gets those caps turned on.

How it works

Every bill, one glance.

Total spend sits next to a small plug in your menu bar. Click it for each provider’s today and month to date.

In the menu bar

Spend where you already look

Today’s total, or this month’s, right in the menu bar. No more opening five billing consoles to add it up.

Every provider

Today and this month, side by side

Anthropic, Google Cloud and Gemini, OpenAI, Vercel, Cloudflare, Twilio, and Neon in one panel, each on its own billing clock.

Alerts

A nudge at the amount you choose

Notifications at daily and monthly amounts you pick, per provider and in total, once per day or month.

Honest numbers

It tells you how fresh every number is.

Kill Cord checks only while your Mac is awake, and it never pretends otherwise. Every provider shows when it was last checked. After sleep, or offline, a number says it isn’t live until the next check.

  • Shows provider lag. Some providers run behind. Google’s billing export can be most of a day behind, and the panel says so.
  • Says what it can’t see. Neon reports usage, not dollars. Supabase has no billing API. Totals list what they leave out.
  • Never implies overnight coverage. It doesn’t check while your Mac sleeps, and checks again about 10 seconds after wake.
Checked 3:42p
The number is current as of that check.
Last checked 11:42p, not live
Kill Cord couldn’t check since then: your Mac slept, went offline, or the check failed. The line under it says which.
$25.47*
The total includes a number that isn’t live.
Not reported yet
The provider hasn’t reported that period. Not the same as $0. Vercel and Cloudflare report by day.
Billing period from Nov 3
Cloudflare reports by billing period, not calendar month.
data current through 11:00a
The provider’s own freshness stamp, where it gives one.
Caps audit

The caps that actually stop a runaway bill.

A menu bar number can’t stop spend. Each provider’s own caps can. For every provider, Kill Cord lists the spend controls it offers, says whether each is a hard stop or only an alert, and opens the exact console page to turn it on.

No. 1

See what each provider offers

Every native control, labeled hard stop, partial stop, or alert only, so you know what will actually stop spend.

No. 2

Open This Setting

One button goes straight to the right page in the provider’s console. Kill Cord never changes a cap for you.

No. 3

Confirmed, or your checkmark

Where an API can confirm a cap (OpenAI, Google budgets, Cloudflare, Twilio, Neon), Kill Cord checks it every few hours. Elsewhere it’s your checkmark, and it asks you to look again after 30 days.

  • AnthropicOrganization spend limit and per-workspace spend limitsHard stop
  • Google Cloud and GeminiSpend cap budgets that pause the Gemini API, Vertex AI, or Cloud Run; the AI Studio project spend cap; budget alertsHard stop + alerts
  • OpenAIOrganization hard limit and project limits, and spend alertsHard stop + alerts
  • VercelSpend Management with pause production deployments, and its notificationsPartial stop
  • CloudflareSpend Management limits for Workers and Durable Objects, and budget alertsHard stop + alerts
  • TwilioUsage triggers on total price (Twilio has no native hard cap)Alert only
  • NeonSpending threshold, and per-project consumption quotasAlert + hard stop
  • SupabaseThe Pro plan Spend CapPartial stop

Providers say even hard stops aren’t instant, so spend can run a little past a cap.

Providers

Eight providers, read only.

Kill Cord reads each provider’s own billing data with a key you create. Here’s what it reads, and what it can and can’t see.

ProviderSpend sourceKey you needDollars?
AnthropicAdmin API cost reportAdmin API keyYes, within about 5 minutes
Google Cloud and GeminiCloud Billing export to BigQueryService account key with read access to the exportYes, after one-time setup; hours behind
OpenAIOrganization costsAdmin API keyYes
VercelBilling charges (FOCUS)Access tokenYes, daily
CloudflareBillable usage (pay-as-you-go accounts)API token with Billing ReadYes, daily; by billing period
TwilioUsage records (total price)API key or Auth TokenYes
NeonConsumption historyOrganization API keyNo: usage only
SupabaseNoneNothing to connectNo: no billing API (caps audit only)
Privacy

Your keys stay on your Mac.

Each key goes to one place: the provider it belongs to. Nothing else leaves your Mac except Kill Cord’s update check.

Keys in the Keychain

Not in files, preferences, logs, or exports. Kill Cord checks a key with its provider first, then saves it to your login Keychain.

Read only

Kill Cord only reads billing and never changes a provider setting. Anthropic, Twilio, and Neon have no read-only keys, and Kill Cord says so before you save one.

No telemetry

The app has no analytics, no account, and no tracking. Its only other network request is the update check against the GitHub releases.

Corey Haines
Why it exists

I run coding agents and build on a handful of usage-billed APIs, and any of them can run all night: an agent stuck in a loop, a leaked key, a batch job I forgot. The bill shows up after the money is spent, and the caps that would have stopped it were sitting unset in five different consoles. So I built the app I wanted: today’s spend for every provider in my menu bar, and a checklist that gets those caps turned on. And it’s free.

Corey Haines, maker of Kill Cord and more free Mac apps
Questions

Before you plug it in.

Does Kill Cord stop my spending?

No. Kill Cord only reads billing and never changes a provider setting. The hard stops are each provider’s own caps, and Kill Cord’s caps audit walks you through turning them on and opens the right console page.

Does it watch my spend while my Mac is asleep?

No. Kill Cord checks only while your Mac is awake. After sleep or time offline, numbers say “Last checked 11:42p, not live” until the next check, which happens about 10 seconds after wake. That’s why native caps matter: they keep working when your Mac doesn’t.

Which providers does it support?

Anthropic, Google Cloud and Gemini, OpenAI, Vercel, Cloudflare, Twilio, and Neon for spend, plus Supabase in the caps audit. Neon reports usage rather than dollars, and Supabase has no billing API. See what each one needs.

What key do I need?

A billing key for each provider you connect. Anthropic and OpenAI need admin keys, not regular API keys. Cloudflare needs a token with Billing Read, and Google needs a service account that can read your billing export. Never paste a key into a chat or an AI agent to set Kill Cord up. If you already have, revoke it and create a new one.

Is my key safe?

Each key lives in your login Keychain and goes only to its own provider’s billing API over HTTPS. It never appears in files, preferences, logs, error messages, or exports. If a key ever leaks, revoke it in the provider’s console.

Why does Google read low?

Google’s billing export runs hours behind, typically up to a day, and starts a few hours after you turn it on. Kill Cord shows Google’s own “data current through” time so you know how far behind it is.

Why does today say “Not reported yet”?

The provider hasn’t reported that period, which isn’t the same as $0. Vercel and Cloudflare report by day, so today often reads this way.

What does it cost?

Nothing. Kill Cord is free with no account. The source is on GitHub under the Functional Source License (FSL-1.1-MIT), and each version becomes MIT two years after release.

How do I uninstall it?

In Settings › General, click Remove All… to delete every key and all local data. Then run brew uninstall --cask --zap killcord, or drag Kill Cord to the Trash. Removing keys from Kill Cord doesn’t revoke them, so revoke any you no longer need in each provider’s console.

Get Kill Cord

Plug in your providers. Turn on the caps.

Free, with no account and no subscription. Click the plug, then Connect a Provider, and paste a billing key. Kill Cord checks it with the provider before it saves it.

Or install with Homebrew

brew install --cask coreyhaines31/tap/killcord

macOS 14 Sonoma or later · Updates itself