Engineering evaluation
Gen-5 Shader · Edge
Cross-vendor benchmarks, Bit-Identity fixtures, integration discussion under NDA.
Request engineering evalAPI
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.
Today's state
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.
| Product | Today's integration path |
|---|---|
| Enterprise Compress | Container 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 Substrate | Adapter libraries delivered as a Rust crate under NDA. |
Planned API surface · H2-2026
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.
| Track | Scope | Target |
|---|---|---|
| Compress API | Embedding-compression endpoints, Lens-Pack management, retrieval ranking. | H2-2026 |
| Gen-5 Substrate API | Trit-encoder endpoints, Bit-Identity verification, cross-vendor adapter calls. | H2-2026 |
| Cortex API | Memory persistence, audit-trail query, Action-Gate configuration. | H2-2026 |
Early access
Design-partner engineering teams get direct engineering contact, integration support, and a structured feedback loop into the public-API design.
Engineering evaluation
Cross-vendor benchmarks, Bit-Identity fixtures, integration discussion under NDA.
Request engineering evalCompress container
AWS Marketplace container or on-premise Helm chart, with engineering support for first integration.
Talk to developer teamDesign principles
Already implemented in Compress v1.0.0-rc18 for the container surface. The public API inherits them on day one.
bcrypt-12 for credential hashing, OAuth2 for delegated access, mTLS for Tier 3 deployments. Customer-dashboard auth is production today.
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.
Every .aqpkg update artifact is post-quantum signed. The same signing discipline extends to API release artifacts.
No public endpoint ships without an explicit versioning contract (semver in the changelog, version in path or header).
Join the early-access program. Direct engineering contact, NDA endpoint access, and a structured feedback loop into the public-API design.