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. SAAR provides a native C SDK and CLI through its controlled technical evaluation; public package distribution is not enabled yet. Start here, then continue into each solution's dedicated developer portal.
Developer surfaces
- BEE APIOpenAI-compatible
- QNSI SDKs5 runtimes
- SAAR SDK + CLIC · macOS/Linux
- MCP serversFirst-party
- Command lineAvailable
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.
01
Application developers
Install a first-party package, authenticate with a solution API key and use typed clients against the hosted service.
02
AI and agent builders
Use MCP or the BEE OpenAI-compatible surface to bring governed intelligence and post-quantum trust operations into agent workflows.
03
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
01TypeScript
npm install @heossihq/bee02Python
pip install bee-sdk03MCP
uvx --from bee-sdk@latest bee-mcp04API
https://api.bee.heossi.com/bee
What developers receive
- OpenAI-compatible chat completions
- Tenant-scoped retrieval, agents and tools
- Model Context Protocol server
- Bee Code CLI and VS Code extension
- Versioned OpenAPI and Postman contracts
- Runnable TypeScript and Python examples
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
01TypeScript
pnpm add @heossihq/qnsi02Python
pip install qnsi03Go
go get github.com/heossihq/qnsi-public/sdks/go/qnsi@latest04Rust
cargo add qnsi05JVM / Android
implementation("com.heossi:qnsi:0.4.0")06MCP
pnpm add @heossihq/qnsi-mcp
What developers receive
- Authenticated REST and OpenAPI surfaces
- KMS, vault, storage, search and audit clients
- Cryptographic inventory and migration workflows
- CLI, MCP and browser PQC integration
- Host discovery agent and VS Code integration
- Runnable examples and verification tooling
Available now
SAAR
Byte-exact lossless compression
Integrate a compression layer with a single recovery contract: a successful decode reproduces the original bytes exactly, verified before a candidate is accepted.
Install and connect
01C SDK
Native C SDK - macOS and Linux02CLI
Compress and verify from the command line03Formats
SAAR v7 objects · SAST v3 streams · 16 MiB chunks04Licensing
QNSI-signed local licences (SAAR-LIC4)
What developers receive
- Byte-exact recovery contract with verified candidate acceptance
- Profiles from bounded search to smallest verified candidate
- Stream compression across chunk batches with worker parallelism
- SHA-256 envelope digest and stream transcript integrity checks
- macOS and Linux acceptance; Windows serial path pending
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.
01
Inspectable SDK source
The published BEE and QNSI SDK, MCP, contract and example surfaces can be reviewed in HEOSSI's public GitHub repositories. SAAR integration surfaces are documented on saar.heossi.com/developers during the controlled evaluation.
02
Versioned contracts
OpenAPI, package types and runnable examples define the public integration boundary without exposing proprietary hosted-service internals.
03
Artifact provenance
Export manifests, SHA-256 checksums, licensing and software-bill-of-materials artifacts support independent inspection of public distributions.
04
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.