post_v1_company
Begin starts the org's one formation and returns it with the stages reachable from it.
Begin starts the org's one formation and returns it with the stages reachable from it. It is idempotent: an org that already has a formation gets that one back with 200, while a first call creates it and answers 201.
| Tool | post_v1_company |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 4 |
| Operation | POST /v1/company |
| Product | company |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
alreadyIncorporated | boolean | — | — | — | AlreadyIncorporated declares an org that already has an entity, which takes the import path (POST /v1/company/skip) instead of the formation path. |
jurisdiction | string | — | — | — | Jurisdiction is the state of formation: DE or WY. |
name | string | — | — | — | Name is the proposed company name. |
structure | string | — | — | — | Structure is the legal entity to form: c-corp, llc or dao-llc. |
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",
"arguments": {
"alreadyIncorporated": false,
"jurisdiction": "<jurisdiction>",
"name": "<name>",
"structure": "<structure>"
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. alreadyIncorporated holds a stand-in that cannot be spelled that way — JSON gives a number, a boolean and a timestamp no placeholder form — so that value is 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 |
|---|---|---|---|
post_v1_company | POST /v1/company | company | Begin starts the org's one formation and returns it with the stages reachable from it. |
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_review
ReviewQueue reports the founders whose KYC is not yet settled, oldest formation first, so the queue drains in the order founders have been waiting.
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.