Skip to main content

Overview

The Management API lets you retrieve organization balance totals, manage organization API keys, and retrieve usage and billing for a specific key without using a standard inference API key. Use a management token from your Dashboard Settings page:
Management tokens are different from inference API keys. Use mt-... for /v1/management/*, and use sk-... for model inference endpoints such as /v1/responses.

Available Endpoints

Usage Filters

GET /v1/management/api-keys/{keyId}/usage supports the following query parameters: If both startDate and endDate are present, startDate must be earlier than or equal to endDate.

API Key Request Body

POST /v1/management/api-keys

PATCH /v1/management/api-keys/

At least one PATCH field must be provided.

Monetary Fields

  • Management API monetary request and response fields are USD-only.
  • limitCurrency defaults to USD; sending CNY returns 400 with currency_retired.

Reporting Semantics

  • model refers to the model requested by the caller.
  • modelVendor refers to the public model vendor, not provider-specific execution details.
  • scene is the public request scene derived from the endpoint or task type.
Responses expose public billing and reporting fields only. Provider execution details are not included in management responses.
  • /usage line items can include billing_transaction_id once the underlying request has reached settled billing state. Use request_id + billing_transaction_id for request-level reconciliation.

Billing Pagination Note

/usage is paginated. /billing is currently an aggregated breakdown endpoint and does not return page / limit style pagination metadata. If you need line-level records, use /usage.

Quick Example

First check the current organization balance with the management token:
Then list the API keys available to the same management token:

Next Steps