Projects

A project groups API keys and gives them a shared budget, model lists and data policy. Every organization starts with one. Everything here is in the console under Projects. Owners, admins and members can create and change projects. Billing and viewer roles can read them, and see the controls disabled with the reason.

The project list

Each row shows:

Name and slug. The name opens the project's page.
Env: live or test.
Spend MTD: the month's spend so far. A test project shows unbilled.
Budget: spend against the monthly budget, or the daily one if there is no monthly budget.
Keys: how many active keys the project has.
Data policy: a short summary, or inherits org.
Status: active, paused, archived, or budget paused when a hard budget is spent.

Create a project

Press Create project.
Enter a Name. The Slug is the lower-case id used in addresses; leave it empty to have it made from the name.
Choose the Environment. Test projects route to the sandbox and are never billed.
Optionally enter a daily or monthly budget in USD, and choose whether it is a Hard budget.
Press Create project.

Model lists and the data policy are set on the project's page after it is created.

The project page

The page has five tabs. The selected tab is kept in the page address.

Overview

Overview shows the project's requests over the last 7 days, with successes and errors, and totals for requests, tokens and error rate. Beside it, Spend shows the month to date and today, against the budgets if there are any. A test project has no spend panel, because its requests are not billed.

Keys

Keys lists the project's active keys with their hint and status. Each name opens the key's page. Keys are created on the API keys screen.

Budget and alerts

On Budget & alerts, enter a Daily budget (USD), a Monthly budget (USD), or both, and press Save budget. Clear a field to remove that budget.

With Hard budget ticked, the project is paused when the budget is spent: requests fail with budget_exceeded until the period ends or you raise the budget.
With it cleared, the budget is soft: requests continue and you are only alerted.

A project's budget and each key's budget are separate ceilings, and whichever is reached first applies. The error names the project's budget when it was the one reached. Budget events go to your webhooks.

When a hard budget is spent, a red notice appears at the top of the project page saying whether the daily or the monthly budget ran out. Press Raise by 50 % there to raise that budget by half in one step.

Data policy

On Data policy, a project can only tighten the organization's policy. It cannot loosen it.

Payload logging: inherit from org, on or off. Off stores no request or response payloads.
Retention (days): 7, 30, 90 or 365. It cannot exceed the organization's retention.
Zero data retention: requests go only to endpoints that offer it, and nothing is stored.
No training on data: requests go only to providers that contractually do not train on them.
Redaction before archive: tick the presets to apply (email, phone, pan, aadhaar, card, api_key), and add custom patterns, one regular expression per line. Redaction applies to the stored copy only, never to what is sent to the provider.

Where the organization's policy already decides an option, the option is switched off here and says why: logging cannot be changed when the organization has it off, and zero data retention and no training are ticked and locked when the organization requires them.

Press Save data policy to apply. The organization's own policy is described in data policy.

Settings

On Settings you can:

change the project's Name;
set a Model allow-list of catalog ids or aliases, separated by commas. Empty allows every model. The field suggests ids from the catalog as you type;
set a Model deny-list. Deny wins over allow.

Routing policies are not set here. They are written and bound to a project on the routing screen.

Press Save settings to apply.

Archive or delete a project

Both are under Danger zone on the Settings tab, and both ask you to type the project's slug to confirm.

Archive project: the project's keys stop working and the project becomes read-only. Its history stays visible.
Delete project: removes the project and every key in it. This cannot be undone. If the project cannot be deleted, the error is shown and you stay on the project.

On this page