Concepts

Intents — the one RPC

Every backend capability is a Hive intent dispatched to POST /api/hive/v1/intent. An intent has a type (e.g. marketplace.list), typed input, and streams its result back over SSE. The SDK hides the streaming — dispatchIntent returns the final value.

Intents are tagged with one or more minds — the seven faculties the platform reasons about: perception, planning, decisioning, generation, coordination, memory, voice. Minds power telemetry and routing.

Agents

An agent is a named, product-scoped grouping of intents with a persona (e.g. a support agent, a creator agent). Run one with createHivemindClient().runAgent(name, input). Agents can call tools (external connectors like Gmail/Slack/GitHub) registered once and reused.

The AI Gateway

Products never call OpenAI/Anthropic/OpenRouter directly. Model calls route through one gateway that logs tokens, cost, and latency to a ledger (/admin/ai-costs) and supports provider failover. You get cost observability and provider portability for free.

Prompts

Prompts live in a versioned registry, not inline in code. Each prompt has a key, versions, variables, and a default version; the active version can be swapped (or A/B’d) without a deploy. Calls tag which prompt version produced them, so you can attribute cost and quality per prompt.

The learning loop

Products emit aggregate outcome events (never raw user data). Detectors turn those into cross-product insights — “low-poly assets download 2.5× more,” “reminders ≤15 min before raise completion 40%.” Agents pull recommendDefaults(product) before acting, so one product’s learning improves another’s defaults. That compounding is the moat.

Entitlements & billing

One identity (identity.whoami), one entitlements model (checkEntitlement, hasAccess), one billing ledger across Stripe/Paystack/RevenueCat. Gate a feature server-side with minPlan on an intent; check it client-side with hasAccess(product, feature).

Marketplace

Agents, workflows, prompts, templates, plugins, and tools are publishable and installable. First-party listings are derived live from the registries, so the marketplace is populated on day one; community listings add to it, with a revenue split on paid installs.