Can I measure how AI assistants describe my brand with the Epovest API?

Yes. Create a tracker with POST /trackers, start the measurement, and trigger a survey with POST /trackers/{id}/survey, then read GET /trackers/{id}/scores for the score series and GET /trackers/{id}/responses for the raw answers each engine returned. Trackers survey engines such as ChatGPT, Claude, Gemini, Perplexity, and Grok.

Can the Epovest API suggest new keywords to track?

Yes. Read GET /trackers/{id}/discoveries to see the keyword suggestions Epovest discovered for a tracker, then curate them with POST /trackers/{id}/discoveries/accept, POST /trackers/{id}/discoveries/dismiss, and POST /trackers/{id}/discoveries/restore so future surveys follow the questions that matter.

What are the rate limits for the Epovest API?

The OpenAPI spec does not pin a rate-limit figure in a machine-readable field. Check the Epovest documentation at https://epovest.com/docs for current limits, and have your agent retry with backoff when the API signals that it is being throttled.

How do I set up brand-visibility tracking through Jentic?

Search Jentic for 'measure how AI assistants describe my brand' to load the tracker operations with their input schemas, create a tracker with POST /trackers, and trigger a survey with POST /trackers/{id}/survey. To run it on your own infrastructure, install Jentic One from its GitHub repo.

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

Yes. Epovest puts each resource id in the URL path, such as /trackers/{id} and /projects/{id}, so a rule can pin your agent to the trackers and projects it manages and to read operations like scores and discoveries. Write and spend actions, such as deleting a surface with DELETE /surfaces/{id} or topping up credits, stay out unless you add them, and every call the agent makes is logged.