Developers

Build on HiveBase

One company brain, exposed over MCP, REST, and a typed SDK — with auth, scopes, and metered credits.

Last updated 2026-11-15

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.

Start here

How it fits together

Rendering diagram…
One tool registry projects to MCP, REST, and the SDK — same behavior, scopes, and costs.
  • One registry. Every capability is a tool with a scope, a funding classification, 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 agent clients and server-side callers.
  • Shared funding. The October working contract has no API/MCP channel fee. The same underlying work uses the same quote and funding across channels; calls already inside an accepted fixed-price bundle have no duplicate charge. Candidate offers remain held pending qualification. Existing account terms remain in force until an approved migration.

See Concepts for the model in full.

Also useful