{
 "categories": [
  "enterprise"
 ],
 "deployment": "saas",
 "evidence": [
  {
   "date": "2026-09-16",
   "fact": "homepage",
   "note": "Opened Qualtrics' public home. Qualtrics presents XM as a commercial experience-management platform used by enterprises, governments, and healthcare.",
   "source": "https://www.qualtrics.com/",
   "tier": "declared"
  },
  {
   "date": "2026-09-16",
   "fact": "modalities.api.exists",
   "note": "Qualtrics documents the Qualtrics API as the way to automate repetitive processes and pass information in and out of Qualtrics, including account creation and contact-list work.",
   "source": "https://www.qualtrics.com/support/integrations/api-integration/overview/",
   "tier": "declared"
  },
  {
   "date": "2026-09-16",
   "fact": "modalities.api.kinds[0]",
   "note": "Qualtrics states the v3 API is a REST API using GET, POST, PUT, or DELETE requests that return JSON. The opened example POSTs to https://yourdatacenterid.qualtrics.com/API/v3/responseexports.",
   "source": "https://www.qualtrics.com/support/integrations/api-integration/overview/",
   "tier": "declared"
  },
  {
   "date": "2026-09-16",
   "fact": "modalities.api.auth[0]",
   "note": "Qualtrics requires the API token in the X-API-TOKEN header. Each user generates their own token from Qualtrics IDs after Access API permission is enabled.",
   "source": "https://www.qualtrics.com/support/integrations/api-integration/overview/",
   "tier": "declared"
  },
  {
   "date": "2026-09-16",
   "fact": "modalities.api.coverage",
   "note": "After the API feature is purchased, Qualtrics says the API can be used for products on the license, including Survey Platform and XM Directory. Site Intercept has a separate documentation link. Coverage is not every XM UI action.",
   "source": "https://www.qualtrics.com/support/integrations/api-integration/overview/",
   "tier": "declared"
  },
  {
   "date": "2026-09-16",
   "fact": "modalities.api.docs",
   "note": "Opened Qualtrics API docs home. The hub lists instructions, guides, API reference, and SDKs. This record uses the opened support overview as the assessed getting-started surface.",
   "source": "https://api.qualtrics.com/",
   "tier": "declared"
  },
  {
   "date": "2026-09-16",
   "fact": "modalities.mcp.first_party",
   "note": "Qualtrics declares a first-party MCP server for each JSON API documented on the API site, with one MCP tool per documented endpoint. Non-JSON APIs are not supported.",
   "source": "https://www.qualtrics.com/support/integrations/api-integration/overview/",
   "tier": "declared"
  },
  {
   "date": "2026-09-16",
   "fact": "modalities.mcp.verdict",
   "note": "The MCP section is vendor support documentation for Qualtrics-hosted MCP servers intended for clients such as ChatGPT, Claude, and Cursor.",
   "source": "https://www.qualtrics.com/support/integrations/api-integration/overview/",
   "tier": "declared"
  },
  {
   "date": "2026-09-16",
   "fact": "modalities.data_access.export[0]",
   "note": "The opened cURL example POSTs a surveyId and format csv to /API/v3/responseexports.",
   "source": "https://www.qualtrics.com/support/integrations/api-integration/overview/",
   "tier": "declared"
  },
  {
   "date": "2026-09-16",
   "fact": "modalities.data_access.import[0]",
   "note": "Qualtrics states a user can automate contact-list creation rather than compile and import contact lists in the UI.",
   "source": "https://www.qualtrics.com/support/integrations/api-integration/overview/",
   "tier": "declared"
  },
  {
   "date": "2026-09-16",
   "fact": "verdict.scores.api",
   "note": "The v3 REST API is a documented production surface for account, directory, and response work. Access API permission and a purchased API feature are material gates, so the path is useful rather than unusually complete.",
   "source": "https://www.qualtrics.com/support/integrations/api-integration/overview/",
   "tier": "declared"
  },
  {
   "date": "2026-09-16",
   "fact": "verdict.scores.mcp",
   "note": "Vendor-declared per-API MCP with tools mapped to JSON endpoints is official and useful. The opened page does not publish a live MCP URL or auth walkthrough, so the official path is a limited vendor preview.",
   "source": "https://www.qualtrics.com/support/integrations/api-integration/overview/",
   "tier": "declared"
  },
  {
   "date": "2026-09-16",
   "fact": "freshness.watch[0].url",
   "note": "Opened and verified as Qualtrics' current API getting-started page, including X-API-TOKEN auth and the Model Context Protocol section.",
   "source": "https://www.qualtrics.com/support/integrations/api-integration/overview/",
   "tier": "declared"
  },
  {
   "date": "2026-09-16",
   "fact": "freshness.watch[1].url",
   "note": "Opened and verified as the current Qualtrics API documentation hub listing instructions, guides, reference, and SDKs.",
   "source": "https://api.qualtrics.com/",
   "tier": "declared"
  },
  {
   "date": "2026-09-16",
   "fact": "freshness.watch[2].url",
   "note": "Opened the official MCP Registry search for qualtrics. The JSON response was servers: [] with count 0. First-party coverage remains the vendor-declared per-API MCP on the support page.",
   "source": "https://registry.modelcontextprotocol.io/v0.1/servers?search=qualtrics",
   "tier": "scraped"
  }
 ],
 "freshness": {
  "last_verified": "2026-09-16",
  "volatility": "high",
  "watch": [
   {
    "type": "docs",
    "url": "https://www.qualtrics.com/support/integrations/api-integration/overview/"
   },
   {
    "type": "docs",
    "url": "https://api.qualtrics.com/"
   },
   {
    "type": "registry",
    "url": "https://registry.modelcontextprotocol.io/v0.1/servers?search=qualtrics"
   }
  ]
 },
 "homepage": "https://www.qualtrics.com/",
 "id": "qualtrics",
 "license": "commercial",
 "modalities": {
  "agent_docs": {
   "llms_txt": "unknown"
  },
  "api": {
   "auth": [
    "api-token"
   ],
   "coverage": "partial",
   "docs": "https://www.qualtrics.com/support/integrations/api-integration/overview/",
   "exists": true,
   "kinds": [
    "rest"
   ]
  },
  "cli": {
   "exists": "unknown"
  },
  "computer_use": {
   "issues": [],
   "viability": "unknown"
  },
  "data_access": {
   "export": [
    "response-csv"
   ],
   "import": [
    "contact-lists"
   ]
  },
  "extensibility": {
   "scripting": [],
   "webhooks": "unknown"
  },
  "integrations": {
   "make": "unknown",
   "n8n": "unknown",
   "power_automate": "unknown",
   "zapier": "unknown"
  },
  "mcp": {
   "first_party": true,
   "third_party": [],
   "verdict": "official"
  },
  "rpa": {
   "drivability": "unknown",
   "notes": "No repeatable UI probe was run. The Qualtrics v3 REST API and the vendor-declared per-API MCP servers cover survey, directory, and account work without browser control of the XM UI.\n",
   "ui_stack": [
    "web-dom"
   ],
   "vendor_support": []
  },
  "sdk": {
   "exists": "unknown",
   "languages": [],
   "official": "unknown"
  }
 },
 "name": "Qualtrics",
 "platforms": [
  "web"
 ],
 "related": {
  "alternatives": [],
  "our_products": []
 },
 "schema_version": 1,
 "score_version": 1,
 "status": "active",
 "vendor": "Qualtrics",
 "verdict": {
  "best_path": "api",
  "scores": {
   "api": 7,
   "cli": null,
   "computer_use": null,
   "integrations": null,
   "mcp": 6,
   "overall": 7,
   "rpa": null
  },
  "summary": "Qualtrics is automatable today through the Qualtrics v3 REST API. This record is the Qualtrics XM Survey Platform and XM Directory, not Site Intercept as a standalone identity, and not Medallia or SurveyMonkey. Qualtrics presents the API as the way to automate account creation, contact-list work, and CRM integration instead of repeating those steps in the UI. Requests use GET, POST, PUT, or DELETE against a datacenter host such as https://{datacenter}.qualtrics.com/API/v3/... and return JSON. Authentication on the opened support page is the X-API-TOKEN header from a per-user API token. Token generation requires the Access API permission; the API feature is a purchased license add-on. Qualtrics also states it provides an MCP server for each JSON API on the API site, with tools mapped to documented endpoints, for clients such as ChatGPT, Claude, and Cursor. Example uses named on the opened page are response-rate queries and XM Directory contact updates. A dedicated API-site MCP overview slug was not opened as a live page in this pass, so MCP setup details stay on the support page. Official SDKs, a CLI, and connector catalogs were not opened. Computer-use viability is unassessed. API scores 7 and is the best path because REST create, export, and directory calls do not depend on the per-API MCP servers. MCP scores 6 as official but thinly documented on the opened page.\n"
 }
}