Install a matching runtime SDK
Use a matching source checkout or an operator-provided release artifact. A local build is not evidence that an npm, PyPI, plugin, or marketplace release is public. Confirm the artifact version and checksum with its provider before installation.
TypeScript from a source checkout
From the checkout's core directory, build the locked SDK and then install it in your own application. Node.js 24 or later is required by this source version.
cd sdk
npm ci
npm run build
cd /absolute/path/to/your-application
npm install /absolute/path/to/core/sdk
For an operator-provided package, replace the final path with the exact local .tgz path. Do not use an unverified package name as a substitute for an unavailable release.
Python from a source checkout
Use a dedicated environment. The base SDK supports Python 3.9 or later; the LangGraph recipe requires Python 3.10 or later. A framework recipe may require a newer interpreter and its own pinned dependencies.
python3 -m venv .venv
. .venv/bin/activate
python -m pip install /absolute/path/to/core/sdk-python
For an operator-provided wheel, use its exact local .whl path. The LangGraph profile identifies the existing approval and restart recipe. Follow the matching recipe's framework prerequisites; installing the base SDK alone does not install every framework adapter.
Connect a path you can test
Set the deployment's API origin, organization ID, and an appropriately scoped runtime credential through your local secret manager. Never place real credentials in a shared workflow or source file. Public browser signup does not mint a runtime credential automatically.
Register one agent in your workspace, then configure the chosen managed connection or registered protected HTTP target with an administrator. Test one harmless allow case, one denial, and one revoked credential. Native tools outside that selected path are outside the asserted scope.
Use a separate personal review credential for the action evidence quickstart. Protected-action reads require the organization's proof.actions feature and protected_actions.view; export needs additional role and permission checks. Registration on a free plan does not grant those entitlements.
The runtime catalog records capability by versioned profile. An action's actual grade comes from its evidence: a signed target receipt can support grade A only with its trust and binding checks; observation is not independent acknowledgment. A timeout can remain unknown.