Developers

Developer docs

Use HiveBase as the shared company-context layer for external agents, internal tools, CI jobs, and custom workflows.

MCP
Preferred agent path

Install one hosted endpoint and let AI clients discover OAuth automatically.

2.0.0
Platform API

17 REST paths and 20 operations generated from the API schema.

36
MCP tools

Source-backed from the current API/MCP tool audit.

Start with the right interface

MCP and REST share the same platform surface. Choose based on who is calling HiveBase.

Developer reference

Core guarantees

Reads are designed for broad agent adoption and can be exposed without write approval friction.
OAuth MCP writes return confirmation metadata so humans approve ledger-affecting changes.
API keys are scoped, workspace-bound, and intended for CI or trusted server-to-server callers.
Tool names, scopes, costs, and descriptions are backed by the API schema and MCP tool audit.