ZuploZuplo
LoginStart for Free
  • Documentation
  • API Reference
Getting Started
    Develop in the portal
      1 - Setup Your Gateway2 - Rate Limiting3 - API Key Auth4 - Deploy5 - Dynamic Rate LimitingDynamic MCP Server - Quickstart
    Develop locally with the CLI
      1 - Setup Your Gateway2 - Rate Limiting3 - API Key Auth4 - Deploy5 - Dynamic Rate LimitingDynamic MCP Server - Quickstart
Concepts
API Management
AI Gateway
    OverviewGetting StartedSource ControlUniversal API
    Providers
    Teams
    Apps
      OverviewManaging AppsPolicy ChainsCustom PoliciesFallbacksUsage Limits
    Policies
    Cookbooks
    Integrations
MCP Gateway
MCP Server
Developer Portal
Development
Deploying & Source Control
Analytics
Observability
Networking & Infrastructure
Account Management
Programming API
Build with AI
Zuplo CLI
Migration Guides
Platform LimitsVersion Support PolicySecuritySupportTrust & ComplianceChangelog
powered by Zudoku
Apps

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, which controls dashboard access to the app. Access to AI providers is governed separately by the user's Zuplo account and Zuplo project roles. A Zuplo account contains one or more projects, and the AI Gateway is the Zuplo project that contains these providers, teams, and apps. See Role Permissions.

Each app has three things of its own:

  • An API URL—the endpoint the app's code calls, shown in full at the top of the app page. Expand it to see the ready-to-paste URL for each service the gateway mounts under the app—Chat Completions (v1/chat/completions), Responses (v1/responses), and Messages (v1/messages)—and copy the one your client needs. The Universal API lists which providers serve each endpoint. The gateway attributes requests made to this URL to the app, tracking usage independently per app.
  • 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, app-specific 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 & Teams tab of your AI Gateway project in the Zuplo Portal and select the app. The key lives on the app's API Key tab.

Rotate keys to revoke access

An issued app API key authenticates gateway traffic by the key itself. Changing a user's dashboard permissions or removing them from a team doesn't invalidate the key. To revoke access, rotate the app's API key and update authorized clients with the new value.

Additional Resources

  • Creating & Editing Apps - How to create, configure, and delete apps.
  • Creating & Editing Teams - How to create and edit teams.
  • Role Permissions - Details on Zuplo account, Zuplo project, and AI Gateway team roles.
Edit this page
Last modified on August 26, 2026
Policy TemplatesManaging Apps
On this page
  • API Keys