A stable developer surface for AI systems that must survive contact with production.
Nexus SDK and its runtime variants give product teams typed clients, workflow adapters, and enterprise defaults for building against the VortexAQ platform.
Move faster without turning every application team into an AI infrastructure team.
Give product teams a typed surface, not a pile of gateway conventions.
The SDK page needs to feel like something an application engineer can adopt this week: typed clients, runtime variants, and audit context that moves through the code instead of living in a separate console.
~$ pnpm add @vortexaq/nexus-sdk && npx vortex init[ok] Resolving nexus-sdk contract...[ok] Bound signal: Build surfaceimport { Nexus } from "@vortexaq/nexus-sdk";const nexus = new Nexus({ project: "clinical-review" });const result = await nexus.responses.create({ model: "policy:best-text", input: "Extract actions and owners from this review.", audit: { workflow: "case-intake", reviewer: user.id },});Artifacts: typed model clients · workflow adapters · audit context propagation- Use one SDK across server, edge, and worker runtimes.
- Carry policy and audit context through application code.
- Ship durable agent and copilot flows without rebuilding gateway plumbing.
- typed model clients
- workflow adapters
- audit context propagation
Move faster without turning every application team into an AI infrastructure team.
Deployment briefing ↗Primitives your teams ship against.
Concrete behaviors and interfaces so security, platform, and product teams share one operational picture.
Typed clients for model calls, projects, keys, and usage metadata
Framework variants for server, edge, worker, and constrained deployments
Policy and audit context propagation through application code
Reference patterns for durable agents, copilots, and human-in-the-loop flows