{
 "categories": [
  "commerce",
  "enterprise"
 ],
 "deployment": "saas",
 "evidence": [
  {
   "date": "2026-10-16",
   "fact": "homepage",
   "note": "The product page is titled for the Inriver PIM product overview.",
   "source": "https://www.inriver.com/product/",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "name",
   "note": "The page names the product Inriver PIM and describes the product content lifecycle.",
   "source": "https://www.inriver.com/product/",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "vendor",
   "note": "The page is published on inriver.com and speaks as Inriver about the PIM platform.",
   "source": "https://www.inriver.com/product/",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "categories",
   "note": "The page describes syndication to retailers and e-commerce platforms and calls the platform enterprise-ready. Categories are commerce and enterprise.",
   "source": "https://www.inriver.com/product/",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "license",
   "note": "The page offers a guided demo and a consultation. It does not show a free tier. The license is commercial.",
   "source": "https://www.inriver.com/product/",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "deployment",
   "note": "The vendor llms.txt says the company type is SaaS and that the architecture is cloud-native multi-tenant SaaS. Deployment is saas.",
   "source": "https://www.inriver.com/llms.txt",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "platforms",
   "note": "The overview says the REST API exposes functionality present in the Web Portal and Control Center. Those are browser surfaces. Platforms include web.",
   "source": "https://community.inriver.com/hc/en-us/articles/360023123453-Inriver-REST-API-overview",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "modalities.api.exists",
   "note": "The article describes the inriver REST API and says it provides endpoints for reading and updating iPMC data and the business model.",
   "source": "https://community.inriver.com/hc/en-us/articles/360023123453-Inriver-REST-API-overview",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "modalities.api.kinds[0]",
   "note": "The article title and body call it the REST API.",
   "source": "https://community.inriver.com/hc/en-us/articles/360023123453-Inriver-REST-API-overview",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "modalities.api.auth[0]",
   "note": "The article says a valid REST API key is passed in the X-inRiver-APIKey header and that MCP uses the same authentication as the REST API.",
   "source": "https://www.inriver.com/resources/inriver-mcp-ai-tools-pim/",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "modalities.api.coverage",
   "note": "Read and update of iPMC data and the business model are stated, with concurrency, timeout, and batch limits. A community manager reply says Swagger is for customers and partners. Coverage is partial.",
   "source": "https://community.inriver.com/hc/en-us/articles/360023123453-Inriver-REST-API-overview",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "modalities.api.docs",
   "note": "Opened as the current public REST API overview. The method list itself is not on this page.",
   "source": "https://community.inriver.com/hc/en-us/articles/360023123453-Inriver-REST-API-overview",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "modalities.mcp.first_party",
   "note": "The Inriver article dated 15 May 2026 says Inriver MCP support was released in September 2025 and describes Query Manager and Code Writer as Inriver endpoints.",
   "source": "https://www.inriver.com/resources/inriver-mcp-ai-tools-pim/",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "modalities.mcp.verdict",
   "note": "The vendor describes first-party MCP endpoints around the REST API. The article does not print URLs. The verdict is official because the vendor states the support.",
   "source": "https://www.inriver.com/resources/inriver-mcp-ai-tools-pim/",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "modalities.agent_docs.llms_txt",
   "note": "Opened a text/plain llms.txt index. It describes Inriver PIM, syndication, and a cloud-native SaaS architecture.",
   "source": "https://www.inriver.com/llms.txt",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "verdict.scores.api",
   "note": "A documented read/write REST API with an API key and published concurrency limits is a production path. The customer or partner gate on the method list keeps the score at 6.",
   "source": "https://community.inriver.com/hc/en-us/articles/360023123453-Inriver-REST-API-overview",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "verdict.scores.mcp",
   "note": "The vendor describes two MCP endpoint roles, the API-key header, and the MCPUser permission. No server URL or repository is printed. That is a limited official description. Score 5.",
   "source": "https://www.inriver.com/resources/inriver-mcp-ai-tools-pim/",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "freshness.watch[0].url",
   "note": "Opened and verified as the current REST API overview. The page shows an update on 17 September 2026.",
   "source": "https://community.inriver.com/hc/en-us/articles/360023123453-Inriver-REST-API-overview",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "freshness.watch[1].url",
   "note": "Opened and verified as the 15 May 2026 Inriver MCP article.",
   "source": "https://www.inriver.com/resources/inriver-mcp-ai-tools-pim/",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "freshness.watch[2].url",
   "note": "Opened and verified as the current Inriver PIM product page.",
   "source": "https://www.inriver.com/product/",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "freshness.watch[3].url",
   "note": "Opened and verified as the current Inriver llms.txt index, including the SaaS architecture line.",
   "source": "https://www.inriver.com/llms.txt",
   "tier": "declared"
  }
 ],
 "freshness": {
  "last_verified": "2026-10-16",
  "volatility": "medium",
  "watch": [
   {
    "type": "docs",
    "url": "https://community.inriver.com/hc/en-us/articles/360023123453-Inriver-REST-API-overview"
   },
   {
    "type": "mcp",
    "url": "https://www.inriver.com/resources/inriver-mcp-ai-tools-pim/"
   },
   {
    "type": "docs",
    "url": "https://www.inriver.com/product/"
   },
   {
    "type": "docs",
    "url": "https://www.inriver.com/llms.txt"
   }
  ]
 },
 "homepage": "https://www.inriver.com/product/",
 "id": "inriver",
 "license": "commercial",
 "modalities": {
  "agent_docs": {
   "llms_txt": true
  },
  "api": {
   "auth": [
    "api-key"
   ],
   "coverage": "partial",
   "docs": "https://community.inriver.com/hc/en-us/articles/360023123453-Inriver-REST-API-overview",
   "exists": true,
   "kinds": [
    "rest"
   ]
  },
  "cli": {
   "exists": "unknown"
  },
  "computer_use": {
   "issues": [],
   "viability": "unknown"
  },
  "data_access": {
   "export": [
    "json"
   ],
   "import": []
  },
  "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 REST overview describes the Web Portal and Control Center. The documented machine path is the REST API. The MCP article does not print server URLs. This record is Inriver PIM, not Akeneo.\n",
   "ui_stack": [
    "web-dom"
   ],
   "vendor_support": []
  },
  "sdk": {
   "exists": "unknown",
   "languages": [],
   "official": "unknown"
  }
 },
 "name": "Inriver PIM",
 "platforms": [
  "web"
 ],
 "related": {
  "alternatives": [
   "akeneo"
  ],
  "our_products": []
 },
 "schema_version": 1,
 "score_version": 1,
 "status": "active",
 "vendor": "Inriver",
 "verdict": {
  "best_path": "api",
  "scores": {
   "api": 6,
   "cli": null,
   "computer_use": null,
   "integrations": null,
   "mcp": 5,
   "overall": 6,
   "rpa": null
  },
  "search": {
   "description": "Inriver documents a REST API key and read/write limits. The method list is for customers and partners. The MCP article does not print URLs.",
   "title": "Inriver PIM is automatable through its REST API"
  },
  "summary": "Inriver PIM is automatable today through its REST API for customers and partners. The community overview says the API exposes Portal and Control Center behavior and provides endpoints for reading and updating iPMC data and the business model. It says an API key should be treated as a username and password for the portal, and for Control Center as well when the key is generated on an administrator. The 15 May 2026 MCP article says that REST API key is sent in the X-inRiver-APIKey header. The overview limits callers to ten concurrent requests per environment and IP address, a 230 second timeout, and upsert batches of at most 100 first-level entities, 5,000 linked entities, or 100,000 field values. A community manager reply on the same page says the method list and Swagger are available to customers and partners. Inriver's article says MCP support shipped in September 2025 as a wrapper around that REST API. Query Manager fetches entity data and also needs the MCPUser permission in Control Center. Code Writer is for writing and testing REST scripts and requires no authentication. The article names Claude Desktop, VS Code, and Cursor, and it says the connection machine needs Node.js and npm. It does not print server URLs or a repository. The vendor llms.txt describes the platform as cloud-native multi-tenant SaaS. Zapier, Make, Power Automate, and n8n were not opened. Computer-use viability is unassessed. The API scores 6 because read and write are documented and the public method list is gated. The MCP description scores 5 because the article does not give a URL an agent can call. The API is the best path.\n"
 }
}