SDKs
The Sparq SDKs, what each one does, and what is available today.
The SDKs are thin. They never hold model keys, evaluate policy or store memory: all of that stays in Sparq.
| Package | Language | What it is | Status |
|---|---|---|---|
@sparq/client | TypeScript | Types generated from the contract; HTTP client and streaming next | Types available to early-access teams |
@sparq/react | React | Chat kit: message list, composer with feature switches, approval and question cards | Next release |
@sparq/react-admin | React | Admin components: agent and skill editors, tool picker, diff, test results, approvals | Next release |
sparq-py (import sparq) | Python | Spec validation, draft pull and push, local runner and evaluation runner | Next release |
None of the packages is published to a public registry yet. Until they are, call the API over HTTP, as the guides show.
TypeScript types
The types are generated from the same OpenAPI document as this reference, so they always match the contract.
import type { Schema, paths } from "@sparq/client";
type Run = Schema<"Run">;
type RunStatus = Schema<"RunStatus">; // "queued" | "running" | ... | "error"
type StreamPath = paths["/v1/runs/{run_id}/stream"];Keys stay on servers
Whatever SDK you use, call Sparq with keys from your own back end. A browser or mobile app should call your back end, or send your user's own sign-in token.