Configure the boundary
Set API key, base URL, and organization through explicit flags or environment variables with documented precedence.
AuraOne Open / Hosted API integration
Integrate AuraOne without hiding credentials or release state.
Use typed sync and async clients plus a pipeline-safe CLI to call hosted AuraOne evaluation workflows from Python services, notebooks, and automation.
For Python engineers who need explicit base URL, organization, credential, output, error, and package-provenance contracts.
- License
- MIT; verify the license file for the selected source and package.
- Data boundary
- The SDK sends explicit API requests to the configured AuraOne base URL. API keys remain in the operator's environment and are never embedded in generated output.
- License
- MIT; verify the license file for the selected source and package.
- Runtime boundary
- The SDK sends explicit API requests to the configured AuraOne base URL. API keys remain in the operator's environment and are never embedded in generated output.
Product surface
The job, runtime boundary, and resulting artifact stay visible.
Inspect locally
Start from the source, then follow the reviewed README.
PyPI serves the verified 0.2.1 wheel and source distribution. Pin the exact version when reproducibility matters.
python -m pip install auraone-sdkAutomate predictably
Select table, JSON, or JSONL output; keep successful machine output on stdout and diagnostics on stderr.
Handle failures explicitly
Use stable exit codes and structured errors for authentication, authorization, validation, conflicts, rate limits, network failures, and server errors.
AuraOne Python SDK evaluation path
Source inspection, runtime testing, and release verification are separate checkpoints.
01
Inspect the package
Confirm source, license, package version, Python support, dependency metadata, and release workflow.
Repository and package metadata
02
Configure credentials
Provide the API key and optional base URL and organization through the documented environment boundary.
Local environment configuration
03
Run a read operation
Use JSON or JSONL output in automation and confirm stdout, stderr, and exit-code behavior.
Observed CLI result
04
Verify publication
Match the installed package, PyPI metadata, wheel and sdist digests, changelog, and source tag.
Verified PyPI and GitHub Release record
Evidence packet preview
AuraOne Python SDK evidence packet
The current release is trusted only when the source, artifact, runtime, and support records agree.
- Identity
- auraone-sdk package, source revision, version, and MIT licenseRepository and PyPI metadata
- Configuration
- AURAONE_API_KEY, AURAONE_BASE_URL, AURAONE_ORG_ID, and explicit CLI flagsCLI contract
- Automation
- Table, JSON, JSONL, no-color behavior, stdout/stderr separation, and exit codesCLI tests
- Publication
- Wheel, source distribution, hashes, clean install, tag, changelog, and trusted publisherRelease preflight and PyPI verification
Release evidence
Availability follows the evidence record.
Source access, package publication, binary integrity, and product captures are reported separately. Missing proof is shown as blocked, not inferred.
AuraOne Python SDK release decision
PyPI serves auraone-sdk 0.2.1 as a wheel and source distribution, the public v0.2.1 source tag resolves to the same release commit, and the GitHub Release carries the matching distributions and checksums.
auraone-sdk
PyPI wheel and source distribution / 0.2.1
The wheel and source distribution are public on PyPI and attached to GitHub Release v0.2.1 with checksums; the recorded digest is the wheel SHA-256.
SHA-256 40776ef3a2fef358f3e8ca80b7344378ceae616cccda9d3d1294b02d6bad3105