SDKs & CLI

Specification only — nothing on this page is built yet. The API is small enough today (three endpoints) that a raw fetch or curl call, as shown in the Quickstart, is the right tool. This page exists so the shape is decided before the surface grows, per §14 (Phase 3) of the architecture document.

When to build it

A generated SDK earns its cost once the API has enough endpoints that hand-written fetch calls become repetitive and error-prone across consumers — realistically once product endpoints exist alongside the registry ones (Phase 4+), not before.

TypeScript SDK — planned shape

Generated from the API’s route handlers via an OpenAPI schema, not hand-maintained — the fastest way for the SDK to drift out of sync with the real API is a human keeping it up to date by hand.

import { Nexora } from "@nexora/sdk";

const nexora = new Nexora({ apiKey: process.env.NEXORA_API_KEY });

const products = await nexora.products.list();
const sentinel = await nexora.products.get("sentinel");

• Typed request/response shapes generated from the same schema as the API Reference.
• Automatic retry with backoff on 429, honouring X-RateLimit-Reset.
• One package, published from this monorepo once the API stabilises past /v1.

CLI — planned shape

nexora login
nexora products list
nexora products get sentinel
nexora keys create --name "CI pipeline"

A thin wrapper over the TypeScript SDK, not a second implementation — it exists for scripting and CI, not as the primary integration path.

Other languages

Not planned until a customer asks. The API is plain JSON over HTTPS with bearer-token auth, so any language can call it directly today — see the API Reference.