AI Gateway Apps
An app represents one caller of your AI Gateway—a service, an agent, or a feature in a larger codebase. A support chatbot on your website is one app; the batch job that summarizes tickets overnight is another. Each app belongs to a team and can reach the AI providers assigned to that team.
Each app has three things of its own:
- An API URL—the endpoint the app's code calls, shown at the top of the app page. The gateway attributes requests made to this URL to the app, tracking usage independently per app. See the Universal API.
- An API key—authenticates the app's requests when the gateway runs the authentication policy.
- A policy chain—the ordered policies that run on the app's requests: model access, budgets, caching, guardrails, and custom policies. The chain starts out empty unless the app's team has a policy template.
API Keys
Each app has its own API key, which the gateway validates when the
authentication policy applies. The key is
optional: the gateway attributes usage by app ID, resolving it either from a
validated key or from the {app_id} segment of the request URL, so an app
without authentication still tracks usage independently.
To find an app's API key, open the Apps tab of your AI Gateway project in the Zuplo Portal and select the app. The API key appears in the API Key section at the top of the app page.
Additional Resources
- Creating & Editing Apps - How to add, remove, and set roles for project members.
- Creating & Editing Teams - How to create and edit teams.
- Role Permissions - Details on the roles available at the account and project levels.