PostHog publishes 139 APIs on the network with a composite of 63.7 — strong — and an agent-readiness score of 42.3 (agent-ready). Its agentic-access contract enumerates 1,567 operations, 927 acting, 18 human-in-the-loop.
1,567 operations across 139 APIs — 11.3 per entry. The densest surface profiled this week, four times Grafana’s ratio.
Commercial clarity at 92.1
| Facet | Score |
|---|---|
| Commercial clarity | 92.1 |
| Operational transparency | 68.4 |
| Discoverability | 59.3 |
| Contract quality | 58.3 |
| Developer ergonomics | 54.3 |
| Governance | 41.7 |
That 92.1 is the highest single facet score of any provider in this week’s sweep, matching GitHub’s operational transparency.
PostHog tells you what everything costs, publicly, per event, with the free tier stated plainly and the pricing page readable without a form. That is a deliberate position — the company has been unusually loud about publishing its internal handbook, its pricing philosophy, and its strategy in public — and the score simply reflects it.
It is worth naming what that buys, because it is not goodwill. An engineer evaluating an analytics platform can model the annual cost from the docs in ten minutes. Nobody has to book a call to find out whether the thing is affordable at their volume, which means nobody drops out of the funnel at the point where a competitor requires a conversation.
Open source, and the facets show it unevenly
PostHog is open source — event tracking, session recording, feature flags, A/B testing, and surveys, self-hostable or cloud, with the customer keeping control of their product data.
Grafana, profiled earlier this week, converts open source into governance 69.8 and discoverability 85.2, because its specs live with its code under a public review process. PostHog converts it into commercial clarity and lands at governance 41.7 and discoverability 59.3.
Same licensing posture, very different results. The difference is that Grafana’s HTTP API is the product’s own interface, described because it had to work, while PostHog’s catalog surface is decomposed from a large generated schema — Actions, Activity Log, Activity Logs, Advanced Activity Logs, Alerts, Annotations, Approval Policies, Batch Exports, CDP, Change Requests, Code, Code Invites, Cohorts, Comments, Conversations, Core, Customer Analytics, Customer Journeys, Dashboards, Dashboard Templates, and 119 more.
Note Activity Log, Activity Logs, and Advanced Activity Logs as three separate entries. Open source gets you access to the definitions; it does not get you an editor.
927 acting operations, 18 pauses
Nine hundred and twenty-seven operations mutate state, and 18 carry a human-in-the-loop marker.
For most of this surface that ratio is defensible — deleting a dashboard or editing a cohort is annoying and recoverable. Two areas are not. Feature flags change what real users see in production, instantly, at whatever percentage rollout the call specifies. Batch exports move customer event data to external destinations, which is a data-governance action with a compliance shape.
Those are the operations where an agent should stop and ask, and they are competing for 18 markers with 925 others.
Takeaway
139 APIs, 1,567 operations, and the most transparent pricing of any provider in the sweep. PostHog spends its openness on commercial clarity rather than on governance, ships a dense generated surface with three flavours of activity log, and leaves feature-flag rollout in the same unflagged bucket as editing a dashboard.
See the full profile at apis.io/providers/posthog/.