LangSmith

Connect your client's LangSmith with a key they paste, and call its API through Operate As.

Connects by
Pasting a API key
Category
AI
Services
1
Tools
431
ServiceKey
LangSmithlangsmith

Connecting

Your client makes a API key in their LangSmith settings and pastes it on their link. Operate As tries it with LangSmith before saving it, and stores it encrypted. See Services connected with an API key.

Check they're connected
curl https://api.operate.as/v1/me/clients \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"
Response
[  {    "id": "6f1c2a7e-...",    "name": "Miller Dental",    "services": [      "langsmith"    ]  }]

Permissions

What the client readsPermission it asks for
Use the LangSmith key you paste, with only the access you gave that keyChosen on the provider's screen

Tools

Install LangSmith's typed package for your language:

pip install operate-as-langsmith
Run langsmith.add_basic_auth_members_to_current_org_api_v1_orgs_curr
curl -X POST https://api.operate.as/v1/actions/langsmith.add_basic_auth_members_to_current_org_api_v1_orgs_curr \  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "clientId": "6f1c2a7e-...",    "input": {}  }'

Every input, with its JSON Schema: GET /v1/actions/langsmith.add_basic_auth_members_to_current_org_api_v1_orgs_curr

Response
{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

Pass-through

Paths continue from https://api.smith.langchain.com/api/v1. Your Operate As key goes in Authorization; the client's access is added for you.

See Pass-through requests for the full request and response format.

Call any endpoint
curl "https://api.operate.as/v1/clients/6f1c2a7e-.../langsmith/sessions" \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"
Response
{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

When access ends

A key works until your client deletes it in LangSmith. They can paste a new one on the same link at any time, and your workflows carry on without changes.

See Keeping access alive and Removing access.

Calls answer, once the key is deleted
{  "status": 401,  "data": {    "…": "the service's own error"  },  "encoding": "json"}