get_v1_company_register
ListRegister returns the platform's whole formation register, newest activity first — every org's formation, not the caller's.
ListRegister returns the platform's whole formation register, newest activity first — every org's formation, not the caller's. It is a Hanzo platform operation: a caller who is not a platform reviewer gets 403.
Filter by stage and structure, page with limit and offset. An unknown stage is refused with 400 rather than returning a silently empty page.
| Tool | get_v1_company_register |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 4 |
| Operation | GET /v1/company/register |
| Product | company |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
limit | integer | — | — | — | Limit bounds the page; 0 or less means the default of 200. |
offset | integer | — | — | — | Offset skips that many rows. |
stage | string | — | — | — | Stage keeps only formations at that stage. Empty means any. |
structure | string | — | — | — | Structure keeps only formations of that entity kind. Empty means any. |
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_company_register",
"arguments": {
"limit": 0,
"offset": 0,
"stage": "<stage>",
"structure": "<structure>"
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. limit and offset hold stand-ins that cannot be spelled that way — JSON gives a number, a boolean and a timestamp no placeholder form — so those values are this page's, not the API's. Neither the door nor the operation 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_company_register | GET /v1/company/register | company | Returns the platform's whole formation register, newest activity first — every org's… |
The same capability over plain HTTP is in the company 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_company
Get returns the caller org's formation and the stages reachable from it, or 404 when the org has not begun one.
get_v1_company_register_summary
SummarizeRegister counts the platform's formations by stage — the register's shape in one read, so a queue that is growing is visible as a number rather than inferred by paging the list.