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

Yes. Write a rule that allows only the survey-read and response-read operations for one organization, so the agent can pull survey results and nothing else, and every call it makes is logged. If you later want it to create surveys as well, you add that one operation to the rule.

What authentication does the BoundaryAI API use?

The BoundaryAI API authenticates with a bearer API key passed in the Authorization header per its OpenAPI spec, while the dashboard web app signs in with a Clerk-issued session token. Through Jentic the key is stored encrypted by your own instance and added to each request at call time, so it never appears in the agent's prompt or logs.

Can I generate a survey with AI using the BoundaryAI API?

Yes. The API includes an AI survey generation operation that drafts a questionnaire from a short description, alongside the standard create-survey operation, so an agent can turn a prompt like 'a five-question post-purchase survey' into a ready draft it can then edit.

What are the rate limits for the BoundaryAI API?

Each BoundaryAI API key carries its own per-minute rate limit set on the key, as described in the OpenAPI spec; the spec does not publish a single fixed number for every account. For the limit that applies to your key, check the key's settings in the BoundaryAI dashboard under Integrations Hub.

How do I create a survey with the BoundaryAI API through Jentic?

Import the BoundaryAI API from the Jentic API Directory, then have your agent issue a request such as 'create a post-purchase survey for my store'. Jentic matches the intent to the create-survey operation and returns its input schema so the agent builds a valid request, with your stored API key injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.