Four of Crono's core objects go by one name in the interface and another in the API, in webhook payloads and in the MCP integration. If you are reading an endpoint reference or a webhook event and the object names look unfamiliar, this is why.
Keep this page open alongside the API reference at ext.crono.one/docs.
The four that differ
Company in the app is Account in the API
Contact in the app is Prospect in the API
Deal in the app is Opportunity in the API
Sequence in the app is Strategy in the API
Objects that keep the same name
Templates, Lists, Tasks, Pipelines, Notes, Users, Reports and custom fields are called the same thing in both places.
Lead
Lead has no equivalent in the Crono interface. It appears in the API and in webhook events only if your workspace is integrated with Salesforce, where it refers to the Salesforce Lead object. If you are not on Salesforce, you can ignore every Lead event and endpoint.
Where you will run into this
Endpoints — you create a company by posting to /Accounts and a contact by posting to /Contacts
Webhook events — the objectType field carries the API name, so a new company arrives as Account and a finished sequence as a Strategy event
MCP tools — tool names follow the API, so SearchAccounts searches companies and SearchProspects searches contacts
One practical note: when you update or delete a record through the API or MCP, use the record's ObjectId rather than its name. Names are not unique, and matching on them is the usual cause of the wrong record being changed.