Connect Pendo to Claude
Give Claude governed access to Pendo’s 54 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Pendo to Claude in four steps
Admins approve the server once. Everyone in Claude then gets it through the same governed connection.
- 1
Approve Pendo in Runlayer
Add Pendo from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Claude to Runlayer
Admins install the Runlayer Plugin for everyone from Claude’s admin plugin settings, or users add it themselves. With direct tool listing turned on for your deployment, Pendo’s 54 tools show up in Claude’s own tool list.
Claude setup guide - 3
Sign in to Pendo
Sign in the way Pendo requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Pendo from Claude
Pendo’s approved tools appear in Claude. Every call is checked against policy and recorded.
Tools
54 Pendo tools in Claude
Runlayer policy decides which of these Claude users can call.
Account metadata schema
Return the set of metadata fields available for accounts.
Acquisition trend
Count new visitors or accounts per period - users whose first-ever interaction with the app (scope='app'), a specific page or feature (scope='page' or 'feature'), or a track event…
Agent analytics conversation analysis
Lists and ranks individual AI agent conversations with per-conversation metrics.
Agent analytics issue analysis
Returns issue diagnoses, flagged response tool/model usage, and user prompt content for the events of a specific detected issue cluster in AI Agent Analytics.
Agent analytics key metrics
Returns key aggregate metrics for AI agent conversations with period-over-period comparison.
Agent analytics tracked issue analysis
Deep-dives into a single tracked issue in AI Agent Analytics for a specific AI agent, surfacing the visitors and accounts, sampled issue explanations from detected issue clusters, the tools and…
Agent analytics tracked use case analysis
Deep-dives into a single tracked use case in AI Agent Analytics for a specific AI agent, surfacing the visitors and accounts, the tools and models the agent invoked, sampled explanations, and a…
Aggregate entity usage
Rank pages, features, or track events by aggregate usage over a date range, or measure a named set of them as one population.
Control
What Runlayer can see and stop in Claude
Some controls apply to every client at the gateway. Others depend on what Claude exposes to Runlayer.
Gateway policy (available)
Every Pendo call from Claude passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Claude as the client, the tool, and the policy and scanner decisions.
Anthropic inference hooks (available)
With Claude Enterprise, Anthropic sends each governed Claude prompt to Runlayer before inference, with nothing installed on devices (Anthropic beta).
Compliance API import (available)
Anthropic Compliance API imports Claude web and desktop chats for review.
Managed browser extension (available)
Managed Chrome, Edge, and Firefox deployments can monitor supported web-chat activity and apply prompt-time controls where the surface permits it.
Stop a call before it runs (available)
Runlayer can reject a Claude prompt before Anthropic runs it, which stops the whole request rather than one tool call.
Block output after it runs (available)
Because Runlayer checks the full prompt, tool results in it can be blocked before the model sees them.
Redact output in place (not available)
Anthropic Inference hooks cannot return a rewritten prompt, so Runlayer cannot mask content in Claude. The gateway still applies policy to the call.
Frequently asked questions
Connect more