Product

Hard spending caps and a kill switch for AI agents.

FlockTab is a proxy that gives each agent a hard cap and a kill switch, hosted or on your own machine. It speaks the OpenAI and Anthropic APIs and passes your own Claude, ChatGPT, Grok and Kimi logins through the same gate. It is not a gateway suite or a model marketplace: it is the thing that stops the spend.

Tabs, not keys

A tab is an agent's spend account. Name it, cap it, issue a key. Close it when you want the agent to stop.

Reserve before the provider

Every call holds estimated cents against the tab first. If the reserve would cross the cap, the provider is never called.

Kill switch

Close one tab or the flock. Takes effect on the next reservation. In-flight calls finish.

Policies per Agent

Caps, velocity, model and irreversible allowlists, tool caps. Applied in order: tab state, cap, velocity, models, irreversible, tool caps. First block wins. Set in the console or with tab policy.

Audit ledger

Reservation, decision, reason, cents, per Agent, project, model and login. This is a control plane, not a trace waterfall.

Self-hosted or hosted

Run tab up and the proxy lives on your machine: prompts, replies and provider keys go straight to the vendor, and flocktab.com only sees model, tokens and cents. Hosted, your key is ciphertext we cannot open without the unlock secret you send per call, and prompts pass through in memory, never stored. You pay the provider; FlockTab is billed per agent.

The tab CLI

tab claude, tab codex, tab grok, tab kimi: the agent starts through FlockTab with nothing to configure. tab top shows the whole flock live in your terminal.

Your own subscriptions

Claude Max, ChatGPT, SuperGrok and Kimi logins pass through the same gate and kill switch, recorded at list price, never charged. Several logins pool: each launch takes the one with the most of its week left.

Agent Guard and loop watch

Per Agent: irreversible tool calls (force-push, production deploy, payment, deleting data) are recorded, asked or refused before they run, and an agent stuck repeating itself can be paused.

Outside spend

Connectors read what FlockTab did not proxy (OpenRouter, Cloudflare, GitHub and more) and put it beside the tab, by project, with what is still unattributed.

Projects

Agents and outside costs roll up to projects for chargeback. Agents link to the project they are named after; shared costs split by weight.

Observability

A live map of the flock: which Agents are working, what they cost, and how they talk to each other. Metadata only, never prompts.

Start a flockHow it worksThe tab CLI