Developers
Build on HiveBase
One company brain, exposed over MCP, REST, and a typed SDK — with auth, scopes, and metered credits.
Last updated 2026-07-27
HiveBase is API-first. The same context, decisions, and tasks your team uses in the app are available to your agents and backends over three interfaces that share one auth model, one set of scopes, and one billing meter.
MCP
The primary surface. Connect Claude, Cursor, Codex, or ChatGPT to live tools.
REST API
HTTP for backends and CI. Derived from the same tool registry as MCP.
TypeScript SDK
A zero-dependency typed client with first-class errors.
Start here
Quickstart
Your first authenticated tool call in under five minutes.
Authentication
OAuth 2.1 for MCP clients, scoped hb_sk_ keys for backends.
How it fits together
Rendering diagram…
- One registry. Every capability is a tool with a scope, a credit cost, and a
read/write classification. MCP
tools/list, the REST routes, and the SDK methods are all generated from it. - One auth model. OAuth 2.1 (with Dynamic Client Registration) for interactive
agent clients;
hb_sk_*API keys for trusted server-side callers. - One meter. Reads are free; work that runs a model costs credits. Costs are returned on every response so you never get surprised.
See Concepts for the model in full.