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

Yes. Write a rule that allows reading contacts and conversations but not the send-message, enroll, or delete operations, so the agent can prepare outreach while a person approves anything that contacts a real lead, and every call it makes is logged. Because contact, list, and sequence ids are in the URL path, you can also bound the agent to one list.

What authentication does the ACA API use?

The ACA API authenticates with a bearer token, an organization-scoped aca_ API key sent as an Authorization header, per its OpenAPI spec; the token is frozen to one organization when it is created. Inbound webhook calls carry a separate x-webhook-secret header. Through Jentic the token is stored encrypted by your own instance and added at call time, so it never appears in the agent's prompt or logs.

Can I enroll leads into a sequence with the ACA API?

Yes. You enroll one or more leads into a sequence, then send messages and read the resulting conversation threads, so an agent can run an outreach cadence end to end. The lead pool search lets it build the target list before enrollment begins.

What are the rate limits for the ACA API?

The API is limited to 120 requests per minute per token, counted in fixed one-minute windows according to its own description, and exceeding it returns a 429 with a Retry-After header. For details and plan limits, see the ACA documentation at https://www.automatedclientacquisition.com.

How do I enroll a lead into a sequence with the ACA API through Jentic?

Import the ACA API from the Jentic API Directory, then have your agent issue a request such as 'enroll this lead into my onboarding sequence'. Jentic matches the intent to the enrollment operation and returns its input schema so the agent builds the correct request; because enrollment reaches real people, keep it behind your approval rules. To run it on your own infrastructure, install Jentic One from its GitHub repo.