{
 "categories": [
  "commerce",
  "enterprise"
 ],
 "deployment": "saas",
 "evidence": [
  {
   "date": "2026-10-16",
   "fact": "homepage",
   "note": "The Akeneo site presents Akeneo for product information used in commerce, and the FAQ names Akeneo PIM.",
   "source": "https://www.akeneo.com/",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "name",
   "note": "The FAQ heading asks how Akeneo PIM differs from ERP, DAM, or MDM, and answers that Akeneo PIM manages product information for commerce.",
   "source": "https://www.akeneo.com/",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "vendor",
   "note": "The authentication guide is published on api.akeneo.com as Akeneo API documentation for the PIM.",
   "source": "https://api.akeneo.com/documentation/authentication.html",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "categories",
   "note": "The page describes product data for commerce channels and says Akeneo is used by mid-market and enterprise brands, manufacturers, distributors, and retailers.",
   "source": "https://www.akeneo.com/",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "license",
   "note": "The MCP guide addresses a PIM SaaS instance and says availability may vary by Akeneo package. The opened pages do not show a free tier. The license is commercial.",
   "source": "https://api.akeneo.com/mcp/getting-started.html",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "deployment",
   "note": "The getting-started page asks for the PIM SaaS instance URL, with the example https://yourcompany.akeneo.com. Deployment is saas.",
   "source": "https://api.akeneo.com/mcp/getting-started.html",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "platforms",
   "note": "Creating a connection is done by logging into the PIM and opening Connect, Connection settings. That is a browser app. Platforms include web.",
   "source": "https://api.akeneo.com/documentation/authentication.html",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "modalities.api.exists",
   "note": "The guide says the REST API requires authentication and shows how a connector obtains a token.",
   "source": "https://api.akeneo.com/documentation/authentication.html",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "modalities.api.kinds[0]",
   "note": "The reference is titled REST API reference and lists HTTP methods such as get, post, patch, and delete under /api/rest/v1/.",
   "source": "https://api.akeneo.com/api-reference-index.html",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "modalities.api.auth[0]",
   "note": "Connector auth is an OAuth password grant. The token request sends Authorization Basic for the client ID and secret, plus grant_type password with the API username and password. Calls then use the bearer access token.",
   "source": "https://api.akeneo.com/documentation/authentication.html",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "modalities.api.coverage",
   "note": "The reference covers products, models, families, attributes, assets, reference entities, catalogs, and workflows, with read and write on many resources. Locales and currencies are reads. Coverage is partial relative to every PIM feature.",
   "source": "https://api.akeneo.com/api-reference-index.html",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "modalities.api.docs",
   "note": "Opened as the current connector authentication guide for the PIM REST API.",
   "source": "https://api.akeneo.com/documentation/authentication.html",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "modalities.mcp.first_party",
   "note": "Akeneo documents the Akeneo MCP Server as the bridge from an Akeneo PIM instance to MCP clients, and the getting-started page gives the hosted URL.",
   "source": "https://api.akeneo.com/mcp/overview.html",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "modalities.mcp.verdict",
   "note": "The getting-started page publishes https://server.mcp.akeneo.cloud/mcp as Akeneo's hosted server and shows the credential headers. The verdict is official.",
   "source": "https://api.akeneo.com/mcp/getting-started.html",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "modalities.extensibility.webhooks",
   "note": "The Event Platform guide shows an HTTPS subscription that delivers events such as com.akeneo.pim.v1.product.updated to a destination URL.",
   "source": "https://api.akeneo.com/event-platform/getting-started.html",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "modalities.data_access.export[0]",
   "note": "The token response is a JSON object with access_token, expires_in, token_type, and refresh_token.",
   "source": "https://api.akeneo.com/documentation/authentication.html",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "modalities.agent_docs.llms_txt",
   "note": "Opened a text/plain llms.txt index. It lists Akeneo PIM, Product Cloud, and related product pages.",
   "source": "https://www.akeneo.com/llms.txt",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "verdict.scores.api",
   "note": "A broad documented REST reference with password-grant tokens and HTTPS event subscriptions is practical. Connection credentials and resource permissions keep the score at 8.",
   "source": "https://api.akeneo.com/api-reference-index.html",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "verdict.scores.mcp",
   "note": "An official hosted server with read and write on many PIM concepts is a 7. The same page leaves media files, jobs, and catalogs unsupported, and the getting-started page says package availability may vary.",
   "source": "https://api.akeneo.com/mcp/overview.html",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "freshness.watch[0].url",
   "note": "Opened and verified as the current connector authentication guide.",
   "source": "https://api.akeneo.com/documentation/authentication.html",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "freshness.watch[1].url",
   "note": "Opened and verified as the current Akeneo MCP overview, including the concept support table.",
   "source": "https://api.akeneo.com/mcp/overview.html",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "freshness.watch[2].url",
   "note": "Opened and verified as the current REST API reference index.",
   "source": "https://api.akeneo.com/api-reference-index.html",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "freshness.watch[3].url",
   "note": "Opened and verified as the current Event Platform getting-started guide.",
   "source": "https://api.akeneo.com/event-platform/getting-started.html",
   "tier": "declared"
  }
 ],
 "freshness": {
  "last_verified": "2026-10-16",
  "volatility": "high",
  "watch": [
   {
    "type": "docs",
    "url": "https://api.akeneo.com/documentation/authentication.html"
   },
   {
    "type": "mcp",
    "url": "https://api.akeneo.com/mcp/overview.html"
   },
   {
    "type": "docs",
    "url": "https://api.akeneo.com/api-reference-index.html"
   },
   {
    "type": "docs",
    "url": "https://api.akeneo.com/event-platform/getting-started.html"
   }
  ]
 },
 "homepage": "https://www.akeneo.com/",
 "id": "akeneo",
 "license": "commercial",
 "modalities": {
  "agent_docs": {
   "llms_txt": true
  },
  "api": {
   "auth": [
    "oauth2-password"
   ],
   "coverage": "partial",
   "docs": "https://api.akeneo.com/documentation/authentication.html",
   "exists": true,
   "kinds": [
    "rest"
   ]
  },
  "cli": {
   "exists": "unknown"
  },
  "computer_use": {
   "issues": [],
   "viability": "unknown"
  },
  "data_access": {
   "export": [
    "json"
   ],
   "import": []
  },
  "extensibility": {
   "scripting": [],
   "webhooks": true
  },
  "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. Connection credentials are created in the PIM under Connect, Connection settings. The documented machine paths are the REST API and the hosted MCP server. This record is Akeneo PIM, not Inriver.\n",
   "ui_stack": [
    "web-dom"
   ],
   "vendor_support": []
  },
  "sdk": {
   "exists": "unknown",
   "languages": [],
   "official": "unknown"
  }
 },
 "name": "Akeneo PIM",
 "platforms": [
  "web"
 ],
 "related": {
  "alternatives": [
   "inriver"
  ],
  "our_products": []
 },
 "schema_version": 1,
 "score_version": 1,
 "status": "active",
 "vendor": "Akeneo",
 "verdict": {
  "best_path": "api",
  "scores": {
   "api": 8,
   "cli": null,
   "computer_use": null,
   "integrations": null,
   "mcp": 7,
   "overall": 8,
   "rpa": null
  },
  "search": {
   "description": "Akeneo documents a REST API with an OAuth password grant and an official hosted MCP server. MCP availability varies by package.",
   "title": "Akeneo PIM is automatable through its API"
  },
  "summary": "Akeneo PIM is automatable today through its REST API. The connector authentication guide says a connection supplies a client ID, a secret, a username, and a password. The client posts those to /api/oauth/v1/token with grant_type password and an Authorization Basic header of the base64 client ID and secret. The response is JSON with a bearer access token that lasts 3600 seconds and a refresh token. The guide says the refresh token expiration is 1209600 seconds, which is 14 days. Later calls send Authorization Bearer. The REST reference lists create, read, update, and delete for products, product models, families, attributes, assets, reference entities, and related resources. Locales and currencies are listed as reads. The Event Platform documents HTTPS subscriptions. A subscription for com.akeneo.pim.v1.product.updated posts the event to a destination URL after the caller sends the PIM token and client ID. Akeneo also documents a hosted MCP server at https://server.mcp.akeneo.cloud/mcp. The getting-started page says availability may vary by package, that the caller supplies a PIM SaaS URL, and that the same connection credentials are sent as headers. The overview table marks products, families, attributes, categories, assets, reference entities, and workflows as readable, and most of those as writable. It marks product media files, jobs, and catalogs as unsupported. Zapier, Make, Power Automate, and n8n were not opened. Computer-use viability is unassessed. The API scores 8. The MCP server scores 7. The API is the best path because the reference covers media files, jobs, and catalogs that the MCP table leaves unsupported, and because the getting-started page says MCP availability depends on the package.\n"
 }
}