Skip to main content
An AI Gateway public resource is a protocol-aware reverse proxy on a fully qualified domain name, like HTTP / HTTPS. Clients call that URL instead of OpenAI, Anthropic, Gemini, or another model API. Pangolin authenticates the caller, then forwards the request to an attached provider. This page covers how the resource works: reachability, authentication, and what you attach. Providers, keys, model routing, the catalog, and client setup live in AI Gateway.

​
How It Works

  1. You assign a FQDN on a domain managed in Pangolin and set the resource type to AI Gateway.
  2. You attach one or more org-level providers. The resource speaks the API formats those providers advertise.
  3. A user retrieves a virtual API key by visiting the URL in a browser and logging in, or from the Resource Launcher or https://app.pangolin.net/<org-id>/keys.
  4. Coding agents send that key to the same FQDN. Pangolin checks the key and proxies to the selected provider.
Visiting the URL in a browser is how you retrieve a key. Model calls still need the key in the request. A dashboard session cookie cannot proxy through the gateway.

​
Providers, Not Targets

AI Gateway public resources do not use HTTP targets. Traffic goes to providers configured under AI Gateway → Providers, then attached on the resource. Cloud APIs (OpenAI, Anthropic, and similar) need no site. Custom providers can use Site Targets when the model server sits on a site network. That routing is on the provider, not on the resource.

​
Authentication and Access Rules

Authentication is always on. You cannot turn Platform SSO off the way you can on an HTTPS resource. Assign users and roles the same way as a public HTTPS resource. Those grants control who can use an identity key. Manual keys grant access as soon as you create them, regardless of users and roles on the resource. When the call uses an identity key, or a manual key attributed to a user, Pangolin forwards that identity upstream as Remote-* headers. An unattributed manual key authenticates without sending them. HTTPS resources can add PIN, passcode, header auth, shareable links, or email OTP. AI clients authenticate programmatically, so this type uses virtual API keys instead of those methods. See Virtual API Keys and public authentication. You can still attach a resource policy for users, roles, and access rules.

​
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 HTTP / HTTPS, they can also share a FQDN because they all route to the gateway inside Pangolin. See Multiple Gateway Resources.

​
Compared to Private AI Gateway

For providers, keys, model routing, and connecting Claude Code, Codex, and other clients, see AI Gateway.