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.
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.
With no filing partner wired the filing is recorded honestly as "manual" — no filing id is fabricated. Available only at the documents stage.
| Tool | post_v1_company_documents |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 0 |
| Operation | POST /v1/company/documents |
| Product | company |
Arguments
This tool declares no arguments. Call it with an empty arguments object.
Call it
A tools/call carries its arguments in one flat object. This tool declares none, so the object is empty.
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_documents",
"arguments": {}
}
}'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_documents | POST /v1/company/documents | company | Renders the formation documents for the chosen structure and jurisdiction, ingests each… |
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_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.
post_v1_company_esign
RequestEsign sends the generated formation documents for signature by every founder and records the provider's reference on the formation.