Can I pull AI-visibility metrics and scores with the CiteHawk API?

Yes. The API lists the brands a workspace tracks, returns a daily metrics timeseries with the latest KPIs, and reports Visibility and Brand Health scores with history. It also returns the AI responses, with citations, that power those metrics.

What are the rate limits for the CiteHawk API?

The OpenAPI spec does not specify rate limits for the CiteHawk API. Check the vendor's documentation at https://www.citehawk.com for current limits before pointing an agent at it.

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

Yes. Write a rule that allows only the read operations, such as metrics, scores, and brands, so the agent reports on visibility but cannot start white-label prospect scans. Because the key is already scoped to one workspace, the agent cannot reach another tenant's data, and every call is logged.

Is there a CiteHawk MCP server?

You don't need an MCP server to give your agent the CiteHawk API. Jentic connects it directly from the API Directory: import it, store your workspace key once, and your agent calls the brands, metrics, and scores operations. You skip loading another server's tool definitions into the agent's context.

How do I pull AI-visibility data through Jentic?

Add the CiteHawk API from the Jentic API Directory and store your workspace key once. Your agent then searches by intent such as 'pull my brand's AI visibility metrics' and Jentic returns the matching operation with its input schema, so it can read the scores and the AI responses behind them. To run it on your own infrastructure, install Jentic One from its GitHub repo.