{"hiHint":"GET /help/:topic for details. Topics: api-keys, auctions, authentication, buckets, callback-allowlist, claims, classes, consuming, cors-allowed-origins, dashboards, delegation, deletion, depletion-warning, destinations, events, how-to-cushion-reservation, how-to-fleet-management, how-to-monitor-then-gate, how-to-per-customer-allowance, human:alerts, human:buckets, human:claims, human:delegation, human:integrating, human:topups, metadata, observability, openapi, receipts, replenishment, reservations, scopes, splitting, tenant, thresholds, topups, transfers, unspent-warning, webhook-validation, webhooks. GET /docs/llm.md returns the longer-form LLM/agent integration guide as plain text. A topic's heContent is plain text, always. Its optional heTramaj, when not null, is the same topic as tramaj markup for a client that renders it (the Console); agents can ignore it. Accounts, sign-up, plans and creating a tenant (which is where a first API key comes from) are handled by a separate account service in front of this instance, not by this API. Its own guide for agents: https://console-api.buckette.co/docs/llm.md","hiTopics":[{"htsName":"api-keys","htsSummary":"Create and manage API keys within your tenant"},{"htsName":"auctions","htsSummary":"Auctions on a bucket: participants bid a price for units (each round's winners get a carved-out child bucket and a key) or for the bucket itself (sold once, second price)"},{"htsName":"authentication","htsSummary":"How to authenticate requests with Bearer tokens"},{"htsName":"buckets","htsSummary":"Create and manage resource buckets"},{"htsName":"callback-allowlist","htsSummary":"Per-request callback URLs for Async consume/reserve/claims — an alternative to webhooks"},{"htsName":"claims","htsSummary":"Consume across several buckets at once — all-of, first-of, or queued"},{"htsName":"classes","htsSummary":"Consume classes: keep lower-value work away from the part of a budget that higher-value work will need"},{"htsName":"consuming","htsSummary":"Consume or check resources atomically"},{"htsName":"cors-allowed-origins","htsSummary":"Per-tenant browser origins allowed to call this tenant cross-origin, on a shared instance"},{"htsName":"dashboards","htsSummary":"Dashboards and monitors: what to read to draw one, and where the hosted Console keeps its own"},{"htsName":"delegation","htsSummary":"Bucket-scoped API keys — carve out a sub-budget for another operator"},{"htsName":"deletion","htsSummary":"Delete a bucket for good (two-phase: hidden now, erased in the background)"},{"htsName":"depletion-warning","htsSummary":"Be warned when the rate of spending runs a bucket out before its next refill"},{"htsName":"destinations","htsSummary":"Prove a webhook URL or domain is willing to receive buckette traffic"},{"htsName":"events","htsSummary":"Every event buckette emits: when it fires, delivery versus audit log, and the payload fields"},{"htsName":"how-to-cushion-reservation","htsSummary":"How-to recipe: hold back a safety margin near the end of a budget period"},{"htsName":"how-to-fleet-management","htsSummary":"How-to recipe: carve a bucket per agent out of a shared multi-dimensional pool"},{"htsName":"how-to-monitor-then-gate","htsSummary":"How-to recipe: check availability before acting, then retry until it's there"},{"htsName":"how-to-per-customer-allowance","htsSummary":"How-to recipe: a monthly allowance per customer under one shared monthly cap"},{"htsName":"human:alerts","htsSummary":"For people: low, critical, overflow and depleted alerts"},{"htsName":"human:buckets","htsSummary":"For people: what a bucket and a dimension are, Locking, Reporting and MeteredOverage, the maximum"},{"htsName":"human:claims","htsSummary":"For people: claims and reservations, an advanced mechanism for spending across several buckets or waiting in a queue"},{"htsName":"human:delegation","htsSummary":"For people: giving someone or something a bounded part of a bucket, and the four key rights"},{"htsName":"human:integrating","htsSummary":"For people: integrating buckette, delegating keys and origins to workflows and agents, and why notifications need setup"},{"htsName":"human:topups","htsSummary":"For people: topping a bucket up, schedules, carryover and overflow with worked numbers"},{"htsName":"metadata","htsSummary":"The buckette/ reserved bucket-metadata key convention"},{"htsName":"observability","htsSummary":"Audit logs, statistics, health check, Prometheus metrics, and CSV export"},{"htsName":"openapi","htsSummary":"Machine-readable OpenAPI 3.0 specification"},{"htsName":"receipts","htsSummary":"Signed receipts an external relying party can verify without a callback"},{"htsName":"replenishment","htsSummary":"Configure automatic or manual resource refills"},{"htsName":"reservations","htsSummary":"Hold resources without consuming them yet, then commit or cancel"},{"htsName":"scopes","htsSummary":"Permission scopes that control what each API key can do"},{"htsName":"splitting","htsSummary":"Allocate a child bucket and reclaim resources back to the parent"},{"htsName":"tenant","htsSummary":"Your own tenant: identity, limits, usage, and metadata"},{"htsName":"thresholds","htsSummary":"Monitor a bucket's balance independent of any specific request"},{"htsName":"topups","htsSummary":"Top a bucket up automatically from another one when it runs low"},{"htsName":"transfers","htsSummary":"Move an amount from one bucket to another, now or when the source can pay"},{"htsName":"unspent-warning","htsSummary":"Be warned before a scheduled reset discards what is left"},{"htsName":"webhook-validation","htsSummary":"Which outbound URLs buckette accepts, and why yours was rejected"},{"htsName":"webhooks","htsSummary":"Subscribe to bucket events via HTTP callbacks"}]}