API

A public API surface,
on schedule for H2-2026.

No public REST or gRPC API at launch. Today: container deployment and direct engineering engagement. Tomorrow: a coordinated public API across both flagships and Cortex.

Container endpoints todayPublic API H2-2026Banking-grade authBifrost egressDilithium2-signed

Today's state

Container + engineering engagement.

This is a deliberate choice. The first launch wave is about deep integrations with design-partner teams, not breadth-first developer self-serve. The next wave opens the public surface.

ProductToday's integration path
Enterprise CompressContainer endpoints exposed internally to the deploying customer (AWS Marketplace container or on-premise Helm chart). Not a public multi-tenant API surface.
AQEA Gen-5 SubstrateAdapter libraries delivered as a Rust crate under NDA.

Planned API surface · H2-2026

Three tracks. One release.

Mapped to the Two-Flagship architecture plus the Cortex adjacent product. Exact endpoint shape, versioning policy and authentication mechanics are being designed against feedback from early design partners — we will not pre-commit endpoint URLs we might need to revise.

TrackScopeTarget
Compress APIEmbedding-compression endpoints, Lens-Pack management, retrieval ranking.H2-2026
Gen-5 Substrate APITrit-encoder endpoints, Bit-Identity verification, cross-vendor adapter calls.H2-2026
Cortex APIMemory persistence, audit-trail query, Action-Gate configuration.H2-2026

Early access

Pre-public endpoints — under NDA.

Design-partner engineering teams get direct engineering contact, integration support, and a structured feedback loop into the public-API design.

Engineering evaluation

Gen-5 Shader · Edge

Cross-vendor benchmarks, Bit-Identity fixtures, integration discussion under NDA.

Request engineering eval

Compress container

Container deployment & integration

AWS Marketplace container or on-premise Helm chart, with engineering support for first integration.

Talk to developer team

Design principles

Fixed before the first endpoint ships.

Already implemented in Compress v1.0.0-rc18 for the container surface. The public API inherits them on day one.

Banking-grade auth

bcrypt-12 for credential hashing, OAuth2 for delegated access, mTLS for Tier 3 deployments. Customer-dashboard auth is production today.

Bifrost-enforced egress

Every outbound HTTP and TCP call leaves through one audited component — mechanically enforced via Clippy at compile time. Net-effect: predictable network surface, no shadow egress.

Dilithium2-signed updates

Every .aqpkg update artifact is post-quantum signed. The same signing discipline extends to API release artifacts.

Versioned by design

No public endpoint ships without an explicit versioning contract (semver in the changelog, version in path or header).

Want to shape the public API?

Join the early-access program. Direct engineering contact, NDA endpoint access, and a structured feedback loop into the public-API design.