Is there a Custify MCP server?

You don't need an MCP server to give your agent the Custify API. Jentic connects it directly from the API Directory: import it, store your bearer token once, and your agent calls the people, company, health score, and ticket operations. Operations are discovered on demand, so nothing extra loads into the agent's context.

Can I limit what my agent is allowed to do with the Custify API?

Yes. Many operations address a person, company, ticket, or other record by its ID in the URL path, so a rule can bound the agent to specific records as well as to specific operations. You might allow reading health scores and creating tasks while blocking company and people deletion, with every call logged.

Can the Custify API record product usage events?

Yes. The event operation inserts product usage events against a person or company, and the batch operation submits many requests at once, so an agent can feed usage signals into Custify to keep health scores and lifecycles current.

What are the rate limits for the Custify API?

The OpenAPI spec does not specify rate limits. Check the Custify documentation at https://docs.custify.com for current limits and batch guidance before running high-volume imports.

How do I update a company through Jentic?

Search Jentic by intent, for example 'create or update a company in Custify', and Jentic returns the matching operation with its input schema. Your agent supplies the company fields and reads back the result. To run it on your own infrastructure, install Jentic One from its GitHub repo.