SDK implementation

Choose the SDK after trying the Public Test Sandbox when a TypeScript or Python client library fits your application. SDKs help with language-level API shape; the canonical v1.0 contract remains the source of truth for a new protocol integration.

Choose TypeScript or Python for your application. Before a live query, the selected SDK uses an issued Live Key owned by a serviceable Application.

Use the TypeScript SDK

Use the Python SDK

Credential mechanics

SDK setup does not define credential mechanics or change account access. For the authoritative guidance, see Authentication.

Choose a language

• TypeScript SDK for Node.js and JavaScript integrations.
• Python SDK for Python services and agents.

Local SDK verification

Use SDK mock mode only to validate client construction, request shape, and application error handling locally. A mock key works only in SDK mock mode; it is not a credential and cannot establish live access.

import { initialize } from "@agentoffernetwork/sdk"
 
const client = await initialize({ apiKey: "test-key", mode: "mock" })

from agentoffernetwork import SDKConfig, initialize
 
client = await initialize(SDKConfig(api_key="test-key", mode="mock"))

SDK handoff boundary

Installation and local mock verification are local checks, not live completion. Complete the selected language route only after the shared Application and Live Key access condition is met and its live query returns the canonical v1.0 success result.

For live access, review Production Access & API Keys and Authentication. These shared prerequisites do not choose a language for you.

For signature details, Open SDK Reference.

For a new HTTP integration, send the exact selector AON-Protocol-Version: 1.0 and validate the same Query / Offer contract before relying on SDK convenience methods. Treat the canonical v1.0 schema and generated SDK types as the Offer contract.