Try itExperimental
See what an agent can do with Pylon before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; commands tagged live-capable can re-run against the real endpoint from our edge, right now (▶ run live — the exact same request, live and recorded lines always labeled); the live MCP handshake runs real requests from our edge, right now — including, where the server allows it, one real read-only tool call (bring your own key for auth-gated servers); sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$curl -si https://api.usepylon.com/merecorded session — replayed, not liveVerified integrations
Connections to other tracked products — hover a chip for the verbatim evidence quote behind it.
By theme — the product's score on each story themeBy theme
Agent actions — stories about agent actions in this arenaAgent actionsevidence →
Stories about agent actions in this arena
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Channels languages — stories about channels languages in this arenaChannels languagesevidence →
Stories about channels languages in this arena
Escalation handoff — stories about escalation handoff in this arenaEscalation handoffevidence →
Stories about escalation handoff in this arena
Guardrails safety — stories about guardrails safety in this arenaGuardrails safetyevidence →
Stories about guardrails safety in this arena
Insights analytics — stories about insights analytics in this arenaInsights analyticsevidence →
Stories about insights analytics in this arena
Integrations platform — stories about integrations platform in this arenaIntegrations platformevidence →
Stories about integrations platform in this arena
Knowledge grounding — stories about knowledge grounding in this arenaKnowledge groundingevidence →
Stories about knowledge grounding in this arena
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Pricing economics — stories about pricing economics in this arenaPricing economicsevidence →
Stories about pricing economics in this arena
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Resolution quality — stories about resolution quality in this arenaResolution qualityevidence →
Stories about resolution quality in this arena
Testing qa — stories about testing qa in this arenaTesting qaevidence →
Stories about testing qa in this arena
Story verdicts — every judged story with its evidenceStory verdicts
Follow the green: where the map greys out is where Pylon stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agent actions — stories about agent actions in this arenaAgent actions
Stories about agent actions in this arena
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
✓8/10
unlocks → Machine-readable spec · Versioning policy · Official CLI · Full data export
Subscribe to events via webhooks
✓7/10
Build against official SDKs
~6/10
Issue scoped/least-privilege API credentials for an agent
~4/10
Connect an agent via an official MCP server
✓9/10
Download a machine-readable API spec (OpenAPI or equivalent)
—0/10
Rely on versioned APIs with a documented deprecation policy
—0/10
Test against a sandbox environment without touching production data
~3/10
Explore an interactive API reference with runnable examples
—0/10
Docs for agents
Point an agent at llms.txt or agent-oriented docs
✓8/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
✓8/10
Operate the product with natural-language commands
~6/10
Plug MCP servers into this product so it can use their tools
~5/10
Get AI-generated insights and suggestions from my data inside the product
~6/10
Set up automations that run autonomously in the background
~6/10
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Channels languages — stories about channels languages in this arenaChannels languages
Stories about channels languages in this arena
One agent covers chat, email, and in-app, plus the channels my customers actually use — Slack, WhatsApp, social
~5/10
The agent supports customers in many languages, even where my knowledge base exists only in English
—–
The agent handles phone calls — speech in, speech out — with the same knowledge and actions as chat
—–
Escalation handoff — stories about escalation handoff in this arenaEscalation handoff
Stories about escalation handoff in this arena
Guardrails safety — stories about guardrails safety in this arenaGuardrails safety
Stories about guardrails safety in this arena
Guardrails stop the agent from inventing policies, prices, or promises — off-knowledge questions get a safe decline, not a guess
~3/10
Launch in a supervised mode where the agent drafts replies for human approval before anything reaches a customer
—0/10
I mark topics as human-only — legal threats, cancellations, security — and the agent never freelances on them
~4/10
Insights analytics — stories about insights analytics in this arenaInsights analytics
Stories about insights analytics in this arena
Integrations platform — stories about integrations platform in this arenaIntegrations platform
Stories about integrations platform in this arena
Knowledge grounding — stories about knowledge grounding in this arenaKnowledge grounding
Stories about knowledge grounding in this arena
Knowledge stays current automatically — the agent re-syncs sources on a schedule or on change, not via manual re-uploads
~4/10
The platform surfaces knowledge gaps and conflicting content that cause the agent to miss or fumble questions
—0/10
Every answer is grounded in my own content and shows which article or source it drew from
~5/10
The agent ingests my help center, docs, past tickets, and internal wikis as knowledge sources without manual re-authoring
~5/10
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Pricing economics — stories about pricing economics in this arenaPricing economics
Stories about pricing economics in this arena
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Resolution quality — stories about resolution quality in this arenaResolution quality
Stories about resolution quality in this arena
Answers use the customer's live data — plan, order status, account history — not just generic help articles
~6/10
The agent asks clarifying questions and works through multi-step troubleshooting instead of dumping one canned answer
~5/10
The agent fully resolves a meaningful share of conversations end-to-end — measured as resolutions, not mere deflections or bounces
~3/10
I control the agent's tone and brand voice, and it stays consistent across topics and languages
~3/10
Testing qa — stories about testing qa in this arenaTesting qa
Stories about testing qa in this arena
Sorted by importance (agentic first) (high → low) · 53/53 stories · click a row’s chevron for the rationale and evidence
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 9/10 | Tprobed⚿ | |
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Cclaimed | |
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Tprobed⚿ | |
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | partial | 5/10 | Cclaimed | |
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 7/10 | Cclaimed | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Tprobed⚿ | |
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Cclaimed | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Tprobed⚿ | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Cclaimed | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Tprobed⚿ | |
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 4/10 | Tprobed⚿ | |
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ⚿ | |
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ⚿ | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | partial | 3/10 | Cclaimed | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | full | 8/10 | Tprobed⚿ | |
Dashboards show resolution rate, CSAT, handoff rate, and cost per resolution — the numbers I report to my exec team C Analytics | support leader | Insights analytics — stories about insights analytics in this arenaInsights analytics | 3 | partial | 5/10 | Cclaimed | |
Every answer is grounded in my own content and shows which article or source it drew from C Grounding | ai-native user | Knowledge grounding — stories about knowledge grounding in this arenaKnowledge grounding | 3 | partial | 5/10 | Cclaimed | |
The agent ingests my help center, docs, past tickets, and internal wikis as knowledge sources without manual re-authoring C Ingestion | support ops lead | Knowledge grounding — stories about knowledge grounding in this arenaKnowledge grounding | 3 | partial | 5/10 | Cclaimed | |
The agent takes real actions through my APIs — refunds, order changes, subscription updates — with scoped auth per action C Actions | developer | Agent actions — stories about agent actions in this arenaAgent actions | 3 | partial | 5/10 | Tprobed⚿ | |
When the agent escalates, the human gets the full conversation, a summary, and collected details — the customer never repeats themselves C Handoff | support leader | Escalation handoff — stories about escalation handoff in this arenaEscalation handoff | 3 | partial | 5/10 | Cclaimed | |
Guardrails stop the agent from inventing policies, prices, or promises — off-knowledge questions get a safe decline, not a guess C Hallucination | ai-native user | Guardrails safety — stories about guardrails safety in this arenaGuardrails safety | 3 | partial | 3/10 | Cclaimed | |
The agent fully resolves a meaningful share of conversations end-to-end — measured as resolutions, not mere deflections or bounces C Resolution | support leader | Resolution quality — stories about resolution quality in this arenaResolution quality | 3 | partial | 3/10 | Cclaimed | |
The agent runs inside my existing helpdesk — Zendesk, Salesforce, Intercom — or standalone, syncing tickets and context both ways C Helpdesk | developer | Integrations platform — stories about integrations platform in this arenaIntegrations platform | 3 | partial | 3/10 | Cclaimed | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | 0/10 | ⚿ | |
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | none | 0/10 | ||
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | n/a | 0/10 | ⚿ | |
Answers use the customer's live data — plan, order status, account history — not just generic help articles C Personalization | support leader | Resolution quality — stories about resolution quality in this arenaResolution quality | 2 | partial | 6/10 | Cclaimed | |
I encode standard operating procedures the agent follows step-by-step for known issue types, with deterministic branching C Procedures | support ops lead | Agent actions — stories about agent actions in this arenaAgent actions | 2 | partial | 6/10 | Cclaimed | |
I test the agent against historical tickets or simulated conversations before it faces real customers C Simulation | support ops lead | Testing qa — stories about testing qa in this arenaTesting qa | 2 | partial | 6/10 | Cclaimed | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 5/10 | Tprobed⚿ | |
One agent covers chat, email, and in-app, plus the channels my customers actually use — Slack, WhatsApp, social C Channels | support leader | Channels languages — stories about channels languages in this arenaChannels languages | 2 | partial | 5/10 | Cclaimed | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partial | 5/10 | Tprobed⚿ | |
The agent asks clarifying questions and works through multi-step troubleshooting instead of dumping one canned answer C Reasoning | support leader | Resolution quality — stories about resolution quality in this arenaResolution quality | 2 | partial | 5/10 | Cclaimed | |
I configure when the agent must hand off — by topic, sentiment, customer tier, or explicit request — and it reliably obeys C Rules | support ops lead | Escalation handoff — stories about escalation handoff in this arenaEscalation handoff | 2 | partial | 4/10 | Cclaimed | |
I mark topics as human-only — legal threats, cancellations, security — and the agent never freelances on them C Topic controls | support ops lead | Guardrails safety — stories about guardrails safety in this arenaGuardrails safety | 2 | partial | 4/10 | Cclaimed | |
Knowledge stays current automatically — the agent re-syncs sources on a schedule or on change, not via manual re-uploads C Freshness | support ops lead | Knowledge grounding — stories about knowledge grounding in this arenaKnowledge grounding | 2 | partial | 4/10 | Cclaimed | |
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | 0/10 | ||
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | 0/10 | ||
Launch in a supervised mode where the agent drafts replies for human approval before anything reaches a customer C Supervision | support ops lead | Guardrails safety — stories about guardrails safety in this arenaGuardrails safety | 2 | none | 0/10 | ||
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | 0/10 | ||
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Pricing is outcome-based and published — I pay per resolution with caps and controls, not an opaque enterprise quote G Pricing | support leader | Pricing economics — stories about pricing economics in this arenaPricing economics | 2 | none | untested | none yet | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | none | untested | none yet | |
The agent handles phone calls — speech in, speech out — with the same knowledge and actions as chat C Voice | support leader | Channels languages — stories about channels languages in this arenaChannels languages | 2 | none | untested | none yet | |
The agent supports customers in many languages, even where my knowledge base exists only in English C Languages | support leader | Channels languages — stories about channels languages in this arenaChannels languages | 2 | none | untested | none yet | |
AI conversations get ongoing QA — scored samples, flagged failures, and a review loop that feeds fixes back into the agent C Qa | support ops lead | Testing qa — stories about testing qa in this arenaTesting qa | 1 | partial | 5/10 | Cclaimed | |
I control the agent's tone and brand voice, and it stays consistent across topics and languages C Voice | support leader | Resolution quality — stories about resolution quality in this arenaResolution quality | 1 | partial | 3/10 | Cclaimed | |
The platform clusters conversations by topic and surfaces emerging product issues before they spike ticket volume C Insights | support leader | Insights analytics — stories about insights analytics in this arenaInsights analytics | 1 | none | 0/10 | ||
The platform surfaces knowledge gaps and conflicting content that cause the agent to miss or fumble questions C Gaps | support ops lead | Knowledge grounding — stories about knowledge grounding in this arenaKnowledge grounding | 1 | none | 0/10 | ||
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | none | 0/10 |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 46 stories with headroom
What would move Pylon’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Openness — open source, data portability, and self-hosting storiesExport all of my data in open formats and leave
nonemoves PA Scoreimpact 30
Evidence shows a REST API and webhooks for programmatic access to issues/accounts/contacts, but nothing documents a bulk data-export feature, open-format dump, or data-portability/account-closure workflow that would let a user extract all their data and leave.
Privacy posture — data-handling and privacy storiesPrevent my data from being used to train AI models
nonemoves PA Scoreimpact 30
Missing: explicit AI-training opt-out/data-usage policy, contractual or product-level control preventing training use, and any documentation addressing this specific privacy concern.
Agenticness — how well agents can access and operate the productUse an official CLI
nonemoves agent-readyimpact 30
Missing: any mention of a CLI, CLI installation instructions, or CLI command reference.
Agenticness — how well agents can access and operate the productExplore an interactive API reference with runnable examples
nonemoves API qualityimpact 30
Pylon documents a REST API and webhooks (pylon-docs-31, pylon-docs-32) but there is no evidence of an interactive API reference with runnable/try-it examples — probes explicitly found no OpenAPI/Swagger spec at any candidate path (pylon-probe-3), only static markdown docs.
Agenticness — how well agents can access and operate the productDownload a machine-readable API spec (OpenAPI or equivalent)
nonemoves API qualityimpact 30
Pylon has a REST API and docs, but explicit probes for OpenAPI/Swagger spec files at standard paths all returned 404, and no evidence anywhere shows a downloadable machine-readable spec (OpenAPI, JSON Schema, etc.) for its API.
Agenticness — how well agents can access and operate the productRely on versioned APIs with a documented deprecation policy
nonemoves API qualityimpact 30
Missing: versioning scheme (e.g., v1/v2 paths), documented deprecation timeline/policy, changelog entries about breaking changes.
Agenticness — how well agents can access and operate the productPlug MCP servers into this product so it can use their tools
partialq5/10moves agent-readyimpact 22.5
Missing: a dedicated 'add MCP server' configuration flow/UI, documentation of supported transports/auth for third-party servers, and independent or runtime evidence of a working third-party MCP connection.
Resolution quality — stories about resolution quality in this arenaThe agent fully resolves a meaningful share of conversations end-to-end — measured as resolutions, not mere deflections or bounces
partialq3/10moves PA Scoreimpact 21
Missing: quantified resolution-rate reporting, evidence distinguishing true resolutions from deflections, independent/customer validation of resolution outcomes.
Showing the top 8 of 46 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map4 surfaces · 34 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
Pylon docs docs34 stories
- The agent takes real actions through my APIs — refunds, order changes, subscription updates — with scoped auth per action
- I encode standard operating procedures the agent follows step-by-step for known issue types, with deterministic branching
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Plug MCP servers into this product so it can use their tools
- Connect an agent via an official MCP server
- Drive the product through a documented public API
- Issue scoped/least-privilege API credentials for an agent
- Build against official SDKs
- Subscribe to events via webhooks
- Get AI-generated insights and suggestions from my data inside the product
- Set up automations that run autonomously in the background
- Delegate tasks to a built-in AI assistant inside the product
- Operate the product with natural-language commands
- Test against a sandbox environment without touching production data
- Perform bulk operations across many items at once
- Define rules that trigger actions automatically on events
- One agent covers chat, email, and in-app, plus the channels my customers actually use — Slack, WhatsApp, social
- When the agent escalates, the human gets the full conversation, a summary, and collected details — the customer never repeats themselves
- I configure when the agent must hand off — by topic, sentiment, customer tier, or explicit request — and it reliably obeys
- Guardrails stop the agent from inventing policies, prices, or promises — off-knowledge questions get a safe decline, not a guess
- I mark topics as human-only — legal threats, cancellations, security — and the agent never freelances on them
- Dashboards show resolution rate, CSAT, handoff rate, and cost per resolution — the numbers I report to my exec team
- The agent runs inside my existing helpdesk — Zendesk, Salesforce, Intercom — or standalone, syncing tickets and context both ways
- Knowledge stays current automatically — the agent re-syncs sources on a schedule or on change, not via manual re-uploads
- Every answer is grounded in my own content and shows which article or source it drew from
- The agent ingests my help center, docs, past tickets, and internal wikis as knowledge sources without manual re-authoring
- Do everything through the API that I can do in the UI
- Answers use the customer's live data — plan, order status, account history — not just generic help articles
- The agent asks clarifying questions and works through multi-step troubleshooting instead of dumping one canned answer
- The agent fully resolves a meaningful share of conversations end-to-end — measured as resolutions, not mere deflections or bounces
- I control the agent's tone and brand voice, and it stays consistent across topics and languages
- AI conversations get ongoing QA — scored samples, flagged failures, and a review loop that feeds fixes back into the agent
- I test the agent against historical tickets or simulated conversations before it faces real customers
Changelog docs3 stories
Probe proofs — replayable recordings from the probe harnessProbe proofs
Replayable recordings from our probe harness — see the Prove-It protocol to submit one.
$curl -si https://api.usepylon.com/mereproduced$ curl -si https://api.usepylon.com/me
HTTP/2 401
date: Thu, 10 Sep 2026 18:40:34 GMT
content-type: application/json
content-length: 182
access-control-expose-headers: X-Pylon-Request-ID
vary: Accept-Encoding
vary: Origin
x-pylon-request-id: 35e0fdd4-bbe7-4855-a6d2-27f5847fe87d
{
"errors": [
"[redacted] must follow Bearer authorization scheme: https://www.rfc-editor.org/rfc/rfc6750#section-2.1."
],
"request_id": "35e0fdd4-bbe7-4855-a6d2-27f5847fe87d"
}
$curl -sL https://docs.usepylon.com/pylon-docs/llms.txt | head -6reproduced$ curl -sL https://docs.usepylon.com/pylon-docs/llms.txt | head -6 # Pylon ## Pylon - [Introduction](https://docs.usepylon.com/pylon-docs/getting-started/quickstart.md) - [Quick Start](https://docs.usepylon.com/pylon-docs/getting-started/publish-your-docs.md)
$curl -sL https://docs.usepylon.com/pylon-docs/integrations/pylon-mcp.md | head -8reproduced$ curl -sL https://docs.usepylon.com/pylon-docs/integrations/pylon-mcp.md | head -8 > For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/integrations/pylon-mcp.md). # Pylon MCP Expose Pylon data to AI tools and assistants via Model Context Protocol. ## Pylon MCP Server
$curl -si -X POST https://mcp.usepylon.com -H 'Content-Type: application/json' -d '<jsonrpc initialize>'reproduced$ curl -si -X POST https://mcp.usepylon.com -H 'Content-Type: application/json' -d '<jsonrpc initialize>' HTTP/2 401 date: Thu, 10 Sep 2026 18:40:34 GMT content-type: text/plain; charset=utf-8 content-length: 13 set-cookie: AWSALB=HRmv03lDBFZeh7eT81mS/tQsid4oJWw9w8Xw9or1dHg6L+A101pZEv3P8eXAhDzPlKZpE5v5jhJk0DwGPdszWNQ41QfZ0d55Fs9t5DOZyLqIsxXWiOaurVK4oaly; Expires=Thu, 17 Sep 2026 18:40:34 GMT; Path=/ set-cookie: AWSALBCORS=HRmv03lDBFZeh7eT81mS/tQsid4oJWw9w8Xw9or1dHg6L+A101pZEv3P8eXAhDzPlKZpE5v5jhJk0DwGPdszWNQ41QfZ0d55Fs9t5DOZyLqIsxXWiOaurVK4oaly; Expires=Thu, 17 Sep 2026 18:40:34 GMT; Path=/; SameSite=None; Secure access-control-expose-headers: X-Pylon-Request-ID vary: Accept-Encoding www-authenticate: Bearer resource_metadata="https://mcp.usepylon.com/.well-known/oauth-protected-resource" x-content-type-options: nosniff x-pylon-request-id: 610bca5c-334a-42aa-8f25-4f2c29c7f149 unauthorized
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
4 of 19 testable claims verified · 0 contradicted → integrity 21/100
34 distinct capability claims found in Pylon’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
4
Verified
15
Unverified
0
Contradicted
15
Undersold
Verified (7)
“Provides a GET /task-statuses API endpoint to enumerate configured task statuses”
Drive the product through a documented public APIfullproof ↗
“Agents can be connected to ticketing workflows via Webhooks, API, or Pylon MCP”
Drive the product through a documented public APIfullproof ↗
“Admins can define Custom API tools so agents can call internal or third-party API endpoints when no MCP server exists”
The agent takes real actions through my APIs — refunds, order changes, subscription updates — with scoped auth per actionpartialproof ↗
“A JavaScript API lets developers build custom workflows and behavior in code”
Drive the product through a documented public APIfullproof ↗
“Supports building complex workflows and automations to run business processes”
Define rules that trigger actions automatically on eventsfullproof ↗
“Public API allows programmatic access and actions on data within Pylon”
Drive the product through a documented public APIfullproof ↗
“AI tools authenticate via OAuth with scoped access to read/update issues, accounts, and contacts”
Issue scoped/least-privilege API credentials for an agentpartialproof ↗
Unverified (23)
“Lets humans and AI agents collaborate on investigating, resolving, and acting on customer issues”
Delegate tasks to a built-in AI assistant inside the productfullproof ↗
“Disabling a product-data sync immediately stops any run already in progress”
Knowledge stays current automatically — the agent re-syncs sources on a schedule or on change, not via manual re-uploadspartialproof ↗
“AI Support Agents deflect customer questions using content, gather internal context, and take action”
The agent fully resolves a meaningful share of conversations end-to-end — measured as resolutions, not mere deflections or bouncespartialproof ↗
“AI Support Agents deflect customer questions using content, gather internal context, and take action”
Delegate tasks to a built-in AI assistant inside the productfullproof ↗
“Lets teams build a swarm of multiple AI Agents to augment support staff”
Delegate tasks to a built-in AI assistant inside the productfullproof ↗
“Agent behavior for specific scenarios is configured via natural-language instructions”
I encode standard operating procedures the agent follows step-by-step for known issue types, with deterministic branchingpartialproof ↗
“Agents can be connected to ticketing workflows via Webhooks, API, or Pylon MCP”
Plug MCP servers into this product so it can use their toolspartialproof ↗
“Agents can be connected to ticketing workflows via Webhooks, API, or Pylon MCP”
“Can simulate interactions with the AI agent to see how it handles different questions before going live”
I test the agent against historical tickets or simulated conversations before it faces real customerspartialproof ↗
“Agents can be assigned to specific issues, giving admins full control over which issues the AI touches”
I configure when the agent must hand off — by topic, sentiment, customer tier, or explicit request — and it reliably obeyspartialproof ↗
“An issue log lets admins inspect outcomes and steps taken by the AI agent on each issue”
AI conversations get ongoing QA — scored samples, flagged failures, and a review loop that feeds fixes back into the agentpartialproof ↗
“Skills are reusable instruction sets that teach agents to handle workflows consistently”
I encode standard operating procedures the agent follows step-by-step for known issue types, with deterministic branchingpartialproof ↗
“Admins can define Custom API tools so agents can call internal or third-party API endpoints when no MCP server exists”
Plug MCP servers into this product so it can use their toolspartialproof ↗
“Agents can be connected to external sources of knowledge to expand what they can answer”
The agent ingests my help center, docs, past tickets, and internal wikis as knowledge sources without manual re-authoringpartialproof ↗
“Provides a dedicated AI-supercharged knowledge hub for Q&A articles and internal runbooks”
The agent ingests my help center, docs, past tickets, and internal wikis as knowledge sources without manual re-authoringpartialproof ↗
“Supports customers across whichever channels they use to reach the company”
One agent covers chat, email, and in-app, plus the channels my customers actually use — Slack, WhatsApp, socialpartialproof ↗
“Monitors connected Slack channels for customer issues and auto-bundles messages into tracked issues”
One agent covers chat, email, and in-app, plus the channels my customers actually use — Slack, WhatsApp, socialpartialproof ↗
“Email addresses can be connected so support requests over email are tracked and responded to”
One agent covers chat, email, and in-app, plus the channels my customers actually use — Slack, WhatsApp, socialpartialproof ↗
“Chat widgets support full custom branding, colors, and multiple separate widgets with different workflows”
I control the agent's tone and brand voice, and it stays consistent across topics and languagespartialproof ↗
“Ships with default analytics dashboards for common support metrics, filterable by many attributes”
Dashboards show resolution rate, CSAT, handoff rate, and cost per resolution — the numbers I report to my exec teampartialproof ↗
“Webhooks can be received for various events happening in Pylon”
“Daily scans customer channel conversations, uses AI to summarize them, and syncs summaries to the linked Salesforce Account”
Get AI-generated insights and suggestions from my data inside the productpartialproof ↗
“Daily scans customer channel conversations, uses AI to summarize them, and syncs summaries to the linked Salesforce Account”
The agent runs inside my existing helpdesk — Zendesk, Salesforce, Intercom — or standalone, syncing tickets and context both wayspartialproof ↗
Undersold (15)
Point an agent at llms.txt or agent-oriented docsfullproof ↗
Run the product headlessly / in CI for automationpartialproof ↗
Set up automations that run autonomously in the backgroundpartialproof ↗
Operate the product with natural-language commandspartialproof ↗
Test against a sandbox environment without touching production datapartialproof ↗
Perform bulk operations across many items at oncepartialproof ↗
When the agent escalates, the human gets the full conversation, a summary, and collected details — the customer never repeats themselvespartialproof ↗
Guardrails stop the agent from inventing policies, prices, or promises — off-knowledge questions get a safe decline, not a guesspartialproof ↗
I mark topics as human-only — legal threats, cancellations, security — and the agent never freelances on thempartialproof ↗
Every answer is grounded in my own content and shows which article or source it drew frompartialproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
Answers use the customer's live data — plan, order status, account history — not just generic help articlespartialproof ↗
The agent asks clarifying questions and works through multi-step troubleshooting instead of dumping one canned answerpartialproof ↗
Claims outside our story set (9)
Real capability claims found in Pylon’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“Account Fields page can be filtered and sorted by synced fields and alphabetically”
source ↗“Custom object forms support per-field guidance text”
source ↗“Task custom fields are visible to customers in the portal's Task Details view”
source ↗“Account column in Project views links directly to the account record”
source ↗“Tasks can be grouped by select and multi-select fields”
source ↗“Web Research fields show a selected scalar value instead of raw JSON in tables”
source ↗“Compliance and certifications are managed via Vanta and audit partners”
source ↗“Templates can be reused when creating account fields from the Accounts Table column”
source ↗“Customer portal shows a consolidated issue list across all accounts a user belongs to”
source ↗
Business model
Per-seat SaaS plus usage-based AI agent add-ons; pricing is demo-gated — the pricing page redirects to demo booking (third parties report ~$59–$139/seat/mo, 3-seat minimum). Enterprise custom.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Try Experimental
Run it in the microterminal →Recorded agent sessions — and a live MCP handshake where the vendor ships one.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
Agent surface uptime MCP up · llms.txt up (tracking since Sep 11 '26)