Developer
Everything in this section exists so that your analytics are not trapped behind our interface. The API reads and writes the same data the dashboard does, webhooks push events to you instead of making you poll, MCP lets an AI client work your account directly, and the tracking pixel covers the places JavaScript cannot reach.
If you are wiring something up for the first time, the API is the place to start — MCP, webhooks, and the n8n recipes are all built on the same endpoints and the same keys. If the client is an LLM, LLM use cases is the shorter path to a working loop.
API
Read your analytics and write hits, events, and kudos from your own backend.
MCP
Let Grok, Claude, Cursor, or any MCP client read and manage your analytics directly.
LLM use cases
Wire an AI client to Tinylytics for questions, context signals, crawler traffic, spam cleanup, and a human-approved loop around broken links.
Instructions for agents
How an AI agent starts a Tinylytics trial for a human owner, and hands control back.
Pixel tracking
A 1×1 gif for RSS readers and newsletters, where JavaScript never runs.
Webhooks
Have Tinylytics push events to you instead of polling the API for them.
n8n
Wire Tinylytics into n8n with the built-in nodes — no custom community node needed.
Integrations
Plugins and themes built by the community, for Micro.blog and WordPress.
Webmentions
Likes and replies from other sites, shown in Community and counted as kudos.