The LLM Gateway is in beta.
Choose a provider path
Append a provider path to your regional gateway base URL, for examplehttps://eu.gateway.smith.langchain.com/anthropic for direct Anthropic access in GCP EU:
Each path uses the provider key stored in the caller’s workspace. For secret names, see Provider authentication.
Gateway Credits models use the standard endpoint rather than a provider-specific path. These hosted models require no provider secret of your own.
Configure provider SDKs
Set each provider SDK’s base URL to its direct gateway path and use your LangSmith API key as the provider API key:Configure LangChain and Deep Agents
LangChain chat models and Deep Agents, including Deep Agents Code, reach these provider paths through theLANGSMITH_GATEWAY environment variable:
LANGSMITH_GATEWAY_API_KEY. Set it to the same key:
LANGSMITH_GATEWAY support requires these minimum Python package versions: langchain-anthropic>=1.5.1, langchain-baseten>=0.2.3, langchain-fireworks>=1.5.1, langchain-google-genai>=4.3.2, and langchain-openai>=1.4.1.ChatAnthropic calls https://gateway.smith.langchain.com/anthropic and ChatOpenAI calls https://gateway.smith.langchain.com/openai/v1. To route requests through the standard endpoint instead, see Send your first LLM Gateway request.
See also
- Send your first LLM Gateway request: use the standard API to call models across providers.
- Set up the LLM Gateway: configure provider secrets and access.
- View LLM Gateway traces: see where gateway traces appear and who can view them.
Connect these docs to your agent of choice via MCP for real-time answers.

