Apstal

AI-first website analytics and visitor tracking platform that replaces traditional dashboards with a natural-language chatbot interface, offering conversational analytics, cookieless tracking, session replays, heatmaps, funnels, error tracking, Core Web Vitals and AI-agent traffic detection. Apstal is agent-native by design: its primary programmatic surface is a hosted MCP server at https://apstal.com/api/mcp (JSON-RPC 2.0 over Streamable HTTP, protocol 2025-06-18) whose tools/list is answerable anonymously, backed by a documented REST ingestion and stats API, a WebSocket real-time stream, an SSE natural-language query endpoint, an A2A agent card, two provider-authored Agent Skills, an llms.txt, OAuth 2.0 authorization-server and protected-resource metadata, and an MCP server card. The company is based in Poland and publishes a GDPR Data Processing Agreement.

Apstal publishes 2 APIs on the APIs.io network. Tagged areas include analytics, web-analytics, privacy, session-replay, and heatmaps.

The Apstal catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Apstal’s developer surface includes authentication, documentation, API reference, getting-started guide, quickstart, support, engineering blog, and 26 more developer resources.

🌐 Visit website 📡 Source on GitHub

58.2/100 strong ▲ 52.3 Agent 44/100 agent ready Full breakdown ↓
scored 2026-08-17 · rubric v0.11.0

2 APIs 1 MCP Servers

analyticsweb-analyticsprivacysession-replayheatmapsmcpagent-nativecookielessllms-txtbigquerygdpra2aagent-skillsbot-detectioncore-web-vitals

Kin Score

Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0

Composite quality — 58.2/100 · strong

Contract Quality 12.9 / 25

Developer Ergonomics 13.0 / 20

Commercial Clarity 16.8 / 20

Operational Transparency 6.8 / 13

Governance 1.5 / 12

Discoverability 7.0 / 10

Agent readiness — 44/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 8 / 8

Dry-Run / Simulate Mode 0 / 4

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/apstal: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 2

Individual APIs this provider publishes, each with its own machine-readable definition.

Apstal MCP Server

Hosted MCP server exposing Apstal analytics via JSON-RPC 2.0 over Streamable HTTP. Public tools (login, register, server_info) and authenticated tools (execute_sql, get_analytic...

Apstal Analytics API

Documented REST surface for programmatic access to Apstal analytics: POST /api/v1/m for batched event ingestion (max 100 events per request), POST /api/v1/stream for rrweb sessi...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Rate Limits 1

Documented rate limits and quota policies.

Scopes 1

OAuth scopes governing access to this provider's APIs.

Apstal Scopes

3 scopes · authorizationCode/refreshToken

3 scopes

SCOPES

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

GettingStarted

Quickstart

SignUp

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

WellKnown

WellKnown

AgentSkill

AgentSkill

LLMsTxt

LLMsTxt

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

ErrorCatalog

Conventions

Lifecycle

Components

DataModel

Conformance

Build 3

SDKs, sample code, and the tooling you integrate with

Packages

Packages

SDKs

SDKs

GitHubOrganization

GitHubOrganization

Access & Security 4

Authentication, authorization, and security posture

DomainSecurity

Authentication

OAuthScopes

Compliance

Operate 4

Status, limits, changes, and where to get help

StatusPage

RateLimits

Support

HelpCenter

Commercial 4

Pricing, plans, and the legal terms of use

Plans

Pricing

TermsOfService

PrivacyPolicy

Company 1

The organization behind the API

Blog

Blog

Other 2

Properties that don't map to a standard resource type

AgentCard

AgentCard

EventSurface

EventSurface

Source (apis.yml)

name: Apstal
description: 'AI-first website analytics and visitor tracking platform that replaces traditional dashboards with a natural-language
  chatbot interface, offering conversational analytics, cookieless tracking, session replays, heatmaps, funnels, error tracking,
  Core Web Vitals and AI-agent traffic detection. Apstal is agent-native by design: its primary programmatic surface is a
  hosted MCP server at https://apstal.com/api/mcp (JSON-RPC 2.0 over Streamable HTTP, protocol 2025-06-18) whose tools/list
  is answerable anonymously, backed by a documented REST ingestion and stats API, a WebSocket real-time stream, an SSE natural-language
  query endpoint, an A2A agent card, two provider-authored Agent Skills, an llms.txt, OAuth 2.0 authorization-server and protected-resource
  metadata, and an MCP server card. The company is based in Poland and publishes a GDPR Data Processing Agreement.'
url: https://apstal.apievangelist.com/apis.yml
created: '2026-07-22'
modified: '2026-08-13'
image: https://apstal.com/logos/apstal-mark.svg
specificationVersion: '0.21'
tags:
- analytics
- web-analytics
- privacy
- session-replay
- heatmaps
- mcp
- agent-native
- cookieless
- llms-txt
- bigquery
- gdpr
- a2a
- agent-skills
- bot-detection
- core-web-vitals
apis:
- name: Apstal MCP Server
  description: Hosted MCP server exposing Apstal analytics via JSON-RPC 2.0 over Streamable HTTP. Public tools (login, register,
    server_info) and authenticated tools (execute_sql, get_analytics, list_projects, register_domain, get_schema, generate_api_key)
    via Bearer token auth.
  humanURL: https://apstal.com/docs/mcp
  baseURL: https://apstal.com/api/mcp
  tags:
  - analytics
  - web-analytics
  - privacy
  - session-replay
  - heatmaps
  - mcp
  - agent-native
  - cookieless
  - llms-txt
  - bigquery
  - gdpr
  properties:
  - type: MCPServer
    url: mcp/apstal-mcp.yml
  - type: ToolCrosswalk
    url: mcp/apstal-tool-crosswalk.yml
  - type: Documentation
    url: https://apstal.com/docs/mcp
  - type: LLMsTxt
    url: llms/apstal-llms.txt
- name: Apstal Analytics API
  description: 'Documented REST surface for programmatic access to Apstal analytics: POST /api/v1/m for batched event ingestion
    (max 100 events per request), POST /api/v1/stream for rrweb session-replay chunk upload, GET /api/analytics/quick for
    aggregated dashboard metrics, and POST /api/ai/semantic for natural-language analytics queries answered as a text/event-stream.
    A WebSocket service at wss://ws.apstal.com carries tracker, dashboard and replay-viewer connections. Authentication is
    a Bearer API key (apstal_ prefix) or a Supabase session JWT. No OpenAPI is published.'
  humanURL: https://apstal.com/docs/api
  baseURL: https://apstal.com/api
  tags:
  - analytics
  - web-analytics
  - session-replay
  - core-web-vitals
  - websocket
  - server-sent-events
  properties:
  - type: APIReference
    url: https://apstal.com/docs/api
  - type: Documentation
    url: https://apstal.com/docs
maintainers:
- FN: Apstal
  url: https://apstal.com
generated:
  by: apis.io/add
  model: claude-opus-4-8
  confidence: 95
  at: '2026-07-22T20:28:11.444Z'
common:
- type: DomainSecurity
  url: security/apstal-domain-security.yml
- type: WellKnown
  url: well-known/apstal-well-known.yml
- type: AgentCard
  url: a2a/apstal-a2a.yml
- type: AgentSkill
  url: skills/_index.yml
- type: LLMsTxt
  url: llms/apstal-llms.txt
- type: Authentication
  url: authentication/apstal-authentication.yml
- type: OAuthScopes
  url: scopes/apstal-scopes.yml
- type: ErrorCatalog
  url: errors/apstal-problem-types.yml
- type: Conventions
  url: conventions/apstal-conventions.yml
- type: Lifecycle
  url: lifecycle/apstal-lifecycle.yml
- type: StatusPage
  url: https://status.apstal.com
- type: Plans
  url: plans/apstal-plans-pricing.yml
- type: RateLimits
  url: rate-limits/apstal-rate-limits.yml
- type: Packages
  url: packages/apstal-packages.yml
- type: SDKs
  url: packages/apstal-packages.yml
- type: Components
  url: components/apstal-components.yml
- type: DataModel
  url: data-model/apstal-data-model.yml
- type: Conformance
  url: conformance/apstal-conformance.yml
- type: Compliance
  url: https://apstal.com/dpa
- type: EventSurface
  url: asyncapi/apstal-realtime-events.yml
- type: DeveloperPortal
  url: https://apstal.com/docs
- type: Documentation
  url: https://apstal.com/docs
- type: APIReference
  url: https://apstal.com/docs/api
- type: GettingStarted
  url: https://apstal.com/docs/getting-started
- type: Quickstart
  url: https://apstal.com/docs/quickstart
- type: Support
  url: https://apstal.com/contact
- type: HelpCenter
  url: https://apstal.com/faq
- type: Blog
  url: https://apstal.com/blog
- type: GitHubOrganization
  url: https://github.com/apstal
- type: Pricing
  url: https://apstal.com/pricing
- type: SignUp
  url: https://apstal.com/login
- type: TermsOfService
  url: https://apstal.com/terms
- type: PrivacyPolicy
  url: https://apstal.com/privacy
x-enrichment:
  date: '2026-08-13'
  status: enriched
  artifacts_added: 27
  pass: local-v1