Nouveau API

API keys can be limited to some areas, one team and an expiry

When you create an API key, you choose which areas it can read or change, whether it works in one team only, and when it stops working.

Creating an API key now opens its own page. You choose what the key can reach: every area, or only the areas you pick, each with Read or Read and write. You can pin the key to one of your teams, and choose when it stops working: in an hour, a day, 30 days, a year, never, or at a date and time you set, to the second.

The list of keys shows what each key can reach, its team, and when it expires or that it has expired. Keys made before this keep working in every area.

Through the API, any key can read its own limits (GET /api/v1/api-keys/current) and make a shorter-lived key with the same areas or fewer (POST /api/v1/api-keys), which stops working when the key that made it is revoked or expires. A limited key used with Magpie's MCP server reaches only its areas' tools.