For Agents
Programmatically get audit logs, get tracing project prebuilt dashboard. Covers 440 operations with apiKey, bearer authentication.
Use for: I need to audit logs, I want to tracing project prebuilt dashboard, Search for read tracer session, Find all tracer session
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the LangSmith, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with LangSmith API.
Get Audit Logs
Read Tracer Session
Update Tracer Session
Delete Tracer Session
Create Tracer Session
GET STARTED
Not supported: Does not handle payments, crm, or developer tools — use for communications only.
The LangSmith API is used to programmatically create and manage LangSmith resources. Host https://api.smith.langchain.com Authentication To authenticate with the LangSmith API, set the `X-Api-Key` header to a valid [LangSmith API key](https://docs.langchain.com/langsmith/create-account-api-key#create-an-api-key). The API exposes 440 endpoints secured with apiKey, bearer authentication.
Patterns agents use LangSmith API for, with concrete tasks.
★ Communications Operations
Use the LangSmith to perform communications operations programmatically. The API provides 440 endpoints covering core functionality including get audit logs, get tracing project prebuilt dashboard, read tracer session.
Call GET /api/v1/audit-logs to get audit logs
Automated Ace Management
Automate ace operations by combining multiple LangSmith endpoints. Agents can get tracing project prebuilt dashboard and then read tracer session in a single workflow.
Call POST /api/v1/sessions/{session_id}/dashboard to get tracing project prebuilt dashboard, then verify the result
AI Agent Integration via Jentic
AI agents discover and call LangSmith endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey, bearer tokens manually.
Search Jentic for 'get audit logs', load the operation schema, and execute with Jentic-managed credentials
440 endpoints — the langsmith api is used to programmatically create and manage langsmith resources.
METHOD
PATH
DESCRIPTION
/api/v1/audit-logs
Get Audit Logs
/api/v1/sessions/{session_id}/dashboard
Get Tracing Project Prebuilt Dashboard
/api/v1/sessions/{session_id}
Read Tracer Session
/api/v1/sessions/{session_id}
Update Tracer Session
/api/v1/sessions/{session_id}
Delete Tracer Session
/api/v1/sessions
Create Tracer Session
/api/v1/sessions
Read Tracer Sessions
/api/v1/sessions
Delete Tracer Sessions
/api/v1/audit-logs
Get Audit Logs
/api/v1/sessions/{session_id}/dashboard
Get Tracing Project Prebuilt Dashboard
/api/v1/sessions/{session_id}
Read Tracer Session
/api/v1/sessions/{session_id}
Update Tracer Session
/api/v1/sessions/{session_id}
Delete Tracer Session
Three things that make agents converge on Jentic-routed access.
Credential isolation
LangSmith apiKey, bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'get audit logs') and Jentic returns the matching LangSmith operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct LangSmith integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Twilio
Alternative communications API
Choose Twilio when you need a different approach to communications operations
Sendgrid
Alternative communications API
Choose Sendgrid when you need a different approach to communications operations
Pusher
Complementary communications API
Choose Pusher when you need a complementary approach to communications operations
Specific to using LangSmith API through Jentic.
What authentication does the LangSmith use?
The LangSmith uses apiKey, bearer authentication. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.
Can I get audit logs with the LangSmith?
Yes. Use the GET /api/v1/audit-logs endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the LangSmith?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I get audit logs through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'get audit logs'. Jentic returns the matching LangSmith operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the LangSmith have?
The LangSmith exposes 440 endpoints covering ace, agent builder, annotation queues operations.
/api/v1/sessions
Create Tracer Session
/api/v1/sessions
Read Tracer Sessions
/api/v1/sessions
Delete Tracer Sessions