apiblaze 0.21.19 → 0.21.21

package/README.md

@@ -1,6 +1,6 @@
 # apiblaze
 
-> **Superseded 2026-09-24** for throttling, quota and credits by `specs/TQC/final_throttling_quota_credits.MD`. Upstash is gone; anything below about Redis keys, Lua gates, leases-on-Upstash or the reclaim/reconcile crons is historical.
+> **Superseded 2026-09-24** for throttling, quota and credits by `specs/TQC/final_throttling_quota_credits.MD`. Upstash is gone; anything below about Redis keys, Lua gates, leases-on-Upstash or the reclaim crons is historical. Money history is the money ledger (`apiblaze billing history`, `apiblaze op ledger`).
 
 CLI for [APIblaze](https://apiblaze.com) — chat with your APIs, run them as serverless proxies, and let your customers self-serve keys, users & groups from your own site.
 
@@ -226,15 +226,15 @@ Every chat turn shows its cost.
 
 ### Producer — limits
 
-Three names, fixed: **rate limit** (requests per second — Standard mode is approximate per
-location and free, Strict is exact per consumer), **quota** (an exact count per fixed UTC
+Three names, fixed: **rate limit** (requests per second per consumer key — approximate per
+location, free, a burst may briefly exceed it), **quota** (an exact count per fixed UTC
 window) and **spend cap** (exact dollars per month). Every rate is shown with its 10-second
 figure beside it (`50/s (500 per 10 s)`), because that is the window the Standard limiter counts.
 
 | Command | What it does |
 |---|---|
 | `apiblaze limits get <project> [--version v]` | Show mode, rate limits, ceiling, quota, spend cap, credential quota |
-| `apiblaze limits set <project> [--rate n] [--end-user-rate n] [--mode strict\|standard] [--quota n --period daily\|weekly\|monthly] [--spend-cap usd] [--credential-quota n]` | Change any subset (`--quota none` / `--spend-cap none` clear). A rate above the self-serve ceiling is refused and the output prints the exact `limits request-max` command |
+| `apiblaze limits set <project> [--rate n] [--end-user-rate n] [--quota n --period daily\|weekly\|monthly] [--spend-cap usd] [--credential-quota n]` | Change any subset (`--quota none` / `--spend-cap none` clear). A rate above the self-serve ceiling is refused and the output prints the exact `limits request-max` command |
 | `apiblaze limits request-max <project> --rps n [--use-case "…"]` | Ask for a higher ceiling (instant to 1,000/s for a proven wallet; an operator approves above) |
 | `apiblaze limits usage <project> [--watch]` | The team quota meter: used / in use / limit / resets in. Per-project usage is not exposed by the API yet — the output says so |
 | `apiblaze config <project> limits.<key> [value]` | The same settings by key: `limits.mode`, `limits.consumerRps`, `limits.endUserRps`, `limits.ceilingRps` (read-only), `limits.quota.limit`, `limits.quota.period`, `limits.spendCapCents`. The old `throttling.*` keys still work for one release |
@@ -248,7 +248,7 @@ figure beside it (`50/s (500 per 10 s)`), because that is the window the Standar
 |---|---|
 | `apiblaze billing balance [--team]` | Available, in use (pre-paid to live requests), grace owed, status, auto-rebuy, last top-up. Numbers are shown only to the wallet owner |
 | `apiblaze billing topup <usd> [--team] [--open]` | Prints (or opens) the dashboard wallet page for that amount — card checkout runs in your browser session |
-| `apiblaze billing history [--since d] [--until d] [--project p] [--format table\|json\|csv] [--raw]` | Usage and exact cost as daily rollups, per consumer key; `--raw` = hourly |
+| `apiblaze billing history [--since d] [--until d] [--project p] [--limit n] [--before cursor] [--format table\|json\|csv] [--raw]` | The team's money ledger, newest first: pending lines (made by the wallet, not sent yet), then events (kind, amount, balance after) and 5-minute usage blocks (requests, amount); follows pages up to `--limit` (default 100) and prints a `--before` cursor when more remain. Then usage and exact cost per project as daily rollups; `--raw` = one usage row per 5-minute bucket |
 | `apiblaze billing rebuy on\|off\|status [--amount usd] [--threshold usd]` | Auto-rebuy: add `--amount` whenever available drops under `--threshold` |
 
 When a call is refused for money or limits, every command prints the same thing for the same