put_v1_captable_company
UpdateCompany sets the caller org's company name and incorporation details.
UpdateCompany sets the caller org's company name and incorporation details. The name is required; the three incorporation fields are optional and each is stored as empty when omitted, so a call that sends only a name CLEARS them. The company row itself is seeded when the tenant's store first opens, so this never creates one.
| Tool | put_v1_captable_company |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 4 |
| Operation | PUT /v1/captable/company |
| Product | captable |
Arguments
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
incorporationCountry | any | — | — | IncorporationCountry is the ISO country the entity is incorporated in. Optional; omitted, null or empty clears it. Any JSON scalar is accepted and stored as its text. |
incorporationState | any | — | — | IncorporationState is the state or province of incorporation. Optional; omitted, null or empty clears it. Any JSON scalar is accepted and stored as its text. |
incorporationType | any | — | — | IncorporationType is the entity kind, e.g. LLC or C_CORP. Optional; omitted, null or empty clears it. Any JSON scalar is accepted and stored as its text. |
name | any | — | — | Name is the company's legal name. Required, and it must be a non-empty string — anything else is refused with the cap table's own validation error. |
This tool's schema does not declare which fields are required, nor any default, nor any enumerated value set. The columns above are empty because the door publishes nothing there, not because the answer is "none" — where a field is constrained, the constraint is stated in that field's own description.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Every declared argument is shown, because the door marks none of them required.
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": "put_v1_captable_company",
"arguments": {
"incorporationCountry": "<incorporationCountry>",
"incorporationState": "<incorporationState>",
"incorporationType": "<incorporationType>",
"name": "<name>"
}
}
}'Values are placeholders derived from each field's declared type. 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 |
|---|---|---|---|
cloud_put_v1_captable_company | PUT /v1/captable/company | captable | UpdateCompany sets the caller org's company name and incorporation details. |
The same capability over plain HTTP is in the captable API reference, on https://api.hanzo.ai.
All 834 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 834 tools captured 2026-08-01 (this build read the vendored copy; the door was unreachable).
How is this guide?