How It Works
- You create a private resource with type AI Gateway on a Newt site and attach one or more org-level providers.
- You grant users, roles, or machines access, the same as any other private resource.
- The user connects with the Pangolin client. The machine running the AI client must be on that tunnel.
- The agent calls the resource URL. Pangolin attributes the call to the connected user and proxies to the selected provider.
none. Deleting the field usually breaks the client.
Providers, Not Destinations
Private AI Gateway resources attach providers on the resource’s AI Gateway tab. They do not use a host or CIDR destination as the model backend. Cloud APIs are called from Pangolin. Custom providers can use Site Targets when the model server is on a site network. Private resources, including this type, can only be created on Newt sites.Authentication and Access Rules
Access is the private resource model: grant users, roles, or machines explicitly. See Private Authentication. When the connected client maps to a user, Pangolin forwards that identity upstream asRemote-* headers.
More Than One Resource
Give different users and roles their own providers with more than one AI Gateway resource. Distinct hostnames are the usual approach. Unlike other private resource types, they can also share a FQDN because they all route to the gateway inside Pangolin. See Multiple Gateway Resources.Compared to Public AI Gateway
For providers, model routing, and connecting Claude Code, Codex, and other clients, see AI Gateway.

