The categories and what one call in each costs, in units.
Needs scope usage:read.
bearerAuthorizationBearer <token>An access token from the identity provider: a person's, or a customer's from the client credentials grant with an API key (developers.inorbit.hr). The gateway verifies it; the audience is iohr-api.
page_size?integerint32page_token?stringiohr.accounts.v1.ListUnitCategoriesResponse
application/json- response
iohr.accounts.v1.ListUnitCategoriesResponse
categories*array<>next_page_token*stringimport { ApiError, Public } from "@inorbithr/sdk";// Reads INORBIT_TOKEN, or INORBIT_KEY_ID and INORBIT_KEY_SECRET.const api = Public.fromEnv();try { for await (const unitCategory of api.accounts.allListUnitCategories()) { console.log(unitCategory); }} catch (e) { if (!(e instanceof ApiError)) throw e; console.error(`${e.code}: ${e.problem} (request id ${e.raw.requestId})`);}npm install @inorbithr/sdk. Calls the package's public surface; an operation newer than your package needs the next release or a client generated for your account. The SDKs.
{ "categories": [ { "description": "string", "name": "string", "units_per_1k_tokens": "string", "units_per_call": "string", "updated_at": "string" } ], "next_page_token": "string"}Get usage by day GET
What the account used, by day, service and metric: the last 30 days unless `from` and `to` say otherwise, at most 366 days. A key reads its own account. Needs scope `usage:read`.
Summarise what happened GET
What happened on the account in a window of time: the incidents that opened and resolved, the monitors that went down and came back, and the decisions that ended. Built from the platform's own records, never by a model, so the same window always gives the same answer. `lines` and `markdown` say it in plain words, with links to the console. Needs scope `summaries:read`.