Can I create a customer with its CRM ids through the Onboard API?

Yes. POST /customers takes a required name plus optional fields including website, external_id, sf_account_id, and hubspot_company_id, so the Onboard record links back to Salesforce or HubSpot. POST /customers/{id}/members then adds people with first_name, last_name, and email.

What are the rate limits for the Onboard API?

The OpenAPI spec does not specify rate limits. Check the Onboard documentation at https://onboard.io for current limits.

Is there an Onboard MCP server?

You don't need an MCP server to give your agent Onboard. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the project, task, and customer operations it needs on demand without loading another server's tool definitions into its context.

How do I add a task to an onboarding project through Jentic?

Search Jentic for 'add a task to an onboarding project', load the Onboard project tasks create operation, and execute it with the project id in the path and the task name and description in the body. Jentic attaches your API key. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Why do so many Onboard operations have short summaries?

The spec is generated from the Onboard backend, and many operations carry only their method and path, such as GET /projects/{id}/insights/summary, as the summary. The request body schemas are still declared, so field names like sf_account_id or event_type come from the spec, but check Onboard's own documentation for behaviour the spec does not describe.

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

Yes. Write a rule that allows only GET and POST on /projects/{id}/tasks for one project id, and the agent can read and add tasks on that project but cannot touch other projects, delete customers, or change webhooks, and every call it makes is logged.