post_v1_company_advance
Advance runs the ONE guarded transition of the formation machine. It is the only door between stages: the actions populate data, this decides ordering.
Advance runs the ONE guarded transition of the formation machine. It is the only door between stages: the actions populate data, this decides ordering.
An edge the machine does not define answers 409; an edge whose guard is not yet
satisfied answers 422 naming what is missing. Reaching the terminal company
stage also records the incorporation on the canonical cap table, and that must
succeed before the transition is persisted.
| Tool | post_v1_company_advance |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 1 |
| Operation | POST /v1/company/advance |
| Product | company |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
to | string | — | — | — | To is the target stage: structure, founders, payment, documents, esign, genesis, import or company. |
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": "post_v1_company_advance",
"arguments": {
"to": "<to>"
}
}
}'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 |
|---|---|---|---|
post_v1_company_advance | POST /v1/company/advance | company | Advance runs the ONE guarded transition of the formation machine. |
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?
post_v1_company
Begin starts the org's one formation and returns it with the stages reachable from it.
post_v1_company_documents
GenerateDocuments renders the formation documents for the chosen structure and jurisdiction, ingests each into the org's data room, and submits the state filing through the filing seam.