Bee — The Progressive Intelligence Engine: tiered LLM, 4 tools, hosted API, free tier.
Website | Documentation | Packages | Machine-readable package index | System status
The public developer distribution for Bee, HEOSSI's governed multimodal intelligence platform. This repository contains the actual source of Bee's Apache-2.0 SDKs, MCP integration, API contracts, runnable examples, and public trust-verification material.
This repository is generated from reviewed, public-safe paths in the Bee monorepo. MANIFEST.json records the exact source commit and content digest for every export; SHA256SUMS and the SPDX SBOM support independent artifact inspection.
The canonical package catalog records each public developer distribution, exact version, registry, role, license boundary, and install command. Its machine-readable companion is PACKAGE-INDEX.json. These distributions do not expose the private Bee service monorepo.
| Surface | Install or entry point | Source / contract |
|---|---|---|
| TypeScript SDK | npm install @heossihq/bee | sdks/typescript |
| Python SDK | pip install bee-sdk | sdks/python |
| MCP server | uvx --from bee-sdk@latest bee-mcp | mcp · server.json |
| OpenAI-compatible API | https://api.bee.heossi.com/bee | openapi.json · postman.json |
| BEE Code for VS Code | Heossi.beecode | Microsoft Marketplace · Open VSX |
| Bee Code CLI | npm install -g @heossihq/beecode | Download guide |
| PQ assurance | Signed public coverage register | trust/pq-register |
import { BeeClient } from "@heossihq/bee";
const bee = new BeeClient({ apiKey: process.env.BEE_API_KEY! });
const result = await bee.chat.completions.create({
model: "bee-cell",
messages: [{ role: "user", content: "Explain hybrid post-quantum TLS." }],
});
console.log(result.choices[0].message.content);
Create an API key in Bee Workspace. The free Cell tier works with both SDKs and MCP.
api/ Versioned OpenAPI and Postman contracts
docs/ Public architecture and enterprise scenario flows
examples/ Runnable TypeScript and Python examples
mcp/ Client configuration and MCP setup
sdks/typescript/ Published @heossihq/bee package source and tests
sdks/python/ Published bee-sdk and bee-mcp source and tests
trust/pq-register/ Public PQ coverage register and offline verification tools
| Evaluator | Start here | What can be verified publicly |
|---|---|---|
| Enterprise architect | Reference architecture and scenario flows | System boundaries, governed request flow, deployment profiles, and responsibility split |
| Security or risk lead | Security policy, PQ coverage register, and diligence index | Disclosure path, released PQ claims, evidence limitations, and public control references |
| Platform engineer | API contracts, SDKs, MCP, and examples | Integration contracts, install paths, source, examples, and client configuration |
| Procurement or technical diligence | MANIFEST.json, SHA256SUMS, SPDX SBOM, and NOTICE | Export provenance, file integrity, package inventory, licensing, and the public/proprietary boundary |
Start with the public reference architecture, then follow the control boundary through three concrete flows:
The matching visual architecture centre is published at bee.heossi.com/docs/architecture.
Bee Code's agent path is durable, subscription-bounded, and independently metered. Workspace, mobile, desktop, SDK, and MCP requests retain their own documented execution contracts; common entitlement enforcement does not imply that every surface has local IDE tools.
The public distribution is locally rendered from an allowlisted monorepo surface. Verify it with:
sha256sum --check SHA256SUMS
python3 scripts/verify_bee_package_index.py PACKAGE-INDEX.json
SHA256SUMS covers every exported payload file except itself and the
commit-specific MANIFEST.json. The manifest separately binds the export to
its source commit and contains a deterministic digest of the complete payload.
The SPDX document is package-level (filesAnalyzed: false); it inventories the
published SDK and MCP packages without claiming a binary or deployment SBOM.
The files in this repository are Apache-2.0 licensed. Bee's model engine, orchestration plane, hosted gateway, Bee Code CLI implementation, editor-extension implementation, and commercial applications remain proprietary and are not represented as open source here. Public API and package behavior is defined by the contracts and SDK source in this repository.
bee-security@heossi.com; see SECURITY.mdRead CONTRIBUTING.md, SUPPORT.md, and the Code of Conduct. Generated paths must be changed in their canonical monorepo source; community examples and documentation can be proposed here and are reconciled during the next local export.
Apache License 2.0 · Copyright 2026 HEOSSI (Pte.) Ltd.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
uvx bee-sdkMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-cuilabs-bee": {
"command": "uvx",
"args": [
"bee-sdk"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencebee-sdkpypiBee — The Progressive Intelligence Engine works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.