AuraOne / Developers
Preparing SDKs, integrations, code examples, infrastructure guidance, and documentation.
AuraOne / Developers
Use typed TypeScript and Python clients, signed webhooks, and named REST endpoints for runs, reviewed clips, evidence, and exports.
Every object keeps the source, consent, reviewer, version, and handoff context required by the workflow. Current SDK versions and connector availability are listed below.
At a glance
Developer tools
Each path opens the current reference for the object, event, or workflow your team needs to implement.
Create and list runs, evidence, exports, and reviewed clips through versioned endpoints with a consistent error and pagination model.
Open endpoint referenceVerify run.completed, export.ready, review.escalated, and alert.created events before routing them into downstream systems.
Inspect event deliveryWork with reviewed clips that retain session, consent, license scope, safety signals, and provenance as one capture record.
Read the capture schemaTrace reviewed work through training, registration, promotion, serving, rollback, and customer handoff.
Review infrastructureFirst commands
The quickstart switches language without changing the API boundary or the evidence fields returned by the run.
npm install --save-exact @auraone/sdk@0.2.0import { AuraOneClient } from "@auraone/sdk";
const client = AuraOneClient.withApiKey(process.env.AURAONE_API_KEY!);
const run = await client.evaluations.create({
template_id: "YOUR_TEMPLATE_ID",
agent_bundle_url: "s3://YOUR_BUCKET/path/to/agent-bundle.zip",
wait: false,
});
console.log(run.id, run.status);npm distribution. Current version: 0.2.0. Entry point: AuraOneClient, VERSION, DEFAULT_CONFIG.
Package documentationPyPI distribution. Current version: 0.2.1. Entry point: AuraOneClient, AsyncAuraOneClient, GraphQLClient.
Package documentationOperating trace
Follow each object through scoped authentication, processing, review, delivery, and downstream verification.
01
02
03
04
The same steps apply whether the entry point is an SDK, REST endpoint, connector, or webhook.
01
Confirm the package, version, endpoint, event, and scope.
SDK manifest and endpoint reference
02
Use a source item that exercises the real criteria, review, and export path.
Request, response, and review result
03
Validate the signature, retries, idempotency, and archive destination.
Webhook and connector receipt
04
Record ownership, retention, failure handling, and the next release check.
Production ownership plan
Before launch
Confirm the interface, authentication, delivery behavior, ownership, and recovery path before launch.