Install Jentic One Beta

Connect the Microsoft Clarity Data Export API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Microsoft Clarity Data Export 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%2Fmicrosoft.com%2Fclarity" | sh

Step 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%2Fmicrosoft.com%2Fclarity" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with Microsoft Clarity Data Export API.

Fetch a Clarity project's live insights for the last one, two, or three days

Break the insights down by a first dimension such as browser or device

Add a second and third dimension to segment the same insights further

Read session and engagement metrics that Clarity has already collected

Use Cases

Patterns agents use Microsoft Clarity Data Export API for, with concrete tasks.

GET STARTED

Start building with Microsoft Clarity Data Export API

Explore with Jentic One

View OpenAPI Document

★ Agent Analytics Digest

An AI assistant can pull a website's recent Clarity numbers and summarize them for a stakeholder without anyone opening the dashboard. The agent fetches the live insights for the last few days, reads back the metrics, and writes a short digest, so a daily traffic recap is produced on demand and grounded in the project's own data.

Fetch the last day of Clarity insights and summarize the key traffic and engagement metrics

Dimension Breakdown on Request

A support or marketing agent can answer 'how does traffic split by device' by segmenting Clarity data on the fly. It fetches the insights with the requested dimensions applied, reads back the breakdown, and presents it, so a question about browser or country splits is answered without a human building a dashboard view.

Fetch Clarity insights broken down by the requested dimensions and return the segmented numbers

Scheduled Metrics Pull

A reporting job can export the last few days of Clarity insights on a schedule and store them for trend tracking. Each run fetches the live insights, reads the metrics, and appends them to a warehouse, so a rolling history is built from the project's own data without manual export.

Fetch the last three days of Clarity insights and append the metrics to a warehouse table

Key Endpoints

1 endpoints — the microsoft clarity data export api returns the traffic and behavior insights a clarity project has recorded for its website.

METHOD

PATH

DESCRIPTION

GET

/export-data/api/v1/project-live-insights

Fetch a project's live traffic and behavior insights

GET

/export-data/api/v1/project-live-insights

Fetch a project's live traffic and behavior insights

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Microsoft Clarity Data Export API by hand means handling its bearer auth and matching the numOfDays and dimension parameters to the response shape. Through Jentic you install once, import it from the API Directory, store the token once, and your agent calls the live insights operation.

Permission scoping

Clarity exposes a single read-only export operation, so a rule can allow just that operation and nothing else. You decide which operations are in scope, and every call the agent makes is logged.

Credential isolation

Your Clarity bearer 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 'export my Clarity project insights', and Jentic returns the live insights operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using Microsoft Clarity Data Export API through Jentic.

What authentication does the Microsoft Clarity Data Export API use?

The Microsoft Clarity Data Export API authenticates with a bearer token in the Authorization header, per its OpenAPI spec. When you call it through Jentic, that token is held by your own self-hosted instance and injected at execution time, so it never appears in the agent's prompt or logs.

Can I break Clarity insights down by browser or device?

Yes. The live insights endpoint takes up to three optional dimension parameters, so you can segment the same numbers by browser, device, country, and similar values. You also choose one, two, or three days of data with the numOfDays parameter.

What are the rate limits for the Microsoft Clarity Data Export API?

The OpenAPI spec for the Microsoft Clarity Data Export API does not define rate limits. Clarity documents a low daily request allowance for the export API, so check its current documentation before scheduling frequent pulls.

Is there a Microsoft Clarity API MCP server?

You don't need an MCP server to give your agent the Microsoft Clarity Data Export API. Jentic connects it directly from the API Directory: import it, store the bearer token once, and your agent calls the live insights operation without another server's tool definitions loaded into its context.

Can I limit what my agent does with the Microsoft Clarity API?

Yes. The API is a single read-only export operation, so a rule can allow just that operation and nothing else, and every call the agent makes is logged. You decide which operations are in scope, so the agent reads insights without touching anything else.

How do I export Clarity insights through Jentic?

Search Jentic with an intent like 'export my Clarity project insights', and it returns the live insights operation with its input schema so the agent submits the day window and dimensions and reads back the metrics. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Microsoft Azure Microsoft Clarity Data Export API

Name: Microsoft Clarity Data Export API
Brand: Microsoft Clarity
Availability: InStock

Agent-ready OpenAPI document · curated by JenticAnalyticsWeb Analyticsbearer1 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Fetch a Microsoft Clarity project's live traffic and behavior insights for the last one to three days, optionally broken down by dimensions like browser, device, or country.

Use for: Get my Clarity project's traffic for the last day, Show engagement metrics broken down by browser, Export the last three days of Clarity insights, Segment Clarity data by device and country

Not supported: Exports recorded traffic and behavior insights only. Does not change project settings, manage users, or return raw session recordings.

The Microsoft Clarity Data Export API returns the traffic and behavior insights a Clarity project has recorded for its website. A single endpoint fetches the project's live insights for the last one to three days and can break the numbers down by up to three dimensions, such as browser, device, or country. It is a read-only export of the metrics Clarity already collects, so it reports on session and engagement data rather than changing project settings.

Jentic One on Github View OpenAPI Document