DEV · 01
REST API
The endpoints, named.
Create and list runs, evidence, exports, and reviewed clips. Same response shape every time, retry-safe. Error model, pagination, and versioning in the reference.
STARTS FROM · Endpoint reference
OPEN →DEVELOPERS
Every call carries its proof.
Typed SDKs for TypeScript and Python. Signed webhooks. A REST surface where every run, every reviewed clip, and every export keeps the consent and provenance chain attached so your data, packets, and handoff terms survive an audit.
SESSION · run.completed
SDKS
2
WEBHOOKS
Signed
CONNECTORS
16
SDKS
2 typed clients
TypeScript and Python. Same response shape across runs, webhooks, and exports.
REST API
Named endpoints
Create and list runs, evidence, exports, and reviewed clips. Error model, pagination, and versioning in the reference.
CONNECTORS
16 connectors
CI gates, archives, incident response, and operator channels — signed delivery, verified payloads.
DEVELOPER SURFACES
Start where your work lands.
The REST surface, signed webhooks, robotics capture, and governed evidence handoff. Each card opens the reference you need next.
DEV · 02
WEBHOOKS
Signed delivery you can verify.
Every event is HMAC-signed: run.completed, export.ready, review.escalated, alert.created. The signature is how the consent and provenance chain survives once the event leaves us.
STARTS FROM · Event catalog
OPEN →DEV · 03
ROBOTICS
Robotics, same contract.
The reviewed unit is a clip, not a loose video: session, consent, license scope, safety signals, provenance. Capture schema, export formats, and live teleop, ready to call.
STARTS FROM · Capture · export · teleop
OPEN →DEV · 04
INFRASTRUCTURE
Promote with proof. Keep the record.
A governed train-register-deploy path where promotion has reviewer evidence attached. Start from reviewed work and keep the review trail.
STARTS FROM · Train · register · deploy
OPEN →FIRST COMMANDS
Three lines to your first call.
Install the SDK, set your key, make the call. Get a key in the console, set the scopes the run needs, rotate it there too. The response shape is the same across both clients.
INSTALL
npm install @auraone/sdk
import { AuraOneClient } from "@auraone/sdk";
// Get a key in the console, set the scopes the run needs.
const client = AuraOneClient.withApiKey(process.env.AURAONE_API_KEY!);
const run = await client.evaluations.create({
template_id: "rubric.web.qa",
agent_bundle_url: "s3://auraone-demo-artifacts/web-qa/agent-bundle-2026-05.zip",
wait: false,
});
// run.id, run.status — and the consent and provenance chain
// stays attached to every object you create from here.
console.log(run.id, run.status);SDK · @auraone/sdk · auraone-sdk · same response shape
DEVELOPERS
Bring the work. Keep the proof.
Typed clients, named endpoints, signed delivery. Reviewed real work becomes evidence that survives an audit. When EU AI Act enforcement begins in August 2026, the provenance is already attached.
↳ STARTS WITH
An install command, an API key with the right scopes, and the first reviewed run.
↳ LEAVES WITH
A typed client, a signed webhook, and every object carrying its consent and provenance chain through an audit.