Solutions · Developers
Build with HEOSSI solutions
BEE and QNSI provide production developer surfaces today: first-party SDKs, authenticated APIs, MCP integrations, command-line tooling, examples and public integration source. Start here, then continue into each solution's dedicated developer portal.
Available Developer Surfaces
Build with HEOSSI solutions available today
HEOSSI provides the corporate developer gateway. Detailed references, credentials, package documentation and operational tooling are maintained within each solution's dedicated portal and public repository.
Application developers
Install a first-party package, authenticate with a solution API key and use typed clients against the hosted service.
AI and agent builders
Use MCP or the BEE OpenAI-compatible surface to bring governed intelligence and post-quantum trust operations into agent workflows.
Platform and security teams
Evaluate contracts, examples, architecture, deployment boundaries, provenance and public assurance evidence before integration.
Available now
BEE
Quantum-native intelligence
Build governed multimodal intelligence, agent and retrieval workflows through first-party SDKs, MCP and an OpenAI-compatible API.
Install and connect
TypeScript
npm install @heossihq/beePython
pip install bee-sdkMCP
uvx --from bee-sdk@latest bee-mcpAPI
https://api.bee.heossi.com/beeWhat developers receive
Available now
QNSI
Post-quantum security infrastructure
Connect applications, AI workloads and infrastructure to governed key, vault, storage, discovery, migration and evidence services.
Install and connect
TypeScript
pnpm add @heossihq/qnsiPython
pip install qnsiGo
go get github.com/heossihq/qnsi-public/sdks/go/qnsi@latestRust
cargo add qnsiJVM / Android
implementation("com.heossi:qnsi:0.4.0")MCP
pnpm add @heossihq/qnsi-mcpWhat developers receive
Public Source and Evidence
Inspect the integration boundary before you build
HEOSSI publishes integration-facing source and verification material while keeping each solution's hosted engines, control planes and proprietary service implementation private.
Inspectable SDK source
The published BEE and QNSI SDK, MCP, contract and example surfaces can be reviewed in HEOSSI's public GitHub repositories.
Versioned contracts
OpenAPI, package types and runnable examples define the public integration boundary without exposing proprietary hosted-service internals.
Artifact provenance
Export manifests, SHA-256 checksums, licensing and software-bill-of-materials artifacts support independent inspection of public distributions.
Operational evidence
Solution portals publish status, security boundaries and, where applicable, reproducible conformance and benchmark evidence.
Start building
Choose the HEOSSI solution that matches your workload
Start with a public developer account, inspect the SDK source, or contact HEOSSI for enterprise, regulated, sovereign and isolated deployment requirements.