Is Pendo agent-ready?

Pendo scores Band D on The Headless Index. Its JAIRF rating is not available because no machine-readable spec was scored. Its strongest area for agent use is API-first design intent; its weakest is MCP and agent posture.

Does Pendo publish an OpenAPI spec?

No published OpenAPI specification was found when Pendo was scored. That caps its JAIRF dimensions and forces agents to rely on documentation or reverse engineering to operate it.

What is Pendo's Headless Index score?

Pendo scores 37/100 on the Headless Index thesis-fit rubric and sits in Band D in the Analytics & Events category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.

03 / Scorecard / Analytics & Events

Pendo

Headless Index

37/100

JAIRF

N/A

Verified

AUG 20, 2026

Methodology v1 · JAIRF v1.0.0

Pendo earns Band D in the Analytics & Events category of The Headless Index, with a thesis-fit score of 37/100. Its strongest dimension is API-first design intent (11/20); its weakest scored dimension is MCP and agent posture (4/20). No public OpenAPI specification was found when Pendo was scored, which limits how far an agent can go without human integration work.

Editorial verdict

Pendo remains a dashboard-first product with a limited programmatic surface. The Headless Index thesis-fit score of 37/100 sits in the lower band of the index, and JAIRF is recorded as N/A for this vendor because no public OpenAPI specification was reachable for the open-source scorer. In practice, vendors at this tier ship enough API to be useful but not enough to be operated end to end by agents without a human in the loop, and the rest of this verdict explains where Pendo lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. Pendo has an API, not an API product. The Engage surface answers at app.pendo.io/api/v1 behind an x-pendo-integration-key header, ingestion at app.pendo.io/data/track, and the Aggregation endpoint is a pipeline language expressed as JSON. An agent cannot drive this product end to end today: the headless surface covers basic CRUD but tapers out before reaching the workflows that matter most. On headless operability: Metadata writes, guide state changes, page and feature definitions and reporting all reach the API. Authoring does not. Guides are built in the Designer browser extension, page and feature tagging is a point-and-click exercise against a live app, and the Resource Center needs its own escape hatch (github.com/pendo-io/resource-center-integration-kit). No CLI, no Terraform provider, no config-as-code path.^[1] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: Nothing official. The pendo-io org publishes Go infrastructure libraries and a mobile SDK but no MCP server, and the registry search returned nothing usable. GitHub has only hobby forks with zero stars (AsherJN/pendo-mcp, Band-Aid/pendo-ontology-mcp). A product analytics tool that agents cannot query is a product analytics tool that agents will route around. Pendo has published no agent documentation either.^[2] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. Delivery runs one way. Pendo collects behaviour and hands it back only when asked, through Aggregation queries (POST app.pendo.io/api/v1/aggregation, which answers 403 unauthenticated) or scheduled warehouse exports. The Engage documentation names no outbound event types, no signature header to verify a payload, and no retry or replay contract. Agents must poll and diff, which is expensive and lossy. Net assessment: Pendo is not a strong target for agent-driven workflows today. The weakest link is MCP posture^[3], and the broader surface gives agents too little to operate against. Pick it only when the rest of your stack already mandates it. Use only when locked in.

Verdict by Headless Index pipeline (auto)

// AI-drafted from the evidence layer. Editorial review pending.

Scores

Scorecard detail

Headless Index · 5 sub-criteria

API-first design intent11/20

scored

Pendo has an API, not an API product. The Engage surface answers at app.pendo.io/api/v1 behind an x-pendo-integration-key header, ingestion at app.pendo.io/data/track, and the Aggregation endpoint is a pipeline language expressed as JSON. Official SDKs are client-side only (github.com/pendo-io/pendo-mobile-sdk covers iOS, Android, React Native, Flutter). No server client exists in any language. Reporting and metadata writes both work; the shape assumes a human wrote the query.

signals (5)

+AI review appliedReviewer: Editorial review on 2026-08-19
−OpenAPI specNot found across 0 probe paths
·GraphQL endpointDiscovered at https://www.pendo.io/graphql, introspection disabled or scoped
+SDKs maintained5 (go, ruby, swift); top by stars: pendo-io/pendo-mobile-sdk (77 stars)
+SDK recency2 of 5 SDK repos pushed within 30 days (most recent SDK commit: 2026-08-19)

cite (1)

github.sdks@2026-08-19

Headless operation10/20

scored

Metadata writes, guide state changes, page and feature definitions and reporting all reach the API. Authoring does not. Guides are built in the Designer browser extension, page and feature tagging is a point-and-click exercise against a live app, and the Resource Center needs its own escape hatch (github.com/pendo-io/resource-center-integration-kit). No CLI, no Terraform provider, no config-as-code path.

signals (9)

+AI review appliedReviewer: Editorial review on 2026-08-19
−API operations exposedNo OpenAPI spec; operations count unknown
·Docs pages crawled0 pages (crawler: none)
·Auth schemes documentedAuth documentation page not reached by crawler
·Setup / quickstart docsNot reached by crawler
·Billing docsNot reached by crawler
·Teams / org docsNot reached by crawler
·CLI docsNot reached by crawler
·Schema / data model docsNot reached by crawler

cite (1)

github.sdks@2026-08-19

MCP & agent posture4/20

scored

Nothing official. The pendo-io org publishes Go infrastructure libraries and a mobile SDK but no MCP server, and the registry search returned nothing usable. GitHub has only hobby forks with zero stars (AsherJN/pendo-mcp, Band-Aid/pendo-ontology-mcp). A product analytics tool that agents cannot query is a product analytics tool that agents will route around. Pendo has published no agent documentation either.

signals (2)

+AI review appliedReviewer: Editorial review on 2026-08-19
·MCP detector statusTimed out during collection (likely GitHub search API rate limit without GITHUB_TOKEN). No verified evidence about MCP presence.

cite (1)

github.sdks@2026-08-19

Schema observability6/20

scored

The contract ships as Postman collections. Both doc sites are Postman-hosted (engageapi.pendo.io for Engage, feedbackapi.pendo.io for Feedback), and probes for openapi.json, swagger.json and openapi.yaml all return 404. There is no GraphQL either, despite a crawler false positive on the marketing site. An agent cannot build a client without a human reading prose first. That is the single biggest blocker on this scorecard.

signals (3)

+AI review appliedReviewer: Editorial review on 2026-08-19
−OpenAPINot discovered across 0 standard probe paths
·GraphQL introspectionGraphQL endpoint at https://www.pendo.io/graphql but introspection is disabled, scoped, or behind authentication

cite (1)

ai_review_browser.schema@2026-08-19

Webhooks & events6/20

scored

Delivery runs one way. Pendo collects behaviour and hands it back only when asked, through Aggregation queries (POST app.pendo.io/api/v1/aggregation, which answers 403 unauthenticated) or scheduled warehouse exports. The Engage documentation names no outbound event types, no signature header to verify a payload, and no retry or replay contract. Agents must poll and diff, which is expensive and lossy.

signals (2)

+AI review appliedReviewer: Editorial review on 2026-08-19
·Webhook docs pageNot reached by crawler within budget (0 pages crawled). Cannot confirm whether vendor offers webhooks.

cite (1)

github.sdks@2026-08-19

JAIRF · 6 dimensions

JAIRF · N/A

This vendor does not publish a public OpenAPI specification. JAIRF cannot be computed. The Headless Index score and editorial verdict carry the readiness assessment.

No public OpenAPI specification discovered during collection

Band rationale:D band triggered: HeadlessIndex=37

04 / Embed

Show Pendo's score on your site.

Drop a live badge into your README, footer, or marketing page. It updates automatically when we re-score, and every embed is a dofollow link back here.

Get embed code

Peers in Analytics & Events

TinybirdD

Headless Index 38/100

JuneD

Headless Index 36/100

FreshpaintD

Headless Index 35/100

See full Analytics & Events ranking →

FAQ

Pendo and agent readiness

Is Pendo agent-ready?: Pendo scores Band D on The Headless Index. Its JAIRF rating is not available because no machine-readable spec was scored. Its strongest area for agent use is API-first design intent; its weakest is MCP and agent posture.
Does Pendo publish an OpenAPI spec?: No published OpenAPI specification was found when Pendo was scored. That caps its JAIRF dimensions and forces agents to rely on documentation or reverse engineering to operate it.
What is Pendo's Headless Index score?: Pendo scores 37/100 on the Headless Index thesis-fit rubric and sits in Band D in the Analytics & Events category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.