What authentication does the Assembly API use?

The API uses an API key passed in the X-API-KEY header. Jentic stores the key in its credential vault and injects it as the X-API-KEY header at execution time so it never enters the agent's context.

Can I create a new client through the Assembly API?

Yes. POST /clients accepts the client details and returns the new client ID. Use PATCH /clients/{id} to update contact information later, and DELETE /clients/{id} to remove a client. Companies can be linked separately via POST /companies.

What are the rate limits for the Assembly API?

The OpenAPI specification does not document explicit rate limits. Implement exponential backoff on HTTP 429 responses and avoid polling /clients or /companies in tight loops - cache results where possible since these records change infrequently.

How do I list overdue tasks through Jentic?

Search Jentic for 'list Assembly tasks' - the matching task-list operation will be returned. Load the operation schema, supply the client filter, and execute. Filter the response in the agent for tasks whose due_date is in the past.

Can I attach notes to a client record?

Yes. POST /notes creates a note tied to a client or workspace, and GET /notes lists existing notes. Notes are useful for logging onboarding milestones, status updates, and call summaries against the client record.

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

Yes. Because you run Jentic One yourself, your own rules decide which Assembly operations and which stored API key the agent may use. Assembly reaches clients and companies through collection endpoints and request bodies rather than a resource ID in the URL path, so you can restrict the agent to only the operations it needs, such as listing or creating clients. If you do not grant it, patching a client with PATCH /clients/{id} is not available to the agent.