Scoped API key and spending limit (Admux)

A workspace owner or campaign manager creates keys in the Admux web app, and each key is shown once. Scopes decide what the key can do, from reading reports and drafting campaigns to reserving funds (campaigns:reserve) and launching (campaigns:launch). The full scope list is published at /v1/scopes. An expired or revoked key is rejected for every request, including pause and cancel; work it already got accepted, such as an automatic launch, continues under the authorization recorded at the time.

The spending limit caps new budget authorizations per UTC day, week, month or lifetime. It counts the budgets the key reserves, not money delivered, so it does not pace delivery; a request over the limit fails with KEY_ALLOWANCE_EXCEEDED.

This model contrasts with buying direct. Gravity issues one key per account, with no scopes and full access including spend.

Create one key per agent or integration so you can revoke one without stopping the others, and name keys after their job. Start with read scopes, add drafting, then reserving, and give launch only to keys whose output you have reviewed. Set the spending limit to the most you would accept that agent committing in a day or week; combined with Admux’s default review-before-launch mode, it lets an agent prepare campaigns while a person keeps the final say. Store keys in a secret manager, never in prompts, logs or public files. Key administration, payments and refunds remain human-only.