Skip to content
EVENT / TOPICHistorical

LangSmith LLM Gateway Enters Public Beta for Agent Runtime Controls

1 reports1 sources10/22/2026 updated

Current overview (not historical)

AI overview

LangSmith LLM Gateway has entered public beta as a governance layer between agents and models, offering organization, workspace, and API key level spending limits, rate limits, model fallbacks, and sensitive data protection. The tool allows teams to unify model usage without code changes and avoid vendor lock-in. It is now available for Plus and Enterprise plan users, providing runtime controls for agents.

Written with AI from the reporting · updated 10/22/2026

Expand the detailed fact route and sources

Story route

A station-by-station route from the first public evidence onward; every station carries its own evidence and uncertainty.

  1. 1Unclassified fact stationOct 22, 00:00recorded Oct 22, 22:06single sourcerevised

    LangSmith LLM Gateway 进入公开 beta 版

    Read original source ↗ LangChain BlogReplay this moment in the explorer
    Evidence & revisions · 1 source records
    Subject:
    langchain
    Action:
    发布 LLM Gateway 公开 beta 版
    Object:
    提供给代理的运行时控制
    Occurred (fact side):
    Oct 22, 00:00
    LangChain Blog ↗Report pageRevision 2 · currently revised
    Published (valid side):
    Oct 22, 21:09
    First seen (known side):
    Oct 22, 22:06
    Fact stationSingle source · one-sided claimRevised

    Copy may have been revised later; time replay is bounded. Layer labels group reading only, not causation between layers.

Uncertainty marks flag where to check the sources; they are not proven causation.

Report timeline

Explore every side through dated source reports.

Oct 22
  1. LangChain BlogRelated fact: single sourceSource report revised
    LangSmith LLM Gateway launches public beta for runtime controls in LLM agents

    Report first recorded Oct 22, 22:06

    LangSmith LLM Gateway is now in public beta, acting as a central governance layer between agents and models to enforce runtime controls like spend caps, rate limits, model fallbacks, and sensitive data protections. These controls can be applied at Organization, Workspace, API key, and User levels, helping teams consistently govern model usage without vendor lock-in and preventing issues like cost overruns or outages.

    Read original source ↗

Event discussion

Reader opinions are hosted on GitHub Discussions; posting requires a GitHub account. Comments are not verified facts.

Open GitHub Discussions