Trajectory SDK
Generated Python client for the Trajectory API, with high-level workflows for uploading trajectories, telemetry, and runtime-backed benchmarks.
Install
pip install trajectory-sdk
Install the optional agent and Harbor integrations used by the full CLI with:
pip install "trajectory-sdk[cli]"
Quick start
Set TRAJECTORY_API_KEY, then create a client:
from trajectory import Client
client = Client()
benchmarks = client.benchmarks.list(limit=10)
The generated resource methods map directly to the public HTTP API. Higher-level operations that
coordinate multiple API calls are available from trajectory.lib:
from trajectory import Client
from trajectory.lib import ingest_events
client = Client()
result = ingest_events(
client,
[
{
"event_type": "agent.completed",
"session_id": "session-123",
"timestamp": "2026-08-28T00:00:00+00:00",
"properties": {"model": "example-model"},
}
],
)
print(result.ingested, result.skipped)
LiteLLM harnesses
Starting with SDK 0.6.6, an existing LiteLLM harness can use this import for policy calls:
from trajectory.lib.litellm import completion
response = completion(model=model, messages=messages, temperature=1.0)
This always uses the injected Trajectory endpoint and credentials. Messages and tools are unchanged.
Keep user/judge calls on native LiteLLM and retain the original loop and grader, then report their
result with the existing
client.trajectories.log_reward(...) and client.trajectories.complete(...) methods.
Command line
The package installs a handwritten trajectory command that delegates API operations to the same
generated client and high-level workflows:
export TRAJECTORY_API_KEY="tj_key_..."
trajectory trajectories upload trajectories.json --dataset my-dataset
trajectory telemetry ingest events.json
trajectory traces upload trajectories.json --events events.json --dataset my-dataset
trajectory secrets set OPENAI_API_KEY
trajectory secrets list
API-backed commands use a 30-minute timeout by default. Override it with --timeout SECONDS.
The existing repository and benchmark tools remain available from the new CLI package:
trajectory bench validate ./benchmark
trajectory bench push ./benchmark --build-images
trajectory extract harness
Development
uv run pytest
uv run ruff check .
uv run ruff format --check .
The generated client lives in src/trajectory/. Handwritten workflows live in
src/trajectory/lib/, the handwritten CLI lives in cmd/trajectory/cli/trajectory_cli/, and tests live in
tests/.
License
1 maintainer
Release files for trajectory-sdk 0.6.9
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| trajectory_sdk-0.6.9.tar.gz | 108.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| trajectory_sdk-0.6.9-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 294.8 kB
Release files / trajectory_sdk-0.6.9.tar.gz
| Download URL | trajectory_sdk-0.6.9.tar.gz |
|---|---|
| Size | 108.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
66cbe310490bf156a2e9439d5f0c2c1186efb88d6cce13dce31f2838cf3934bd
|
|
BLAKE2b-256 checksum How to use checksums |
4e808d20b2619a2e944b594e8e075f10bb4395f517d7a2dcef261cf36d54667c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 12, 2026.
Transparency logRelease files / trajectory_sdk-0.6.9-py3-none-any.whl
| Download URL | trajectory_sdk-0.6.9-py3-none-any.whl |
|---|---|
| Size | 186.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
109ecdfd4b49d2228b5e014ebdbb901155a5b1c4cfb236a65e6486267a967b80
|
|
BLAKE2b-256 checksum How to use checksums |
3367bc09039912a84d56ef909ec2c9cd8ac8ef6ee282dddb74ce7b2553d4de40
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 12, 2026.
Transparency log
