Skip to content
measure
Start free trial

Analytics your agent can read.

A native MCP server and a JSON API built for LLMs. Your agent can check traffic, read a summary, see which AI agents visited, track events and even set up a site, without a human opening a dashboard.

MCP https://lets.measure.events/mcp

Get an API key

Connect in a minute.

Add Measure to your MCP client’s config with an API key from your account. It speaks Streamable HTTP; the server is called measure-events. Then ask it anything about your sites.

  1. 1Create an API key in Measure.
  2. 2Paste the config into your client.
  3. 3Ask: “How did my site do this week?”
MCP client config
{
  "mcpServers": {
    "measure": {
      "url": "https://lets.measure.events/mcp",
      "headers": {
        "Authorization": "Bearer mk_…"
      }
    }
  }
}

Thirteen tools.

Every tool returns structured JSON. Agent traffic is always broken out from human traffic.

list_sites
Your sites with their site key, tracking script and last-7-day pageviews.
get_site_summary
A plain-language summary of the last 7 days, with week-over-week change and highlights.
get_site_analytics
Pageviews, human visitors, AI agent and bot requests, top pages and referrers for a period.
get_agents
Every AI agent that fetched the site: operator, purpose (assistant, training, search), requests and top page.
get_breakdown
Top values of one dimension: path, referrer, channel, country, device, browser, UTM tags or agent.
get_insights
Anomalies and trends: page spikes, new referrers, new AI agents, traffic drops.
get_live
Visitors on the site now and the latest requests.
get_agent_report
Everything in one call: 7- and 30-day traffic, pages, referrers, agents, insights, check-ins and recommended actions.
get_llms_txt
The last 30 days as a short Markdown document, sized for a context window.
track_event
Record a pageview: an agent’s own visit, or a request your server forwards.
create_site
Add a site and get its site key and tracking script back, ready to install.
log_checkin
Note something the agent did, like publishing a post or deploying, so it shows beside the traffic it caused.
signup
Create a Measure account without a human. No API key needed.

Or call the API.

The same data over HTTP. Send your API key as a Bearer token: Authorization: Bearer mk_…

Base URL

https://lets.measure.events/api/v1

Discovery

GET /sites
Your tracked sites
GET /sites/:id/summary
Plain-language summary
GET /sites/:id/agent-report
Everything an agent needs, in one call
GET /sites/:id/agents?period=7d
AI agents, operators and purposes
GET /sites/:id/pages
Top pages
GET /sites/:id/llms-txt
The last 30 days as Markdown
POST /events
Track custom events
POST /agents/signup
Create an account (no key needed)

Agents can sign up themselves.

An agent can create a Measure account and a site with your email, install the script, and start reading numbers. You get an email to claim the account and add a card before the 14-day trial ends.

POST https://lets.measure.events/api/v1/agents/signup
{
  "billing_contact_email": "you@example.com",
  "site": { "domain": "example.com" },
  "agent": { "name": "Claude" }
}

Returns api_key, tracking_script and claim_url. Agents can also report their own visits with POST https://lets.measure.events/api/collect and a site_id, path and agent.

  1. The agent signs up

    One request creates the account, the site and an API key.

  2. It installs the script

    The response includes the snippet; data starts flowing.

  3. You claim it

    An email link lets you take over and add a card, or attach it to an account you already have.

Give your agent the numbers.

$29 a month for 40 sites, 14-day free trial. MCP server included.

Start your 14-day trial See pricing