Bee — The Progressive Intelligence Engine

Official registry AI and agents

Bee — The Progressive Intelligence Engine: tiered LLM, 4 tools, hosted API, free tier.

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).

PYPI package bee-sdk
Claude Code
claude mcp add bee-the-progressive-intelligence-engine -e 'BEE_API_KEY=<your bee_api_key>' -e 'BEE_MODEL=<BEE_MODEL>' -e 'BEE_API_URL=<BEE_API_URL>' -- uvx bee-sdk==0.6.0
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "bee-the-progressive-intelligence-engine": {
            "command": "uvx",
            "args": [
                "bee-sdk==0.6.0"
            ],
            "env": {
                "BEE_API_KEY": "<your bee_api_key>",
                "BEE_MODEL": "<BEE_MODEL>",
                "BEE_API_URL": "<BEE_API_URL>"
            }
        }
    }
}

Environment variables

  • BEE_API_KEY required secret Bee API key (bee_sk_…). Create one at https://bee.cuilabs.io/app/account/api-keys — the free Cell tier works.
  • BEE_MODEL Default model tier (bee-cell … bee-swarm). Tier access follows the API key's plan. Default: bee-cell (free).
  • BEE_API_URL Override the gateway base URL (default https://bee.cuilabs.io/bee). Set only for a self-hosted Bee Enclave or staging.

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Bee: Quantum Intelligence
  2. Developer surface
  3. Quickstart
  4. Repository map
  5. Enterprise evaluation paths
  6. Architecture and scenarios
  7. Integrity and provenance
  8. Public and proprietary boundary
  9. Support and security
  10. Contributing
  11. License

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.

SurfaceInstall or entry pointSource / contract
TypeScript SDKnpm install @heossihq/beesdks/typescript
Python SDKpip install bee-sdksdks/python
MCP serveruvx --from bee-sdk@latest bee-mcpmcp · server.json
OpenAI-compatible APIhttps://api.bee.heossi.com/beeopenapi.json · postman.json
Bee: Quantum Intelligence - CodeHeossi.beecodeMicrosoft Marketplace · Open VSX
Bee Code CLInpm install -g @heossihq/beecodeDownload guide
PQ assuranceSigned public coverage registertrust/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

EvaluatorStart hereWhat can be verified publicly
Enterprise architectReference architecture and scenario flowsSystem boundaries, governed request flow, deployment profiles, and responsibility split
Security or risk leadSecurity policy, PQ coverage register, and diligence indexDisclosure path, released PQ claims, evidence limitations, and public control references
Platform engineerAPI contracts, SDKs, MCP, and examplesIntegration contracts, install paths, source, examples, and client configuration
Procurement or technical diligenceMANIFEST.json, SHA256SUMS, SPDX SBOM, and NOTICEExport 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

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 — The Progressive Intelligence Engine?

Bee — The Progressive Intelligence Engine: tiered LLM, 4 tools, hosted API, free tier.

How do I install Bee — The Progressive Intelligence Engine?

It runs on your machine. In Claude Code: claude mcp add bee-the-progressive-intelligence-engine -e 'BEE_API_KEY=<your bee_api_key>' -e 'BEE_MODEL=<BEE_MODEL>' -e 'BEE_API_URL=<BEE_API_URL>' -- uvx bee-sdk==0.6.0. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Bee — The Progressive Intelligence Engine need an API key?

Yes. It expects BEE_API_KEY, which you set in its configuration.

Is Bee — The Progressive Intelligence Engine open source?

Yes. Its code is on GitHub under the Apache-2.0 license.

Who maintains Bee — The Progressive Intelligence Engine?

It is published by cuilabs. 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.