Admin API

The Admin API lets you manage your Aivene account from code: inspect and update your API keys, pull usage reports, check your balance and transactions, and read your request logs.

https://api.aivene.com/v1/account

Admin keys

An Admin key can read your usage, billing and logs, and can switch your API keys off. Treat it like a password:

• Keep it on a server. Never ship it in a browser, a mobile app or other client-side code.
• Keep it out of apps, agents and workflows that send prompts. An agent that holds an Admin key can disable the API key it runs on.
• Give each Admin key an expiration, and delete Admin keys you no longer use. A disabled or deleted Admin key stops working immediately.

Authentication

Send the Admin key as a bearer token in the Authorization header:

curl https://api.aivene.com/v1/account/api_keys \
  -H "Authorization: Bearer $AIVENE_ADMIN_KEY"

Endpoints

API keys can't be created or deleted through the Admin API. Do that on the API Keys page.

Conventions

The Admin API differs from the rest of the Aivene API in a few places:

• Timestamps are RFC 3339 strings (2026-10-22T14:03:51.204Z), both in responses and in query parameters such as starting_at.
• Money is a decimal string in US dollars ("12.5"), always paired with currency: "USD", so no precision is lost.
• Every object has a type field (api_key, log, billing_transaction, ...).

Pagination

List endpoints return the newest items first, in this envelope:

{
  "data": [ ... ],
  "has_more": true,
  "first_id": "key_8fQ2LmV9xR4tN7wK1pZ3cB6dHs0J",
  "last_id": "key_2Hs0JcB6d1pZ3N7wKxR4tLmV9fQ8"
}

Pass at most one of after_id and before_id. Keep paging while has_more is true.

The usage report pages by time instead and uses a page token.

Errors

Errors use the same shape as the rest of the Aivene API:

{
  "error": {
    "message": "API key 'key_8fQ2LmV9xR4tN7wK1pZ3cB6dHs0J' not found",
    "type": "not_found_error"
  }
}