post_v1_company_founders

SetFounders replaces the formation's founders. Each founder needs a name, an email and an equity share in basis points; every founder is (re)set to pending KYC, so a previously settled decision does not survive a change of the list.


Tool	`post_v1_company_founders`
Door	`https://api.hanzo.ai/v1/mcp`
Method	`tools/call` (JSON-RPC 2.0)
Arguments	1
Operation	`POST /v1/company/founders`
Product	company

Arguments

Field	Type	Required	Default	Values	Description
`founders`	`Founder[]`	—	—	—	Founders is every founding stakeholder. Each needs a name and an email, and equityBps between 0 and 10000 (1% == 100 bps).

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.

Object types

Founder is an object this tool's fields are made of, declared inside the tool's own schema and enumerated in full below.

Founder

Field	Type	Required	Default	Values	Description
`decidedBy`	`string`	—	—	—	DecidedBy is who settled a terminal KYC status: the provider name, or a reviewer's user id.
`email`	`string`	—	—	—	Email is the founder's email, and the key a KYC decision addresses a founder by — POST /v1/company/kyc/decision matches on it.
`equityBps`	`integer`	—	—	—	EquityBps is the founder's ownership in basis points, 0–10000 (1% == 100 bps, so 10000 is the whole company). The founders' shares seed the cap-table genesis.
`kycRef`	`string`	—	—	—	KYCRef is the idv provider's session reference for this founder.
`kycStatus`	`string`	—	—	—	KYCStatus is the founder's identity-verification state: pending, verified (a real idv provider reported a pass), reviewer_confirmed (a privileged reviewer confirmed out-of-band) or failed. The payment stage is unreachable until every founder passes.
`name`	`string`	—	—	—	Name is the founder's full legal name, as it appears on the formation documents.

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_founders",
         "arguments": {
           "founders": [
             {
               "decidedBy": "<decidedBy>",
               "email": "<email>",
               "equityBps": 0,
               "kycRef": "<kycRef>",
               "kycStatus": "<kycStatus>",
               "name": "<name>"
             }
           ]
         }
       }
     }'

Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. founders[].equityBps 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_founders`	`POST /v1/company/founders`	company	Replaces the formation's founders.

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).