post_v1_company_fundraise_round
RecordRound records a fundraising round on the org's canonical cap table.
RecordRound records a fundraising round on the org's canonical cap table. Available only after incorporation (stage company); roundType defaults to PRICED.
| Tool | post_v1_company_fundraise_round |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 6 |
| Operation | POST /v1/company/fundraise/round |
| Product | company |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
name | string | — | — | — | Name is the round's name on the cap table, e.g. "Seed". Required. |
preMoneyValuation | number | — | — | — | PreMoneyValuation is the valuation the round prices off, before the new money. |
pricePerShare | number | — | — | — | PricePerShare is the per-share price of a priced round. |
roundType | string | — | — | — | RoundType is PRICED, SAFE or CONVERTIBLE_NOTE. Defaults to PRICED. |
shareClassId | string | — | — | — | ShareClassID is the cap table's share class the round issues into. |
targetAmount | number | — | — | — | TargetAmount is the amount the round is raising, recorded verbatim on the canonical cap table's rounds.create contract. |
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_fundraise_round",
"arguments": {
"name": "<name>",
"preMoneyValuation": 0,
"pricePerShare": 0,
"roundType": "<roundType>",
"shareClassId": "<shareClassId>",
"targetAmount": 0
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. preMoneyValuation, pricePerShare and targetAmount 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 |
|---|---|---|---|
post_v1_company_fundraise_round | POST /v1/company/fundraise/round | company | Records a fundraising round on the org's canonical cap table. |
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?