◎ Discry Score
qualtrics.com
analytics · API
F
0 / 100
DISCOVERY0
COMPREHENSION0
Category leader: 92 (A)
Discry your API →
ANALYTICS · RANK #27 OF 29

Qualtrics is Not Agent-Ready to agents.

Discry independently scored how well an AI agent can discover and understand the Qualtrics API from what’s public — not whether it’s usable. Below: every signal we checked, what’s costing the score, and what to change.

Discry your API — freeView the docs ↗

SCORED UNDER RUBRIC 1.2 · A full re-launch under Discry Score 2.5 — a new behavioral instrument, not comparable to these scores — is in progress.

Discovery

45% of score · 12/100
OpenAPI specA machine-readable OpenAPI/Swagger spec agents can parse.Partial
llms.txtAn llms.txt index that points agents to the docs that matter.Fail
llms.txt qualityThe llms.txt is focused, current, and well under the size budget.Fail
llms-full.txtA full-text bundle agents can load in one request.Fail
AGENTS.mdAn AGENTS.md that tells coding agents how to build on the API.Fail
.well-known/mcp.jsonA discoverable MCP manifest at a well-known path.Fail
MCP registryThe API is listed in a public MCP registry.Fail
robots.txt AI directivesrobots.txt allows (or explicitly guides) AI crawlers.Fail
SitemapA sitemap so agents can enumerate the docs surface.Fail

Comprehension

55% of score · 44/100
Task-oriented descriptionsEndpoints described by what they accomplish, not just their shape.Partial
Realistic examplesRunnable, real-world request/response examples.Partial
Multi-step workflowsDocs that chain calls into complete jobs an agent can follow.Partial
Error-recovery guidanceDocumented failure modes and how to recover from them.Partial
Answer-first formatThe answer leads; preamble does not bury it.Partial
Capability boundariesClear limits — what the API can and cannot do.Partial
Naming consistencyConsistent, predictable naming across endpoints.Pass
Heading hierarchyClean heading structure agents can navigate.Partial
Markdown docsDocs available as clean markdown, not JS-rendered HTML only.Fail
Token efficiencyDocs are concise enough to fit an agent context window.Fail

What we found

  • Qualtrics has the weakest agent-readiness in this batch — robots.txt returns JavaScript instead of a proper text file, suggesting a SPA-based docs site that resists crawling
  • A Microsoft-maintained OpenAPI spec exists for Power Platform integration but Qualtrics itself does not host one publicly
  • The docs site at api.qualtrics.com renders entirely via JavaScript, making it essentially invisible to AI agents that cannot execute JS
  • No MCP servers found in any major registry for Qualtrics
  • Documentation quality is reasonable once rendered, but the JS-only delivery makes agent consumption nearly impossible

What to change

Prioritized by impact on discoverability. You (or your docs platform) deploy these — Discry never touches your API.

  1. 01Fix the docs site to serve robots.txt and sitemap.xml as proper text/XML files rather than JS-rendered pages
  2. 02Create and host an official OpenAPI spec at a public URL
  3. 03Add llms.txt with core API capabilities in a format agents can consume without JS execution
  4. 04Create a server-rendered or static version of API documentation for agent accessibility
  5. 05Register on at least one MCP registry to enable agent discovery

Execution coverage · INFORMATIONAL, UNSCORED

Whether an agent can actually complete a call and recover from errors is the deeper Audit layer — documented here, but not part of the Discry Score.

API key✓ Error format documented✓ Rate limits documented✓ Pagination documented✕ Idempotency documented

Qualtrics uses API keys passed via X-API-TOKEN header. JSON error responses. Rate limits documented. Pagination supported.

See your own Discry Score.

Drop your API docs URL. See what an agent sees — in 60 seconds, free.

Discry your API — free