get_v1_research_totals
GetResearchTotals returns the caller org's headline aggregate plus a per-kind breakdown — the observatory's poll target.
GetResearchTotals returns the caller org's headline aggregate plus a per-kind breakdown — the observatory's poll target. Canonical and retained counts travel together, so a deduped view never reads as loss. ?project= narrows to one project.
| Tool | get_v1_research_totals |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 1 |
| Operation | GET /v1/research/totals |
| Product | research |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
project | string | — | — | — | Project narrows the aggregate to one project. Empty aggregates the whole org. |
tools/list declares a type and a description for each field and nothing further. A — means neither the door nor that operation constrains the field.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Nothing above is required, so every declared argument is shown rather than a guess at which matter.
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": "get_v1_research_totals",
"arguments": {
"project": "<project>"
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. 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 |
|---|---|---|---|
get_v1_research_totals | GET /v1/research/totals | research | Returns the caller org's headline aggregate plus a per-kind breakdown — the observatory's… |
The same capability over plain HTTP is in the research API reference, on https://api.hanzo.ai.
All 755 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 833 tools captured 2026-08-01, of which 755 are documented here (the operator surface is not published) (this build read the vendored copy; the door was unreachable).
How is this guide?
get_v1_research_projects
ListResearchProjects returns every research project in the caller's org with its real totals — canonical and retained side by side — which is the ops board's "every project + real totals" view.
post_v1_research_artifacts
RecordResearchArtifact records one research-diary artifact — a board snapshot or a generated report — CONTENT-ADDRESSED inside the trust boundary.