Endpoints

Usage

Check your usage and remaining allowance

Read your own consumption for the current billing period. Usage is metered in three independent classes (see Rate limits & usage); this endpoint reports the running total in each so you can track an integration against its monthly allowance.

any valid key

This endpoint reflects your own account usage, so it needs no special scope — any valid key (parts:read or ai:run) can read it.

Get usage

GEThttps://api.zenode.ai/v1/usage

Response

JSON

1{
2  "period": {
3    "start": "2026-06-01T00:00:00Z",
4    "end": "2026-07-01T00:00:00Z"
5  },
6  "usage": {
7    "match_requests": {
8      "used": 1240,
9      "limit": null
10    },
11    "part_records": {
12      "used": 8830,
13      "limit": null
14    },
15    "ai_tokens": {
16      "used": 1820400,
17      "limit": null
18    }
19  },
20  "request_id": "req_3e90..."
21}

Parameter	Type	Required	Description
`period`	{ start, end }	Required	The current billing period (ISO-8601 UTC); usage counts reset at start
`usage`	object	Required	One entry per metering class — match_requests, part_records, ai_tokens
`request_id`	string	Required	For support / tracing

Each class entry is { used, limit }:

Parameter	Type	Required	Description
`used`	int	Required	Units consumed in the current period — MPN lines, part records returned, or LLM tokens
`limit`	int \| null	Required	The period allowance for this class; null until per-tier quotas are enabled with billing

Per-tier allowances and quota enforcement ship with billing — until then limit is null and used is informational. The per-minute throttle is separate and surfaced live on the X-RateLimit-* response headers (see Rate limits & usage).

Rate limits & usage — how each class is metered
Async AI jobs — per-job usage for AI token accounting

PreviousAsync AI jobs

Get usage

Response

Next