Skip to main content

​
What this is for

AI Gateway → Apps is where you register each application or agent that calls your gateway. This is identity only: an app is a name you can attach keys and policy to. What actually gets enforced for an app is authored in Policy, and its keys live in API Keys. Registering apps lets you attribute traffic, spend and policy per application rather than per raw key — so “the support bot” and “the batch summarizer” are governed and reported separately.

​
Options

Each app row shows its name, the policies scoped to it (click one to open it in the policy editor), and icons for what those policies configure.

​
How to configure

1

Open Apps

AI Gateway → Apps → New application.
2

Name the app

Enter a Name and an optional Description, then create it. No policy or key is required yet — the app is just an identity.
3

Author its policy

Open Policy and scope a policy to the app (guardrails, model and provider limits, budget, and more). A policy scoped to the app appears on the app’s row.
4

Issue keys

Create API Keys bound to the app; requests made with those keys inherit the app’s policy.

​
Limits

Deleting an application also deletes every policy bound to its scope (the dialog warns first). Re-scope those policies to another app or the baseline first if you want to keep them.
  • Policy — what gets enforced for each app.
  • API Keys — the keys that carry an app’s identity.
  • FinOps — per-application spend.