Bee: Quantum Intelligence
Bee governed intelligence for chat, code, research, documents, and memory.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http bee-quantum-intelligence 'https://api.bee.heossi.com/mcp' --header 'Authorization: <Bearer bee_sk_... API key, or complete the OAuth flow advertised at https://api.bee.heossi.com/.well-known/oauth-protected-resource (authorization server: https://workspace.bee.heossi.com).>'
{
"mcpServers": {
"bee-quantum-intelligence": {
"type": "http",
"url": "https://api.bee.heossi.com/mcp",
"headers": {
"Authorization": "<Bearer bee_sk_... API key, or complete the OAuth flow advertised at https://api.bee.heossi.com/.well-known/oauth-protected-resource (authorization server: https://workspace.bee.heossi.com).>"
}
}
}
}
bee-sdkclaude mcp add bee-quantum-intelligence -e 'BEE_API_KEY=<your bee_api_key>' -e 'BEE_MODEL=<BEE_MODEL>' -e 'BEE_API_URL=<BEE_API_URL>' -- uvx bee-sdk==1.0.69
{
"mcpServers": {
"bee-quantum-intelligence": {
"command": "uvx",
"args": [
"bee-sdk==1.0.69"
],
"env": {
"BEE_API_KEY": "<your bee_api_key>",
"BEE_MODEL": "<BEE_MODEL>",
"BEE_API_URL": "<BEE_API_URL>"
}
}
}
}
Environment variables
BEE_API_KEYrequired secret Bee API key (bee_sk_…). Create one at https://workspace.bee.heossi.com/account/api-keys - the free Cell tier works.BEE_MODELDefault model tier (bee-cell … bee-swarm). Tier access follows the API key's plan. Default: bee-cell (free).BEE_API_URLOverride the gateway base URL (default https://api.bee.heossi.com/bee). Set only for a Bee Enclave or staging.
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
Bee: Quantum Intelligence
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.
Developer surface
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: Quantum Intelligence - 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 |
Quickstart
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.
Repository map
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
Enterprise evaluation paths
| 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 |
Architecture and scenarios
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.
Integrity and provenance
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.
Public and proprietary boundary
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.
Support and security
- SDK, MCP, contract, or example defect: open an issue
- Product or account support: bee.heossi.com/contact
- Vulnerability disclosure:
bee-security@heossi.com; see SECURITY.md - Service health: status · changelog · roadmap
Contributing
Read 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.
License
Apache License 2.0 · Copyright 2026 HEOSSI (Pte.) Ltd.
Frequently asked questions
What is Bee: Quantum Intelligence?
Bee governed intelligence for chat, code, research, documents, and memory.
How do I install Bee: Quantum Intelligence?
It runs as a remote server. In Claude Code: claude mcp add --transport http bee-quantum-intelligence 'https://api.bee.heossi.com/mcp' --header 'Authorization: <Bearer bee_sk_... API key, or complete the OAuth flow advertised at https://api.bee.heossi.com/.well-known/oauth-protected-resource (authorization server: https://workspace.bee.heossi.com).>'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does Bee: Quantum Intelligence need an API key?
Yes. It expects BEE_API_KEY, Authorization, which you set in its configuration.
Is Bee: Quantum Intelligence open source?
Yes. Its code is on GitHub under the Apache-2.0 license.
Who maintains Bee: Quantum Intelligence?
It is published by heossihq. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.