SDKs
Introspection ships SDKs for JavaScript, Python, and Rust. Use an SDK for application traffic and production evidence. For local authoring and platform operations, use the separate CLI reference.
These pages are exhaustive reference. For a complete product workflow, start with Integrate into a full-stack app. For the local-to-production workflow, use Agent development lifecycle.
Choose an SDK
| You are building | Start with | Package |
|---|---|---|
| A Node.js or TypeScript service, or a browser application | JS SDK | @introspection-sdk/introspection-node, @introspection-sdk/introspection-browser |
| A Python service or notebook | Python SDK | introspection-sdk |
| A Rust service | Rust SDK | introspection-sdk |
| A custom client without an SDK | API reference | — |
If you do not have a recipe yet, begin with the Quickstart.
Every SDK reads INTROSPECTION_TOKEN from the environment. See
Authentication for service accounts, browser token
brokering, and token exchange.
What the SDKs own
Your application embeds an SDK around a runtime, so it covers
the work a running agent does and the evidence it produces: tasks and runs,
files, shares, conversations, events, and metrics. They also resolve the
runtime, recipe, or experiment the code is running under, and can bracket their
own execution with an experiment’s start, end, and cancel — each language
page shows the call. For the experiment resource itself (create, arms, goals),
use the CLI or the API reference, and see
Experiments for what the arms mean.
The SDKs do not author recipes or administer projects. Use the CLI to create and operate runtimes, bindings, credentials, judges, and experiments.
Point an application at your own machine
While introspection dev is
attached, an application built on any SDK reaches your local recipe through its
ordinary calls with a development-scoped credential. See
Cloud-connected development
for the routing and failure rules.