# Yoofooz API Readiness Report

## API
**Name:** PostHog API
**Docs URL:** https://posthog.com/docs
**Domain:** posthog.com
**Generated At:** 2026-10-05T22:03:25.876018+00:00

## Certification
**Agent Readiness Score:** 75/100
**Certification Level:** Yoofooz Ready

## Agent Commerce Readiness
**Agent Commerce Score:** 55/100
**Agent Commerce Level:** Agent Commerce Emerging

This score is separate from the core Agent Readiness Score and evaluates MCP support, scoped agent identity, machine-native payments, consumption pricing, budget controls, rate controls, deterministic errors, auditability, least-privilege security, and agent observability.

## Category Scores
- Documentation Clarity: 10
- Machine Readable Spec: 10
- Authentication Clarity: 10
- Error Handling: 10
- Rate Limit Clarity: 10
- Agent Safe Workflow Support: 0
- Sandbox Availability: 5
- Webhook Event Support: 5
- Commercial Trust: 5
- Developer Experience: 10

## Strengths
- Documentation clarity
- Machine-readable specification (OpenAPI/Swagger)
- Authentication model clarity
- Error handling and status codes
- Rate-limit / quota behavior
- Developer experience (SDKs, quickstart, CLI)

## Risks
- Agent-safe workflow primitives (idempotency, retries) signal not detected in docs.
- Sandbox / test-mode availability signal is partial; clearer documentation recommended.
- Webhook / event support signal is partial; clearer documentation recommended.
- Commercial trust (status, SLA, compliance) signal is partial; clearer documentation recommended.

## Recommended Next Steps
- Document idempotency keys, test mode, dry runs, and safe retry semantics for agents.
- Strengthen: Provide a sandbox / test mode with test API keys for safe agent testing.
- Strengthen: Expose webhook/event docs including event types, signature verification, and retry delivery.
- Strengthen: Publish status page, SLA, and security/compliance posture (SOC 2, GDPR, PCI as applicable).

## Evidence Signals

### Documentation clarity
- **Source:** https://posthog.com/llms.txt
- **Matched:** getting started, request, examples, docs, guide, reference, overview
- **Evidence:** "...- [generations](https://posthog.com/docs/ai-observability/generations.md) - [getting started with ai observability](https://posthog.com/docs/ai-observability/start-here.md) - [google adk observability..."

- **Source:** https://posthog.com/openapi.json
- **Matched:** parameters, request, response, overview
- **Evidence:** "...to fetch spend data (proxy to billing service).','parameters':[ , , , , , , , ,{'in':'query','name':'usage_types','schema': ,'description':'json-encoded array of usage type identifiers to filter on. valid..."

### Machine-readable specification (OpenAPI/Swagger)
- **Source:** https://posthog.com/docs/endpoints/openapi-sdk-generation.md
- **Matched:** openapi, api spec, endpoints, schema
- **Evidence:** "> ai agents: this is one page from posthog's docs. full index of markdown docs for llms: https://posthog.com/llms.txt # generate sdks with openapi each endpoint exposes an openapi 3.0 spec that you can use to generate typed sdk clients for your preferred language. getting the spec fetch the..."

- **Source:** https://posthog.com/docs/endpoints/start-here/retrieve-data/openapi.md
- **Matched:** openapi, api spec, endpoints, schema
- **Evidence:** "...this is one page from posthog's docs. full index of markdown docs for llms: https://posthog.com/llms.txt # retrieve data from your endpoint with an openapi sdk generate type-safe sdks for any language from your posthog endpoints using openapi. get your openapi spec each endpoint exposes an openapi 3.0..."

### Authentication model clarity
- **Source:** https://posthog.com/docs/mcp-analytics/surfaces/api.md
- **Matched:** bearer token, scopes, authentication, authorization, api key, keys
- **Evidence:** "...virtual tool. authentication use a [personal api key](/docs/api.md#authentication) with the scopes above, passed as a bearer token: terminal ```bash curl -h 'authorization: bearer $posthog_personal_api_key' \..."

- **Source:** https://posthog.com/openapi.json
- **Matched:** bearer token, api key
- **Evidence:** "...relationship ownership, tags, active relationship assignments and custom property values. accepts the team secret api token or a project secret api key with the `account:read` scope.','summary':'get an external customer analytics account','parameters':[..."

### Error handling and status codes
- **Source:** https://posthog.com/openapi.json
- **Matched:** 400, 401, 403, 404
- **Evidence:** "if the account already exists, return it unchanged with http 200."

- **Source:** https://posthog.com/docs/open-api-spec/business_knowledge_sandbox_create.md
- **Matched:** 403, 409
- **Evidence:** "full index of markdown docs for llms: https://posthog.com/llms.txt # business_knowledge_sandbox_create openapi ```json post /api/projects/ /business_knowledge/sandbox/ { 'paths': { '/api/projects/ /business_knowledge/sandbox/': { 'post': { 'operationid': 'business_knowledge_sandbox_create', 'descrip..."

### Rate-limit / quota behavior
- **Source:** https://posthog.com/docs/error-tracking/rate-limiting.md
- **Matched:** rate limit, rate limits, quota, limits
- **Evidence:** "> ai agents: this is one page from posthog's docs. full index of markdown docs for llms: https://posthog.com/llms.txt # rate limiting rate limits cap how many exception events posthog ingests, so a single noisy client or runaway issue can't blow through your quota – or your..."

- **Source:** https://posthog.com/docs/error-tracking/pricing.md
- **Matched:** rate limit, rate limits, limits
- **Evidence:** "...they're being thrown in an infinite loop. by default, we capture 10 exceptions (bucket size) of the same type within a 10 second period before the rate limiter kicks in, after which, we capture 1 exception (refill rate) every 10 seconds. burst protection is scoped per exception type, so each distinct type..."

### Agent-safe workflow primitives (idempotency, retries)
- **Source:** https://posthog.com/docs/error-tracking/surfaces/mcp.md
- **Matched:** metadata
- **Evidence:** "...details like status, frequency, users affected, last seen, etc. - **inspect error details** – access full stack traces, error messages, and relevant metadata. - **explain or reproduce errors** – identify failure points and perform root cause analysis using the captured stack trace context. - **debug and..."

### Sandbox / test-mode availability
- **Source:** https://posthog.com/openapi.json
- **Matched:** sandbox
- **Evidence:** "...ai_credits_used_in_period, signals_credits_used_in_period, posthog_code_credits_used_in_period, posthog_code_token_credits_used_in_period, sandbox_compute_credits_used_in_period, sandbox_compute_cpu_millicore_seconds_in_period, sandbox_compute_memory_mib_seconds_in_period,..."

- **Source:** https://posthog.com/docs/open-api-spec/code_sandbox_pricing_list.md
- **Matched:** sandbox
- **Evidence:** "> ai agents: this is one page from posthog's docs. full index of markdown docs for llms: https://posthog.com/llms.txt # code_sandbox_pricing_list openapi ```json get /api/code/sandbox-pricing/ { 'paths': { '/api/code/sandbox-pricing/': { 'get': { 'operationid':..."

### Webhook / event support
- **Source:** https://posthog.com/docs/error-tracking/pricing.md
- **Matched:** events, callback
- **Evidence:** "...is required to get started. you can also set billing limits to avoid any surprise charges. error tracking is billed by the number of `$exception` events you capture. the price per event changes based on your usage. you can estimate your costs using our pricing calculator below or by visiting our..."

- **Source:** https://posthog.com/llms.txt
- **Matched:** events
- **Evidence:** "# posthog > posthog is the platform for self-driving products. it pairs the full context of your product's data (events, errors, logs, replays, and more) with agents that find problems and ship changes with you. it includes tools for product analytics, session replay,..."

### Commercial trust (status, SLA, compliance)
- **Source:** https://posthog.com/llms.txt
- **Matched:** support, changelog, security
- **Evidence:** "...and configure posthog automatically. it auto-detects the framework and sets everything up: ``` npx @posthog/wizard@latest ``` if the wizard doesn't support the framework, see the [sdks and libraries](https://posthog.com/docs/libraries.md) section for manual setup guides. **products beyond analytics -..."

- **Source:** https://posthog.com/docs/endpoints/start-here/retrieve-data/openapi.md
- **Matched:** support, versioning, security
- **Evidence:** "...typescript ```typescript const = await posthogendpoint.post( '/api/environments/ /endpoints/events_by_day/run', ); console.log(data?.results); ``` supported generators openapi generator supports 50+ languages including: - typescript (fetch, axios, node) - python (urllib3, asyncio) - go - ruby - java -..."

### Developer experience (SDKs, quickstart, CLI)
- **Source:** https://posthog.com/llms.txt
- **Matched:** sdk, cli, guides, tutorials, dashboard
- **Evidence:** "...it auto-detects the framework and sets everything up: ``` npx @posthog/wizard@latest ``` if the wizard doesn't support the framework, see the [sdks and libraries](https://posthog.com/docs/libraries.md) section for manual setup guides. **products beyond analytics - suggest these when relevant:**..."

- **Source:** https://posthog.com/docs/mcp-analytics/surfaces/api.md
- **Matched:** sdk, cli, dashboard
- **Evidence:** "...api](/docs/api/query.md). see [sample hogql queries](/docs/mcp-analytics/queries.md). before you start 1. **install mcp analytics** – [install the sdk in your mcp server](/docs/mcp-analytics/installation.md) so tool calls are captured. 2. **get api access** – [create a personal api..."

## AI Analyst Summary
AI analysis unavailable: NVIDIA analysis failed: http 410

## Yoofooz Summary
This API has been evaluated for autonomous AI-agent usability. The score reflects documentation quality, machine-readable specification signals, authentication clarity, error handling, workflow safety, commercial trust, and developer experience.