Partly liveWhat works today is listed first. What is still to come is listed under Not yet.

VZN SDK

Create a record in your own tenant from code, with types.

A typed client for the VZN API. TypeScript first: run agents, stream their steps, read and fork sessions, with types generated from the engine's own contract.

See it work

One request, one answer.

Example · scriptedPOST /v1/crm/records/Contact

Request

{
  "data": { "LastName": "Ndlovu", "Email": "thabo@example.test" }
}

Response

{
  "id": "rec_placeholder",
  "object": "Contact",
  "owner_id": "",
  "data": { "LastName": "Ndlovu", "Email": "thabo@example.test" },
  "created_at": "2026-11-04T09:12:00Z",
  "updated_at": "2026-11-04T09:12:00Z"
}

With the SDK

const contact = await vzn.crm.create("Contact", { LastName: "Ndlovu", Email: "thabo@example.test" });

The route and the record's shape are from the engine's own contract. The id and times are placeholders, and the person is made up.

How it goes

Three steps.

  1. Call the engineSend the request with your key. The key picks the tenant.
  2. The engine checks itA bad key, another tenant's data or a missing required field is refused, and the client says why.
  3. You get a typed recordThe response is the record as the engine stored it, with its history kept.
Evidence

What we can show, and where it comes from.

Types
Generated from the engine's OpenAPI contract, so they cannot driftSource: crates/vzn-gateway/openapi.json
Tested against
The real engine: tenant isolation, a bad key, rate-limit retriesSource: packages/vzn-sdk/test/engine.test.ts
Published
Not yetSource: architecture/products/VZN-Labs-SDK.md
Example · scripted
job_01HX2 billing.credit · 200 · R 35.00 · receipt kept

Every action leaves a receipt: who approved it, when, and the proof that it happened. Nothing is billed without an approval.

What you get

Results, not a demo.

  • Call the engine from code with full types, instead of hand-writing requests.
  • A key picks the tenant. Asking for another tenant's data is refused, and the client says so plainly.
Proposed pricing

The typed client is free; the API it calls is metered like the Hub.

Free

R0 / one-time

A typed TypeScript client over the routes developers already call.

  • Typed client
  • Desk token or scoped key
  • Same 401/403 auth lock

Usage

Most common

Metered

Pay for Kernel API usage at the registry's verified rates.

  • Inference at list price
  • Rand budgets
  • The meter's own ledger

Enterprise

Talk to us

Private endpoints and support.

  • Private endpoints
  • Support
  • Talk to us
Status

What runs today, and what is still open.

Works today

  • A typed TypeScript client for the engine API: run, stream, sessions, fork and generative-UI validation
  • Types generated from the engine's OpenAPI contract, so they cannot drift
  • Tested against the real engine, including tenant isolation, a bad key and rate-limit retries
  • A second client for the Kernel's inbox jobs and APPROVE, Studio and social routes, with hand-written types

Not yet

  • Publishing the package
  • The Kernel routes are tested against a fake server only, and skills and workflows are not in the client yet