post_v1_crm_companies

CreateCompany adds a company to the caller's org and answers 201 with the stored record.

CreateCompany adds a company to the caller's org and answers 201 with the stored record. A name is required; an empty currency defaults to USD.


Tool	`post_v1_crm_companies`
Door	`https://api.hanzo.ai/v1/mcp`
Method	`tools/call` (JSON-RPC 2.0)
Arguments	11
Operation	`POST /v1/crm/companies`
Product	crm

Arguments

Field	Type	Required	Default	Values	Description
`arr`	`integer`	—	—	—	ARR is annual recurring revenue in minor units (cents) of Currency.
`city`	`string`	—	—	—	City is the head-office city.
`country`	`string`	—	—	—	Country is the head-office country.
`currency`	`string`	—	—	—	Currency is the ISO code ARR is denominated in; empty defaults to USD.
`domainName`	`string`	—	—	—	DomainName is the company's primary domain, e.g. "acme.com".
`employees`	`integer`	—	—	—	Employees is the headcount.
`id`	`string`	—	—	—	ID names the company to update and comes from the path. A create ignores it: the server mints the id.
`idealCustomerProfile`	`boolean`	—	—	—	ICP marks the company as an ideal-customer-profile fit.
`linkedinLink`	`string`	—	—	—	Linkedin is the company's LinkedIn URL.
`name`	`string`	—	—	—	Name is the company name. Required.
`xLink`	`string`	—	—	—	XLink is the company's X (Twitter) URL.

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.

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_crm_companies",
         "arguments": {
           "arr": 0,
           "city": "<city>",
           "country": "<country>",
           "currency": "<currency>",
           "domainName": "<domainName>",
           "employees": 0,
           "id": "<id>",
           "idealCustomerProfile": false,
           "linkedinLink": "<linkedinLink>",
           "name": "<name>",
           "xLink": "<xLink>"
         }
       }
     }'

Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. arr, employees and idealCustomerProfile 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_crm_companies`	`POST /v1/crm/companies`	crm	Adds a company to the caller's org and answers 201 with the stored record.

The same capability over plain HTTP is in the crm 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).

post_v1_crm_companies

Arguments

Call it

The operation behind it

On this page