Catch a runaway LLM bill the same afternoon. Not at month-end.

Provider limits are per-provider, coarse, and mostly hard caps that break production when hit. PulseMeter gives you one budget across every provider, spike detection against your own baseline, and warnings hours before a cap would hit, sent to Slack and email so a human decides before anything breaks.

Those are dashboards and developer-observability tools that mostly need you to instrument code or route traffic through a proxy. PulseMeter just needs a read-only key, then watches spend for you with hourly detection and proactive alerts. Most days you won't open it at all. That's the point.

No. We only read usage and cost metrics from your provider's reporting APIs: token counts and dollar amounts by day and model — and, for team plans like Claude Enterprise, per-person usage and cost totals. We never see prompts, responses, or the content of anyone's conversations. See our security page.

No. We only call your provider's usage and cost reporting endpoints, which return aggregates of spend that already happened. They never run a model, so they consume zero tokens and add nothing to your invoice. Watching your spend never costs you spend.

On paid plans we poll usage hourly and estimate live spend against a maintained price sheet, then reconcile nightly against the official cost report. A runaway loop that starts at 2pm triggers an alert that afternoon, not on next month's invoice.

About five minutes. Create a read-only admin key at your provider, paste it in, set a budget, and connect Slack. No new SDK to install, no proxy to run, and nothing to change in your code. (One exception: for Claude Enterprise, the Analytics key must be created by your claude.ai organization's primary owner — we walk you through it.)

It depends on how your team uses Claude. For API spend, Anthropic doesn't offer a narrower read-only key for its Usage & Cost endpoints — only a full Admin key can read them, and creating one requires an Organization-tier Console account. PulseMeter calls only those read-only usage and cost endpoints with it. If your team uses Claude through claude.ai seats (Enterprise plans, including Claude Code), that data lives behind a separate Analytics API key that your claude.ai organization's primary owner creates — connect it under the Claude Enterprise provider. Either way we never see prompts or completions, and every key is encrypted at rest. More on our security page.

OpenAI and Anthropic with full hourly detection, Grok (xAI) with official daily costs, and — newly added — Claude Enterprise: per-person usage and cost for teams on claude.ai seats, including Claude Code. ChatGPT Enterprise, Google Gemini, Perplexity, and Microsoft Copilot are on the roadmap and shown in the connect screen.