#launch
Ship the public API. Don't slip.
An AI team that knows your company and runs its work, with receipts.
open the API to customers
M-12
API access is included in Pro
paid add-on · scrapped 14 Jan
Issue and verify API keys
Rate-limit by plan at the edge
Publish the API reference
Grok
a different family
Rate-limit headers on 429
Codex · fixedVerdict
Grok
a different family
Rate-limit headers on 429
Codex · fixedEventually you stop checking.
Forward the thread. Review the change once. The next session starts from the corrected file.
#launch
Ship the public API. Don't slip.
API launch research
Keep v0 working through the launch — dual-run until the new routes are in.
PR #412
Sunset notice merged.
ENG-241
Must clear before anything ships.
launch/public-api.md
launch/public-api.mdWhat should the API announcement say?
Lead with March 17 and the v0 migration path — security review clears first.
One job in, whichever seats it needs, and it keeps going when one runs out.

One task, two touches from you: approve the plan, read the review. Everything between them runs without you.
You type five words. What your company already settled comes with them — and the one thing it never decided, it will not guess.
You
open the API to customers
Brief
Claude
Claude, Codex and Cursor each take a piece, signed in on your Mac. When one hits its cap, the next one continues on Codex, briefed.
Wave 1· at the same time
Wave 2
Five criteria, and a grader that did not do the work. One of them fails before it passes — and the fix is already in the commit.
Grok
a different family
Worth flagging
Nothing expires a key yet
Hashed at rest, shown once — but nothing rotates them. Your policy call.
Your sales deck still promises 600 on Free
The run used decisions/rate-limits.md. The deck disagrees; I left it alone.
curl https://api.acme.dev/v1/usage -H "Authorization: Bearer sk_live_…"
What changed
| Surface | Change |
|---|---|
| api_keys | new table · hash, prefix, last used |
| POST /v1/keys | new · issued once, shown once |
| auth middleware | cookie or key, one session object |
| docs/api | generated from the routes |
Evidence
You touched it twice.
It finishes every task it can verify and undo. Anything it can't stops and asks you — that's the only queue you watch.
General taskNeeds youRenewal price for Northwind2:10 PM
Supervisor recommends $499/mo — the list price in enterprise-gtm.md. Customer-facing and can't be undone, so it stopped.
Headcount of one. Leverage of a team.
Keep the tools you already use.
They read your company from one place.
Add it to Claude Code or CursorOr hand it the task.
Free plan, no card. Nothing acts until you turn it on.
Connect your sources, or bring in a research thread. Get a cited company record and use it in your next coding or content task. You approve work before it runs. AI Squads are a preview of what comes next, not a requirement to get started.
HiveBase works with the agents you already run. It briefs them from your company, routes work across the models and keys you already pay for, and brings back a receipt. Cursor stays Cursor; Claude Code stays Claude Code.
HiveBase connects the decisions in your chats and documents to the work your agents do. A task starts with company context and returns with evidence of what changed. You can inspect the sources and decide what is allowed to proceed.
The job, not the tools. Your Cursor stays Cursor; your Linear stays Linear.
Yes — overlay. CLAUDE.md, GBrain, and Cursor rules stay yours. HiveBase keeps them true. Delete us and you keep everything.
Reads are free. Work you ask for comes out of your plan. Nothing meters what it merely watches. Runs on the models and keys you already pay for, no markup on those.