Hanzo
Cloud MCPcloud

adminAnalytics

Is the SaaS product-analytics board over the caller's tenant window: active customers, new and churned, retention, MRR, ARPU, the usage trend and the top customers by spend — every number folded from

Is the SaaS product-analytics board over the caller's tenant window: active customers, new and churned, retention, MRR, ARPU, the usage trend and the top customers by spend — every number folded from the commerce ledger, not sampled.

The window is the caller's, not the fleet's: a SuperAdmin gets every org, a white-label admin only their own subtree (core.ScopedOrgs, the one scope predicate).

sources[] carries each upstream's freshness so a partial read is VISIBLE rather than silently low: a ledger that answered for only some orgs marks commerce-ledger degraded instead of publishing an undercount as healthy.

TooladminAnalytics
Doorhttps://api.hanzo.ai/v1/mcp
Methodtools/call (JSON-RPC 2.0)
Arguments1
OperationGET /v1/admin/analytics
Productcloud

Arguments

FieldTypeRequiredDefaultDescription
rangestringRange is the lower time bound: 24h, 7d or 30d. Anything else reads as the board's own default.

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": "adminAnalytics",
         "arguments": {
           "range": "<range>"
         }
       }
     }'

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

OperationRouteProductSummary
cloud_adminAnalyticsGET /v1/admin/analyticscloudIs the SaaS product-analytics board over the caller's tenant window: active customers, new

The same capability over plain HTTP is in the cloud 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?

On this page