Skip to main content
Agents, experiments, and evaluators each keep their traces in a tracing project. Endpoints that read or manage that data identify the project by its ID. The SDKs and API call a tracing project a session, so a project ID is also a session ID. Resolve an agent to its project ID first, then pass the ID wherever an endpoint takes a project (session) ID. For example:
  • Querying runs, threads, and traces with project_ids
  • Reading or updating the project, and its views, insights, and alerts
Resolving an agent is in beta. It needs LangSmith 0.18.7rc1 or later, and is not supported on BYOC data planes yet. The examples need the following SDK versions:
  • Python: langsmith>=0.14.9
  • TypeScript: langsmith@>=0.10.13
  • Java: com.langchain.smith:langsmith-java 0.1.0-beta.26 or later
  • Go: github.com/langchain-ai/langsmith-go v0.28.0 or later

What you can resolve

Resolve any of the following to get the ID of its project:

Resolve an agent and query its runs

Resolve an experiment and query its runs

Pass the ID of the experiment. An experiment is its own tracing project, so the endpoint returns the experiment’s ID.

Resolve the evaluators and query their runs

Evaluator traces share one project per workspace, so the evaluators take no ID.

Errors

  • LangSmith returns a 404 if nothing in the workspace matches, if the agent is archived, or if you cannot read its project. An agent’s environments exist once the agent exists.
  • On a BYOC data plane, the endpoint returns a 501, because resolving is not supported there yet.

See also