Explore Flowstate

The Flowstate platform
Flowstate Helm

Know what AI costs. See what you get back.

Understand spending, share budgets and connect AI use to the work it supports.

Recent insights All insights

Buy tokens, rent GPUs, or own the rack?

Open-weight models are now good enough to make self-hosting a financial question rather than a capability one. I modelled four options, an office rack, colocation, rented GPUs and per-token APIs, to find where each one actually wins. The answer turns on utilisation, and it isn't the one the internet keeps giving.

Turn a $3m AI bill into $1.9m

Most teams overpay for AI twice without noticing: they run everything through the default flagship model, and they buy the tokens on a metered plan they can't see into. An intelligent proxy fixes both. Here is the maths, a calculator you can drag, and where Flowstate fits.

Start with the work All use cases

Understand AI spending and value

See where the budget goes and what the business gets back.

Share one AI budget across your tools

Fund people, teams and projects across connected services.

Give your team more capacity

Reduce the preparation, checking and follow-up around recurring work.

Connect AI use to delivered work

Follow AI activity into projects, code and business results.
Quick links
Flowstate / People + AI Talk through your priorities
Documentation
Get help
Docs / Integrations

Connect Claude

Connect Claude to see who uses it and what it costs, per person and per day, beside the rest of your AI spend.

You need access to connect AI providers. Ask your Flowstate admin.

Choose the connection

Anthropic uses a different key for each way you buy Claude. The keys aren’t interchangeable. If you buy both ways, connect both.

You buy Claude throughOpen this in FlowstateKey you need
The Anthropic Console (pay per token, including Claude Code on API keys)Claude Platform, called Anthropic API (Console) in SettingsAn Admin key, created by someone with the admin role in your Console organisation
Claude Enterprise seats on claude.aiClaude EnterpriseAn Analytics API key, created by your organisation’s primary owner

Connect the Anthropic API (Console)

  1. In the Claude Console, open Settings → Admin keys and create a key.
  2. Copy it straight away. It starts with sk-ant-admin01- and is only shown once.
  3. In Flowstate, go to Organisation → Organisation → Integrations and select Claude Platform under AI providers.
  4. Select Connect, or Add another account if one is already connected.
  5. Paste the key and select Verify and connect.

If your organisation doesn’t use Organisation yet, replace steps 3 and 4: go to Settings → Integrations, select Browse catalog and open Anthropic API (Console), then under How to connect select Use this route.

Connect Claude Enterprise

  1. In claude.ai, open Organization settings → API.
  2. Create an Analytics API key with the read:analytics and read:members scopes, and copy it. A key’s scopes can’t be changed later.
  3. In Flowstate, go to Organisation → Organisation → Integrations and select Claude Enterprise under AI providers.
  4. Select Connect, or Add another account if one is already connected.
  5. Paste the key and select Verify and connect.

If your organisation doesn’t use Organisation yet, replace steps 3 and 4: go to Settings → Integrations, select Browse catalog and open Claude Enterprise, then under How to connect select Use this route.

Check it’s working

The key is listed under Connected keys with the status Working, and Data through shows a recent date. See the spend in Agent insights.

What Flowstate brings in

ConnectionWhat you get
Anthropic API (Console)Claude Code usage and cost per person each day, by model. It doesn’t include Claude used through Amazon Bedrock, Google Vertex or Microsoft Foundry.
Claude EnterpriseUsage and billed cost for every person on your plan, by model. Data starts on 1 January 2026.
  • Flowstate syncs every hour, and brings in your history when you first connect.
  • Anthropic can revise Claude Enterprise figures for up to 30 days. Flowstate picks up the changes, so recent numbers can move.
  • Spend is matched to people by email address. People you add to Flowstate later are matched once they’re added.
  • The Claude Enterprise key reads usage, cost and, with read:members, the list of your members. Flowstate can’t see conversations with it.

People

If your organisation has Flowstate Helm, Flowstate also brings in everyone in your Console organisation, and everyone in your Claude Enterprise organisation when the key has read:members. They’re listed on Users & teams. Nobody is emailed until you invite them.

If something’s not right

The key is refused. Select Show what the provider said to see why. Check you used the right key: an Admin key for Anthropic API (Console), an Analytics API key for Claude Enterprise.

The connection shows Key rejected. The key was revoked or replaced at Anthropic. Create a new one and select Replace key on the connection. Your history stays.

The connect window (or the provider’s page in Settings) says “To import people, this key needs read:members”. The Claude Enterprise key was made with read:analytics alone, and its scopes can’t be changed. Select Create a new key beside the message, and create one with both scopes.

Spend through Bedrock or Vertex isn’t there. Connect Amazon Bedrock or Vertex AI as well.

Someone’s spend isn’t shown against them. Their email at Anthropic doesn’t match anyone in Flowstate. Add them or correct their email, or match them by hand under Settings → Integrations → User attribution.