Overview
Control which managed authentication routes members may newly configure, and understand the gateways behind model access.
Each member chooses how their agent reaches a model. This section covers the two org-level levers on top: which managed authentication routes members may newly configure, and how model gateways fit in.
Neither disables native agent use or an existing selection.
Agent authentication policy
Control which managed authentication routes members may newly configure, and read the Conflicts table.
Model gateways
How Proliferate's managed gateway works, and where self-hosted deployments attach their own.
The member-facing catalog of every supported agent lives in Agents. There is no separate admin agent list; that page is canonical.