post_v1_usage_rollup_backfill
Backfill seeds the derived usage rollup from ledger history — the rows written before the incremental view existed, which that view can never capture. SuperAdmin only.
Backfill seeds the derived usage rollup from ledger history — the rows written before the incremental view existed, which that view can never capture. SuperAdmin only. Because the rollup accumulates, a second unguarded run would double every day it re-reads, so it refuses with 409 when the rollup already holds rows unless force=true is passed; forcing WILL double-count.
| Tool | post_v1_usage_rollup_backfill |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 2 |
| Operation | POST /v1/usage/rollup/backfill |
| Product | usage |
Arguments
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
before | string | — | — | Before bounds the seed to ledger rows written before this RFC3339 instant. Defaults to now; pass the incremental view's creation instant so the seed and the live view never overlap and double a day. |
force | string | — | — | Force must be exactly "true" to seed a rollup that already holds rows. It is spelled as a string, not a flag, because the guard has always compared this value literally — "1" and "yes" do NOT force. |
This tool's schema does not declare which fields are required, nor any default, nor any enumerated value set. The columns above are empty because the door publishes nothing there, not because the answer is "none" — where a field is constrained, the constraint is stated in that field's own description.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Every declared argument is shown, because the door marks none of them required.
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "post_v1_usage_rollup_backfill",
"arguments": {
"before": "<before>",
"force": "<force>"
}
}
}'Values are placeholders derived from each field's declared type. tools/list needs no credential; tools/call does — called without one the door answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →
The operation behind it
| Operation | Route | Product | Summary |
|---|---|---|---|
cloud_post_v1_usage_rollup_backfill | POST /v1/usage/rollup/backfill | usage | Backfill seeds the derived usage rollup from ledger history — the rows written before the |
The same capability over plain HTTP is in the usage API reference, on https://api.hanzo.ai.
All 834 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 834 tools captured 2026-08-01 (this build read the vendored copy; the door was unreachable).
How is this guide?