PostHog vs Amplitude for AI agents
Amplitude is more ready for AI agents than PostHog: 98 vs 88 out of 100. Amplitude is ahead on semantic HTML, named buttons and links and image alt text. PostHog is ahead on no card to start.
What an agent finds
| PostHog | Amplitude | |
|---|---|---|
| Score | 88/100 | 98/100 |
| Blocks AI agents | No | No |
| robots.txt disallows | No AI bots | Bytespider |
| llms.txt | At the root | At the root |
| Remote MCP server | mcp.posthog.com/mcp | mcp.amplitude.com/mcp |
| Docs MCP server | none found | amplitude.com/docs/api/mcp |
| OpenAPI spec | posthog.com/openapi.json | amplitude.com/openapi.json |
| Developer docs | posthog.com/docs | amplitude.com/docs/amplitude-ai/amplitude-mcp?siteLocation=homepage_setup_section |
| Public pricing | posthog.com/pricing | amplitude.com/pricing?siteLocation=nav |
| Self-serve sign-up | Yes, opens for agents | Yes, opens for agents |
Check by check
60 core points every site needs, plus 40 split between letting an agent sign a team up and connecting through the API. Sign-up and API checks count half each.
| Check | Points | PostHog | Amplitude |
|---|---|---|---|
| Core | 48 | 60 | |
| Agents get the real page, not a bot wall | 12 | ✓ | ✓ |
| robots.txt lets user-triggered agents in | 6 | ✓ | ✓ |
| Answer-engine crawlers are allowed | 4 | ✓ | ✓ |
| Content is in the raw HTML | 6 | ✓ | ✓ |
| Semantic HTML (main, nav, header) | 4 | · | ✓ |
| Icon buttons and links have names | 3 | · | ✓ |
| Form fields have labels | 3 | ✓ | ✓ |
| Images have alt text | 3 | · | ✓ |
| The page has an H1 | 2 | ✓ | ✓ |
| Structured data (JSON-LD) | 5 | ✓ | ✓ |
| Meta description and Open Graph tags | 3 | ✓ | ✓ |
| sitemap.xml | 3 | ✓ | ✓ |
| llms.txt | 4 | ✓ | ✓ |
| Dates show the content is fresh | 2 | · | ✓ |
| Sign-up | 20 | 18 | |
| Public pricing page | 5 | ✓ | ✓ |
| A self-serve sign-up link | 4 | ✓ | ✓ |
| Sign-up page opens for agents | 3 | ✓ | ✓ |
| A free plan or trial | 3 | ✓ | ✓ |
| No card needed to start | 2 | ✓ | · |
| SoftwareApplication data | 3 | ✓ | ✓ |
| API | 20 | 20 | |
| OpenAPI spec | 3.5 | ✓ | ✓ |
| Remote MCP server | 4 | ✓ | ✓ |
| Docs as markdown | 2.5 | ✓ | ✓ |
| Self-serve API keys | 3 | ✓ | ✓ |
| OAuth client self-registration | 2.5 | ✓ | ✓ |
| OAuth discovery metadata | 1.5 | ✓ | ✓ |
| SDKs and a CLI | 1.5 | ✓ | ✓ |
| Free tier or test keys | 1.5 | ✓ | ✓ |
Automated, read-only scan of each homepage, robots.txt, llms.txt, docs, OpenAPI paths and MCP endpoints on 3 Nov 2026. How scoring works.
Check them again today
Sites change. Run the live scan for the current result, or check your own site.
Questions
Is PostHog or Amplitude better for AI agents?
Amplitude is more ready for AI agents than PostHog: 98 vs 88 out of 100. Amplitude is ahead on semantic HTML, named buttons and links and image alt text. PostHog is ahead on no card to start. Scores are from our scan on 3 Nov 2026.
Does PostHog have an MCP server?
Yes. Our scan reached a remote MCP server at https://mcp.posthog.com/mcp on 3 Nov 2026.
Does Amplitude have an MCP server?
Yes. Our scan reached a remote MCP server at https://mcp.amplitude.com/mcp on 3 Nov 2026.
Does PostHog block AI agents?
No. PostHog served its homepage to an AI user-agent and its robots.txt doesn't disallow any of the AI crawlers we check.
Does Amplitude block AI agents?
Not outright: its homepage loads for an AI user-agent, but its robots.txt disallows Bytespider.