Pendo.io
Pendo is a product-experience and product-analytics platform that helps software teams understand and guide how users engage with their applications. Its Engage API provides programmatic access to the pages, features, guides, visitors, accounts, segments, reports, and metadata collected by the Pendo agent, plus a MongoDB-like Aggregation API for running structured queries over product-usage events. The API authenticates with a per-subscription integration key sent in the x-pendo-integration-key header (OAuth 2.0 is additionally published via RFC 8414 authorization-server metadata), and includes GDPR/CCPA bulk-deletion, segment management, in-app guide targeting, and cloud Data Sync export. Pendo was surfaced as a portfolio company of Battery Ventures.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Pendo.io the way a machine reads it — 22 machine-readable artifacts across 16 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Pendo.io scores 56.8/100 (developing), with a separate agent-readiness read of 69/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile Pendo.io
Each block below is one kind of artifact we hold for Pendo.io. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 16
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Pendo.io Account API
The Account API from Pendo.io — 2 operation(s) for account.
Pendo.io Admin API
The Admin API from Pendo.io — 1 operation(s) for admin.
Pendo.io Aggregation API
The Aggregation API from Pendo.io — 1 operation(s) for aggregation.
Pendo.io Bulk Deletion (GDPR/CCPA) API
The Bulk Deletion (GDPR/CCPA) API from Pendo.io — 4 operation(s) for bulk deletion (gdpr/ccpa).
Pendo.io Conversations API
The Conversations API from Pendo.io — 1 operation(s) for conversations.
Pendo.io Data Sync API
The Data Sync API from Pendo.io — 3 operation(s) for data sync.
Pendo.io Exclude Lists & Servers API
The Exclude Lists & Servers API from Pendo.io — 5 operation(s) for exclude lists & servers.
Pendo.io Feature API
The Feature API from Pendo.io — 1 operation(s) for feature.
Pendo.io Guide API
The Guide API from Pendo.io — 12 operation(s) for guide.
Pendo.io Listen API
The Listen API from Pendo.io — 3 operation(s) for listen.
Pendo.io Metadata API
The Metadata API from Pendo.io — 9 operation(s) for metadata.
Pendo.io Page API
The Page API from Pendo.io — 1 operation(s) for page.
Pendo.io Report API
The Report API from Pendo.io — 3 operation(s) for report.
Pendo.io Segment API
The Segment API from Pendo.io — 10 operation(s) for segment.
Pendo.io Track API
The Track API from Pendo.io — 2 operation(s) for track.
Pendo.io Visitor API
The Visitor API from Pendo.io — 3 operation(s) for visitor.
Scroll within the panel for all 16 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
pendoio-mcp.yml
MCP SERVERSecurity Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Pendo.io — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/pendoio · machine-readable index on apis.io