Client API SDK Quickstart
This page is the SDK-first companion to/getting-started/client-api-quickstart.
Internal beta distribution model: SDKs are shipped as GitHub Release artifacts (not npm/PyPI yet).
1. Prerequisites
- OMNI Client API key (
omni_live_*) - recommended scopes:
mcp.tools.read,mcp.invoke,fred.read - GitHub CLI authenticated for artifact downloads
2. Install SDK artifacts
Artifacts are published inautonomous-computer/omni-system release tags:
JavaScript (pnpm)
Python (pip)
Integrity + compatibility artifacts (required)
3. Initialize, list tools, and call a tool
JavaScript
Python
Go (raw hosted MCP JSON-RPC)
4. Production retry wrappers
JavaScript (write-safe retry)
Python (write-safe retry)
5. Conformance gate before promotion
For release tags, OMNI runs live conformance against hosted MCP. You should run equivalent checks in your rollout pipeline.JS conformance
Python conformance
6. Non-optional production rules
- set explicit request timeouts
- retry only transient failures (
429,5xx) - reuse idempotency keys for retried write-like calls
- log request ids and structured SDK error metadata
- verify artifact checksums before promotion
- track SDK version + compatibility policy version together
7. Release promotion checklist
- download artifacts from approved tag
- verify
SHA256SUMS - verify
MCP_COMPATIBILITY_POLICY.md - run smoke flow (
initialize->tools/list->tools/call) - run conformance scripts
- validate billing semantics in canary
Related docs
/sources/client-api-sdks/sources/client-api-mcp-compatibility/sources/client-api-errors/sources/client-api-retries