Request Usage · Token360

Returns a billing and metering summary for one inference call, keyed by the billing request id — the same UUID you see in response headers X-Request-ID and X-Trace-ID on that call (both headers use the same value).

Call the HTTPS base URL for your environment. Send credentials as Authorization: Bearer <API key> (sk-…) or with a user session JWT, consistent with other authenticated platform APIs.

Authentication

Authorization Bearer

Use an API key in the Authorization header (sk-…) or a user session JWT.

Path Parameters

request_idstringrequired

Billing correlation id: UUID from X-Request-ID / X-Trace-ID on the HTTP response for that inference call.

Query Parameters

typeenum<string>default:all

Optional. Omit entirely to search across all modalities (same as all). Use llm | image | audio | video only when resolving by request id alone could collide and you must narrow the row.

Available options: all llm image audio video

Response

The body uses the standard R<T> envelope (code, msg, data, traceId; serviceCode when present). On success, code is 200 and data is a billing reconciliation summary object (BillingRequestSummaryVO shape below). On failure, data is null.

codeinteger

200 on success; 404 when no record or no access.

msgstring

Human-readable message.

dataobject | null

Summary when successful; null on failure. Fields are as returned; many are optional and depend on what was recorded.

idstring

Canonical row id.

requestIdstring

Billing correlation id (typically matches the path when resolved).

typestring

e.g. llm, image, audio, video.

modelstring

Display model name.

modelNamestring | null

Model name when available.

statusstring

Task or request status when present.

createTimeinteger | string | null

Created time, epoch seconds (UTC); JSON may be string or number depending on serializer.

updateTimeinteger | string | null

Last update, epoch seconds (UTC); JSON may be string or number.

billedboolean | null

Whether usage has been charged (wallet / voucher / token path).

totalAmountnumber | null

Total charged amount when settled.

walletAmountnumber | null

Wallet-funded portion when applicable.

voucherAmountnumber | null

Voucher-funded portion when applicable.

billRecordStatusstring | null

Billing status when present.

statusCodestring | null

Recorded HTTP / status code string on usage row when present.

pricenumber | null

Vendor list price snapshot on the usage row when present.

billingAtinteger | string | null

Billing timestamp as epoch seconds when present; JSON may be string or number.

amountBasenumber | null

Amount before discounts (rating pipeline), when present.

amountFinalnumber | null

Final rated amount before wallet split, when present.

currencystring | null

Currency for rated amounts, when present.

usageobject | null

Merged metering for reconciliation: token counts, nested usage, duration tiers, etc. (no heavy explain / trace blobs).

durationnumber | null

Generation duration in seconds when known.

traceIdstring | null

Server trace id when available.

serviceCodestring | null

Stable service error code when applicable.

Results are limited to the authenticated user and that user’s own API keys (no cross-account access).

Error handling

401 / unauthenticated: missing or invalid Authorization.
code 404: unknown request_id, or no access (other users’ ids are not disclosed).
Charges can land slightly after the model response; a short-lived 404 may mean the ledger row is not written yet.

Request ID (billing correlation)

X-Trace-ID and X-Request-ID on each inference response carry the same UUID; downstream billing stores it as requestId when a billing event exists.
You may send X-Request-ID or X-Trace-ID on the request to pin your own correlation id; otherwise the platform generates one.
Do not use the chat JSON id (chatcmpl-…) or the video resource id (video_…) as this key. For video, persist headers from POST /v1/videos — each GET poll is a new HTTP trace.
For video tasks, GET /v1/videos/{video_id} (or equivalent polling) may include a usage object after the task reaches a terminal status, useful for meter-only checks beside this billing endpoint.