AuraOne / Developers
Preparing SDKs, integrations, and documentation.
AuraOne / Developers
Typed TypeScript and Python clients for current evaluation workflows, signed webhooks, and named REST endpoints for runs, evidence, and exports.
Enterprise workflow access, credentials, and approved connectors are scoped through design partnerships. Current public SDK versions and connector availability are listed below.
At a glance
Developer tools
The first card is the Enterprise Intelligence path. The remaining surfaces document the currently published evaluation API and delivery contracts.
Enterprise Intelligence has a canonical versioned workflow API for definitions, approvals, runs, traces, human exceptions, delivery, and acceptance. Customer access and live connectors remain scoped through design partnerships until production evidence is complete.
Plan a task-model integrationCreate and list runs, evidence, and exports through versioned endpoints. One error model, one 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. Each one keeps its session, its license scope, and its provenance as a single record.
Read the capture schemaTrace reviewed work from training through 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 from authentication through review, delivery, and downstream verification.
01
02
03
04
The same steps apply whether you start from an SDK, a REST endpoint, or a 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, the authentication, and the recovery path before launch.