Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cookie Free Analytics read API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcookiefreeanalytics.com%2Fcookie-free-analytics" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcookiefreeanalytics.com%2Fcookie-free-analytics" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Cookie Free Analytics read API.
List the sites on an account
Read a site overview of visitors, visits, pageviews, bounce, and duration
Read the top pages and top sources for a site
Read live activity for a site in the last five minutes
Read linear same-day funnels on Growth-plan sites
GET STARTED
Read uptime watch state and incidents on Starter-plan sites
Patterns agents use Cookie Free Analytics read API for, with concrete tasks.
★ Agent traffic summary
An AI agent connected through Jentic reads a site's overview and top pages, then writes a short plain-language summary of visitors, pageviews, bounce, and duration for a human. Because Cookie Free Analytics returns only aggregates, the agent never handles raw visitor data to produce the summary.
Read the overview and top pages for a given siteId and summarize the week's traffic in two sentences
Acquisition source reporting
Marketing teams read the top sources endpoint to see where visits come from and compare it to published content. The aggregated source list lets an agent build a referrer breakdown without touching cookies or individual sessions.
Pull the top sources for a site and rank them by share of visits
Uptime and incident check
On Starter-plan sites an agent reads the watch state and open incidents alongside traffic, so a status report can note both how many visitors arrived and whether the site had downtime. The watch endpoints report uptime, TTFB, and TLS state plus any incidents.
Read the watch state and list any open incidents for a given siteId
8 endpoints — the cookie free analytics read api returns the aggregated traffic figures a site owner already sees on the dashboard, without cookies, visitor hashes, or raw per-visitor rows.
METHOD
PATH
DESCRIPTION
/api/v1/sites
List the sites on the account
/api/v1/sites/{siteId}/overview
Read visitors, visits, pageviews, bounce, and duration
/api/v1/sites/{siteId}/pages
Read the top pages
/api/v1/sites/{siteId}/sources
Read the top traffic sources
/api/v1/sites/{siteId}/funnels
Read linear same-day funnels (Growth)
/api/v1/sites/{siteId}/watch
Read uptime watch state, TTFB, and TLS (Starter)
/api/v1/sites
List the sites on the account
/api/v1/sites/{siteId}/overview
Read visitors, visits, pageviews, bounce, and duration
/api/v1/sites/{siteId}/pages
Read the top pages
/api/v1/sites/{siteId}/sources
Read the top traffic sources
/api/v1/sites/{siteId}/funnels
Read linear same-day funnels (Growth)
/api/v1/sites/{siteId}/watch
Read uptime watch state, TTFB, and TLS (Starter)
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Cookie Free Analytics API by hand means issuing a cfa_live_ token, learning the per-site path layout, and knowing which endpoints need the Starter or Growth plan. Through Jentic you install once, import Cookie Free Analytics from the API Directory, store the token once, and your agent calls it.
Permission scoping
Cookie Free Analytics puts the siteId in the URL path (/api/v1/sites/{siteId}/...) and is read-only, so a rule can pin your agent to one site. You choose the read operations it may call, so it can see the overview and top pages for that site and nothing on other sites unless you add them.
Credential isolation
Your Cookie Free Analytics 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.
Intent-based discovery
Agents search Jentic by intent such as 'read site traffic' or 'list top sources', and Jentic returns the matching Cookie Free Analytics operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Cookie Free Analytics read API through Jentic.
What authentication does the Cookie Free Analytics API use?
The Cookie Free Analytics API authenticates with a bearer token in the cfa_live_ format, taken from the account area, per its OpenAPI spec. Through Jentic the token is stored once by your own self-hosted instance and injected when a call runs, so it never appears in the agent's prompt or logs.
Can I read traffic figures for a specific site with the Cookie Free Analytics API?
Yes. List your sites, then call the overview operation with the siteId to read visitors, visits, pageviews, bounce, and average duration, and use the pages and sources operations for top pages and referrers. All figures are aggregates, so no raw visitor rows are returned.
Can I limit what my agent is allowed to do with the Cookie Free Analytics API?
Yes. The API is read-only, and Cookie Free Analytics puts the siteId in the URL path, so a rule can pin your agent to one site and the overview and pages operations you choose, so it cannot read other sites on the account, with every call logged.
What are the rate limits for the Cookie Free Analytics API?
The OpenAPI spec does not specify rate limits. Check the Cookie Free Analytics documentation at https://www.cookiefreeanalytics.com for current limits before polling the live or overview endpoints frequently.
Is there a Cookie Free Analytics MCP server?
You don't need an MCP server to give your agent the Cookie Free Analytics API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent calls the overview and sources operations on demand without loading another server's tool definitions into its context.
How do I summarize a site's traffic with the Cookie Free Analytics API through Jentic?
Search Jentic by intent such as 'read site analytics overview', and Jentic returns the overview operation with its input schema so your agent passes the siteId and reads back the aggregates. To run it on your own infrastructure, install Jentic One from its GitHub repo.
For Agents
Read privacy-friendly, cookie-free site analytics: visitors, visits, pageviews, bounce, and duration, plus top pages, top sources, live activity, funnels, and uptime watch, per site.
Use for: Show the visitor and pageview overview for this site, List the top pages for my site this week, Find the top traffic sources for the site, Check what is happening on the site right now
Not supported: Does not set cookies, collect raw visitor rows, or send events into the analytics store. Use for reading aggregated site analytics only.
The Cookie Free Analytics read API returns the aggregated traffic figures a site owner already sees on the dashboard, without cookies, visitor hashes, or raw per-visitor rows. It lists the sites on an account and, for each site, reports an overview of visitors, visits, pageviews, bounce rate, average duration, and live activity, plus top pages and top sources. Growth-plan sites can read linear same-day funnels, and Starter-plan sites can read uptime watch state and incidents. Every figure is a read-only aggregate scoped to a site by its siteId.
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>