canonical: https://jentic.com/apis/burthq.com/burthq # Burthq Burt Analytics API The Burt Analytics API runs organization-scoped analytics over agent runs and the attribution records that connect people to those runs. It exposes a catalog of the metrics and dimensions you can query, and an endpoint that runs a query against them. Access uses an organization API key that carries an analytics-read scope. ## For AI agents Read the analytics catalog of available metrics and dimensions, then run queries over your organization's agent runs and attribution records. ## Scope Does not handle event ingestion, user identity management, or billing. Use for querying agent-run analytics and attribution only. ## Capabilities - Retrieve the analytics catalog of available metrics and dimensions - Run analytics queries over your organization's agent runs - Report on the attribution records that connect people to agent runs ## Use cases ### Agent-built analytics query An AI agent asked for a metric about agent runs can first read Burt's catalog to learn the available metrics and dimensions, then build and run a valid query without guessing field names. Access is scoped to the organization the API key belongs to. Example prompt: Read the analytics catalog, then run a query of agent-run count grouped by day for the last week ### Attribution reporting A reporting agent can query the attribution records that connect people to agent runs, producing a breakdown of which sources drove activity. The query endpoint returns the organization-scoped result for the metrics and dimensions chosen from the catalog. Example prompt: Query attribution grouped by source for agent runs in the current month ### Catalog-driven dashboard refresh A dashboard automation can read the catalog to confirm the metrics it depends on still exist, then run each saved query to refresh the figures, so a renamed or removed dimension is caught before a query fails. Example prompt: Read the catalog, confirm the 'runs' metric exists, then run the saved daily-runs query ## Key resources - **Catalog** — Read the available analytics metrics and dimensions - **Query** — Run an organization-scoped analytics query over agent runs and attribution ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 72 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 93 / 100 - Developer Experience & Jentic Compatibility: 70 / 100 - AI-Readiness & Agent Experience: 56 / 100 - Agent Usability: 94 / 100 - Security: 60 / 100 - AI Discoverability: 88 / 100 - **View full report:** https://jentic.com/apis/burthq.com/burthq/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring Burt by hand means handling its bearer-token auth with an analytics-read scope and reading the catalog before every query so field names are valid. Through Jentic you install once, import Burt from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** You choose which Burt operations the agent may call: both the catalog and query operations are read-only, so you can grant analytics reads without exposing any write capability, because the API exposes none. - **Credential handling:** Your Burt token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'run an analytics query over agent runs', and Jentic returns the matching Burt operation with its input schema so the agent builds a valid query without reading the docs. ## Related APIs - **Amplitude** — Amplitude is a full product-analytics platform; Burt focuses on analytics over agent runs. - **Mixpanel** — Mixpanel analyses product events and funnels; Burt queries agent-run metrics and attribution. - **Segment** — Segment collects and routes event data; Burt queries analytics once it is stored. ## FAQ ### What authentication does the Burt Analytics API use? The Burt Analytics API authenticates with an organization API key sent as a bearer token in the Authorization header, per its OpenAPI spec. The key carries an analytics-read scope that governs the queries it may run. ### Is there a Burt Analytics MCP server? You do not need an MCP server to give your agent Burt Analytics. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the catalog and query operations without loading another server's tool definitions into its context. ### Can I limit what my agent is allowed to do with the Burt Analytics API? Yes. Both Burt operations are read-only, so a rule that allows the catalog and query operations lets the agent read analytics and nothing else, and every call it makes is logged. ### Can I query attribution with the Burt Analytics API? Yes. The query endpoint runs over the attribution records that connect people to agent runs, so an agent can produce a breakdown of which sources drove activity, scoped to your organization. ### What are the rate limits for the Burt Analytics API? The OpenAPI spec does not publish a numeric rate limit. Check the Burt documentation for the current limits before scheduling frequent dashboard refreshes. ### How do I run an analytics query with the Burt Analytics API through Jentic? Search Jentic for 'run an analytics query over agent runs', and it returns the Burt query operation with its input schema. Read the catalog first to pick valid metrics and dimensions, then run the query. To run it on your own infrastructure, install Jentic One from its GitHub repo.