Developers

Authentication

HiveBase supports hosted OAuth for MCP clients and scoped API keys for trusted programmatic callers.

Auth paths

OAuth 2.1 + Dynamic Client Registration

Default for MCP hosts. Users consent in the browser, tokens are workspace scoped, and write tools can require confirmation.

hb_sk_* API keys

Fallback for CI, backend jobs, and service-to-service automation. Keys are bearer tokens with explicit scopes.

API key request shape

REST callers use the Platform API v2 origin and pass the key as a bearer token.

curl https://app.hivebase.ai/api/v2/brain/search \
  -H "Authorization: Bearer $HIVEBASE_API_KEY" \
  -H "Content-Type: application/json" \
  --get \
  --data-urlencode "query=Acme renewal status"

OAuth write confirmation

OAuth write tools include confirmation metadata so clients can show approve, edit, or reject UI before state changes are committed.

{
  "_meta": {
    "requires_confirmation": true
  },
  "content": [
    {
      "type": "text",
      "text": "Decision ready for confirmation."
    }
  ]
}