Umami
Umami is an open source, privacy-first web analytics platform that provides website traffic insights without cookies or personal data collection, serving as a simple and fast alternative to Google Analytics. The Umami API provides full programmatic access to analytics data, website management, session tracking, event data, and team collaboration features for both self-hosted and cloud instances.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Umami the way a machine reads it — 95 machine-readable artifacts across 7 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Umami scores 61.2/100 (strong), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Umami
Each block below is one kind of artifact we hold for Umami. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 7
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Umami Authentication API
Login and token verification
Umami Events API
Custom event tracking
Umami Sessions API
Visitor session data
Umami Teams API
Team and access management
Umami Users API
User account management
Umami Website Statistics API
Analytics metrics, pageviews, and statistics
Umami Websites API
Website management and configuration
Scroll within the panel for all 7 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Umami Analytics API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Umami Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Umami Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Umami Finops
FINOPSFeatures 8
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Privacy-First Analytics
Tracks website traffic without cookies or personal data, fully GDPR compliant without consent banners.
Real-Time Data
Live visitor counts and real-time pageview tracking for immediate traffic insights.
Custom Events
Track custom user interactions and conversions with a simple JavaScript API.
Team Collaboration
Share analytics access across teams with role-based access control.
Self-Hosting Support
Deploy on your own infrastructure for complete data ownership and control.
Open Source
MIT-licensed open source software with active community development and full transparency.
Multi-Site Support
Manage and analyze multiple websites from a single Umami instance.
API Access
Full REST API for programmatic access to all analytics data and management functions.
Scroll within the panel for all 8 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Umami Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Umami API Rules
SPECTRALUmami API Rules
SPECTRALJSON Schema 19
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
ActiveVisitors
JSON SCHEMALoginRequest
JSON SCHEMALoginResponse
JSON SCHEMAMetric
JSON SCHEMAOkResponse
JSON SCHEMAPageviewData
JSON SCHEMASessionList
JSON SCHEMASession
JSON SCHEMASessionStats
JSON SCHEMATeamList
JSON SCHEMATeamMember
JSON SCHEMATeamRequest
JSON SCHEMATeam
JSON SCHEMAUserRequest
JSON SCHEMAUser
JSON SCHEMAWebsiteList
JSON SCHEMAWebsiteRequest
JSON SCHEMAWebsite
JSON SCHEMAWebsiteStats
JSON SCHEMAScroll within the panel for all 19 ·
JSON Structure 19
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Umami Active Visitors Structure
JSON STRUCTUREUmami Login Request Structure
JSON STRUCTUREUmami Login Response Structure
JSON STRUCTUREUmami Metric Structure
JSON STRUCTUREUmami Ok Response Structure
JSON STRUCTUREUmami Pageview Data Structure
JSON STRUCTUREUmami Session List Structure
JSON STRUCTUREUmami Session Stats Structure
JSON STRUCTUREUmami Session Structure
JSON STRUCTUREUmami Team List Structure
JSON STRUCTUREUmami Team Member Structure
JSON STRUCTUREUmami Team Request Structure
JSON STRUCTUREUmami Team Structure
JSON STRUCTUREUmami User Request Structure
JSON STRUCTUREUmami User Structure
JSON STRUCTUREUmami Website List Structure
JSON STRUCTUREUmami Website Request Structure
JSON STRUCTUREUmami Website Stats Structure
JSON STRUCTUREUmami Website Structure
JSON STRUCTUREScroll within the panel for all 19 ·
Examples 19
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Umami Login Request Example
EXAMPLEUmami Login Response Example
EXAMPLEUmami Metric Example
EXAMPLEUmami Ok Response Example
EXAMPLEUmami Pageview Data Example
EXAMPLEUmami Session Example
EXAMPLEUmami Session List Example
EXAMPLEUmami Session Stats Example
EXAMPLEUmami Team Example
EXAMPLEUmami Team List Example
EXAMPLEUmami Team Member Example
EXAMPLEUmami Team Request Example
EXAMPLEUmami User Example
EXAMPLEUmami User Request Example
EXAMPLEUmami Website Example
EXAMPLEUmami Website List Example
EXAMPLEUmami Website Stats Example
EXAMPLEScroll within the panel for all 19 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 6
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Website Performance Monitoring
Track pageviews, unique visitors, bounce rates, and session duration for website optimization.
Privacy-Compliant Analytics
Replace Google Analytics with a cookieless solution that requires no consent banners under GDPR.
Marketing Analytics
Analyze traffic sources, referrers, and UTM campaign data to measure marketing effectiveness.
Custom Event Tracking
Track button clicks, form submissions, and custom conversions using the Umami event API.
Developer Dashboards
Build custom analytics dashboards using the REST API to display site metrics in your own apps.
Multi-Tenant Analytics
Provide analytics access to multiple clients or teams with shared infrastructure and access controls.
Integrations 5
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Next.js
First-class integration with Next.js via the @umami/nextjs package for page view tracking.
WordPress
Track WordPress sites by adding the Umami tracking script via plugin or manual installation.
Vercel
Deploy Umami on Vercel with a one-click deployment for managed self-hosting.
Docker
Run Umami in any environment using the official Docker container image.
Cloudflare
Deploy tracking scripts behind Cloudflare for performance and abuse prevention.
Solutions 2
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
Umami Cloud
Hosted Umami instance at cloud.umami.is with managed infrastructure and API key authentication.
Umami Self-Hosted
Run your own Umami instance on any infrastructure with full data ownership and JWT authentication.
Resources
Every other property we hold for Umami — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/umami · machine-readable index on apis.io