Get billing
Read the workspace's billing state, on_us / billed / locked, whether a card is on file, the comp window, and the metered balance. Detailed invoices and changes stay in the billing UI.
Authorization
bearerAuth A personal access token from Settings > API tokens.
In: header
Header Parameters
A key you choose, such as a UUID, that makes this POST safe to retry. Within 24 hours the same key and request answers with the first successful answer and runs nothing, the same key with a different request answers 422 idempotency_key_reused, and a key whose request is still running answers 409 idempotency_key_in_use. A failed request keeps nothing, so the same key runs it again.
1 <= length <= 255Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Workspace slug.
Response Body
application/json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
curl -X POST "https://example.com/operations/get_billing" \ -H "Content-Type: application/json" \ -d '{ "workspace": "string" }'{}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}Read alert fire POST
Read one alert fire's detail. Pass a fireId to get that fire's header (rule name, reason, value, baseline, window, delivery status, the triggering call's sessionId) PLUS the rule's keyset-paginated 7-day fire history, the same payload the alert-fire detail page shows. Or pass an alertId (a RULE id from list_alerts) to read that rule's recent 7-day firing history directly. Use it to investigate a fire before deciding whether to retune the rule (update_alert) or summarise the pattern (summarise_alert_fire). Read-only and workspace-scoped, it never re-scores a call or changes a rule.
Get call metrics POST
Read the persisted metric results for one call (by sessionId). Returns each metric's key, engine, pass/fail or numeric score, and judge reasoning, the grid the Results panel renders. A rated metric such as csat has no pass/fail: its score is out of 100. Use this to inspect why a call failed before fixing a tool or prompt. If the call has no results yet, this returns an empty grid; call evaluate_call to compute it. Works for both real calls and simulated eval runs (same results table).