Skip to main content
GET
/
v1
/
api-keys
/
sub-keys
/
{key_id}
/
usage
Get Sub-Key Usage
curl --request GET \
  --url https://api.io.solutions/v1/api-keys/sub-keys/{key_id}/usage \
  --header 'Authorization: Bearer <token>' \
  --header 'x-api-key: <x-api-key>'
{
  "status": "succeeded",
  "data": {
    "key_id": "71775d2e-fbcc-4ef4-aa30-8aaeb82062c0",
    "credit_used": 1.234,
    "credit_limit": 10,
    "remaining_credit": 8.766,
    "credit_refresh_cycle": "monthly"
  }
}

Documentation Index

Fetch the complete documentation index at: https://io.net/docs/llms.txt

Use this file to discover all available pages before exploring further.

Use this endpoint to monitor whether a specific sub-key is approaching or has exceeded its credit limit. The remaining_credit field is null when no credit_limit has been configured for the key — in that case, the key is only bounded by the admin’s overall account balance.
Credit usage reflects settled payments processed by the billing pipeline. There may be a short lag (typically under a minute) between a completed inference call and the usage appearing here.

Authorizations

​
Authorization
string
header
required

The access token received from the authorization server in the OAuth 2.0 flow.

Headers

​
x-api-key
string
required

Admin API key that owns the sub-key. Admin API key (io.net Intelligence)

Path Parameters

​
key_id
string<uuid>
required

UUID of the sub-key to inspect.

Response

Successful Response

​
status
string
Example:

"succeeded"

​
data
KeyUsageData · object