{
 "categories": [
  "finance"
 ],
 "deployment": "saas",
 "evidence": [
  {
   "date": "2026-09-08",
   "fact": "homepage",
   "note": "Pleo presents European business spend management: issue cards, pay bills, AI expense review, and automatic accounting sync. The page states trusted by 40,000+ companies and names Xero, QuickBooks, Sage, Visma e-conomic, DATEV, and Microsoft connectors. The 40,000 figure is vendor-declared.",
   "source": "https://www.pleo.io/en",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "deployment",
   "note": "The homepage describes a cloud spend platform with cards, bills, multi-entity visibility, and accounting-tool sync. No on-prem product is offered on the opened page.",
   "source": "https://www.pleo.io/en",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "platforms",
   "note": "Pleo Support says the mobile app is in the App Store (iOS) and Google Play (Android), for pairing cards, scanning receipts, and viewing transactions. The web product is the finance console.",
   "source": "https://help.pleo.io/en/support/solutions/articles/103000254888-how-to-download-the-pleo-mobile-app",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "platforms",
   "note": "The Apple App Store listing for Pleo is published by Pleo Technologies ApS, requires iOS 15.1 or later, and describes physical and virtual cards, receipt capture, and reimbursements.",
   "source": "https://apps.apple.com/gb/app/pleo/id1110743278",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "platforms",
   "note": "The Google Play listing for package io.pleo.android is published by Pleo Technologies A/S and describes the same spend, receipt, and accounts-payable mobile flows.",
   "source": "https://play.google.com/store/apps/details?id=io.pleo.android",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "license",
   "note": "Pleo publishes paid Start (\u00a38 per user / month), Build (\u00a314), and Optimise (\u00a318) plans on the English pricing page, with additional FX, payment, and card-replacement fees. No no-cost plan is listed on the opened page.",
   "source": "https://www.pleo.io/en/pricing",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "modalities.api.exists",
   "note": "Pleo documents REST APIs with standard HTTP verbs and JSON for Export, Tags, Tax Codes, Webhook Subscriptions, Employees, and App Marketplace integrations.",
   "source": "https://developers.pleo.io/docs/current/getting-started/platform-api-overview",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "modalities.api.kinds[0]",
   "note": "The API overview states a REST API using GET, POST, PUT, and DELETE, JSON request and response bodies, and OpenAPI specifications.",
   "source": "https://developers.pleo.io/docs/current/getting-started/platform-api-overview",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "modalities.api.auth[0]",
   "note": "OAuth 2.0 is the recommended authorisation method and the required default for Early Access Programme partners. Customers grant consent; Pleo issues access tokens scoped by API permissions.",
   "source": "https://developers.pleo.io/docs/current/authentication/oauth/oauth-overview",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "modalities.api.auth[0]",
   "note": "Authenticated API calls send Authorization: Bearer <access_token>. Access tokens are short-lived (expires_in) and are refreshed; they must not be placed in query parameters.",
   "source": "https://developers.pleo.io/docs/current/how-tos/oauth/how-to-call-pleo-apis-using-access-tokens",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "modalities.api.auth[1]",
   "note": "Standalone API keys are company-controlled credentials for a single organisation. They are restricted, not self-service, and must be enabled by Pleo. Most customers currently use legacy APIs, not the new External API platform.",
   "source": "https://developers.pleo.io/docs/current/authentication/standalone-api-keys-overview",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "modalities.api.auth[1]",
   "note": "Standalone API key calls use HTTP Basic with the key as username and an empty password, for example curl -u \"YOUR-API-KEY:\" against https://external.staging.pleo.io/v2/employees.",
   "source": "https://developers.pleo.io/docs/current/how-tos/api-keys/how-to-make-an-api-call-using-standalone-api-keys",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "modalities.api.auth[1]",
   "note": "Production External API is https://external.pleo.io; staging is https://external.staging.pleo.io. OAuth uses Bearer tokens. Standalone API keys use Basic HTTP authentication with the key as username. Integrated API keys are an approved exception. All methods share a 600 requests-per-minute rate limit unless an API page states otherwise.",
   "source": "https://developers.pleo.io/docs/current/authentication/api-base-urls",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "modalities.api.coverage",
   "note": "Custom accounting integrations cover four levels: expense-item export, Tags Sync, Chart of Accounts and Tax Sync, and Vendors. Callers must be onboarded as an integration partner. That is accounting-sync coverage, not a full cards-and-wallet product API, so coverage is partial.",
   "source": "https://developers.pleo.io/docs/current/getting-started/accounting-integrations-quickstart",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "modalities.api.coverage",
   "note": "The Export API packages accounting entries as export jobs and items for ERP systems, with statuses pending, failed, completed, and completed_with_errors, and optional vendor tagging. Callers can poll GET https://external.pleo.io/v2/export-jobs. V0 is flagged for 2025 deprecation; V1 remains operational with V2 recommended.",
   "source": "https://developers.pleo.io/reference/export-api/export-api-overview",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "modalities.api.docs",
   "note": "Opened as the current API overview for REST verbs, JSON, OpenAPI, and the Export, Tags, Tax Code, Webhooks, Employees, and Marketplace surfaces.",
   "source": "https://developers.pleo.io/docs/current/getting-started/platform-api-overview",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "modalities.mcp.first_party",
   "note": "Pleo documents a first-party remote MCP at https://mcp.pleo.io/mcp with Streamable HTTP transport and OAuth 2.0, and states no Advanced or Auth settings are needed.",
   "source": "https://developers.pleo.io/docs/current/pleo-mcp/how-tos/enablement/claude",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "modalities.mcp.first_party",
   "note": "The custom MCP install page lists production URL https://mcp.pleo.io/mcp, staging URL https://mcp.staging.pleo.io/mcp, Streamable HTTP, and browser OAuth 2.0. Staging and production use separate OAuth sessions.",
   "source": "https://developers.pleo.io/docs/current/pleo-mcp/how-tos/installation/custom-mcp",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "modalities.mcp.verdict",
   "note": "Pleo's developer portal presents the MCP as the vendor agent interface that translates assistant requests into Pleo actions. Unlike REST APIs built for code, MCP tools are discovered and called by agents at runtime.",
   "source": "https://developers.pleo.io/docs/current/pleo-mcp/get-started/pleo-mcp-overview",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "modalities.mcp.first_party",
   "note": "MCP access is off by default. An admin enables it per entity under Settings \u2192 General \u2192 Pleo AI. The agent inherits the connected user's permissions, cannot elevate them, and does not support wallet top-ups, reimbursement payouts, invoice payments, or autonomous payment decisions.",
   "source": "https://developers.pleo.io/docs/current/pleo-mcp/get-started/access-and-permissions",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "modalities.mcp.first_party",
   "note": "Vendor docs say the MCP searches and retrieves expenses, completes missing details (categories, tags, splits, tax codes, notes, attendees, receipts), reviews and acts on waiting expenses, and adds ready expenses to the export queue. Read and write tools are both exposed. Named tool identifiers were not copied from a live catalog.",
   "source": "https://developers.pleo.io/docs/current/pleo-mcp/get-started/pleo-mcp-capabilities",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "modalities.extensibility.scripting[0]",
   "note": "Pleo publishes OpenAPI specifications for client generation and automated testing of the REST APIs.",
   "source": "https://developers.pleo.io/docs/current/getting-started/platform-api-overview",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "modalities.extensibility.scripting[1]",
   "note": "App Marketplace APIs are documented so partners can distribute third-party integrations through the Pleo App Marketplace.",
   "source": "https://developers.pleo.io/docs/current/getting-started/platform-api-overview",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "modalities.extensibility.webhooks",
   "note": "Webhook Subscriptions POST JSON to a public HTTPS endpoint. Subscriptions are created at POST https://external.pleo.io/v1/subscriptions. Delivery uses webhook-id, webhook-timestamp, and webhook-signature headers, with exponential retries. Export-job events include v1.export-job.created.",
   "source": "https://developers.pleo.io/reference/webhooks/overview-webhooks",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "modalities.data_access.export[0]",
   "note": "Custom accounting integrations consume immutable structured JSON records for approved expenses over the Export API after a user starts an export job in the Pleo Web App.",
   "source": "https://developers.pleo.io/docs/current/getting-started/platform-overview",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "modalities.data_access.export[1]",
   "note": "Pleo documents CSV export integrations: the Web App generates ERP-specific CSV templates that can be imported into the accounting system without API development.",
   "source": "https://developers.pleo.io/docs/current/getting-started/platform-overview",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "modalities.data_access.import[0]",
   "note": "Tags Sync imports Accounting Dimensions into Pleo as Tag Groups and Tags via the Tags API. Chart of Accounts and Tax Sync likewise create, update, unarchive, and archive records in Pleo from the accounting system.",
   "source": "https://developers.pleo.io/docs/current/platform/accounting-integrations/imports/tags/tags-sync-overview",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "modalities.data_access.import[0]",
   "note": "POST /v0/tag-groups on https://external.pleo.io creates a tag group from a JSON body (archived, code, name). Security schemes are JWT Bearer and Basic API-key authentication.",
   "source": "https://developers.pleo.io/reference/tags-api/tag-groups/creates-a-new-tag-group-resource",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "modalities.data_access.import[0]",
   "note": "The Chart of Accounts API creates, retrieves, updates, archives, and deletes accounts in Pleo so the accounting system's chart can be cached for expense categorisation.",
   "source": "https://developers.pleo.io/reference/accounts/chart-of-accounts-api-overview",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "modalities.rpa.ui_stack[0]",
   "note": "Pleo is a browser SaaS console with companion iOS and Android apps. No UI probe was run.",
   "source": "https://www.pleo.io/en",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "modalities.agent_docs.llms_txt",
   "note": "developers.pleo.io/llms.txt is a real llms.txt index titled Pleo Docs, listing current API, OAuth, export/import, webhook, and Pleo MCP pages for agents.",
   "source": "https://developers.pleo.io/llms.txt",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "verdict.scores.api",
   "note": "REST JSON OpenAPI APIs cover export, tags, tax codes, employees, webhooks, and marketplace install. OAuth 2.0, staging, rate limits, and a changelog exist. Partner EAP, restricted API keys, and accounting-sync rather than full-product scope keep the path at 7.",
   "source": "https://developers.pleo.io/docs/current/getting-started/platform-api-overview",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "verdict.scores.api",
   "note": "The developer changelog records Export API v3 fields, Accounting Entries API, Tags/Chart of Accounts/Tax sync suites, webhook auth options, and MCP docs. Legacy Expense API migration guides are published. Lifecycle is active, not unusually complete.",
   "source": "https://developers.pleo.io/changelog",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "verdict.scores.mcp",
   "note": "Official hosted MCP with documented expense read and write, review, and export-queue preparation is a maintained official server with useful coverage. Admin enablement, Optimise-plan listing, FAQ beta wording, no payment actions, and no opened named-tool catalog keep the score at 7 rather than 9\u201310.",
   "source": "https://developers.pleo.io/docs/current/pleo-mcp/get-started/pleo-mcp-capabilities",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "verdict.scores.mcp",
   "note": "The English plan comparison lists MCP as not included on Start and Build and included on Optimise. That plan gate is applied inside the MCP score.",
   "source": "https://www.pleo.io/en/pricing",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "verdict.scores.mcp",
   "note": "MCP FAQs state there is no extra MCP charge on eligible plans, that the MCP cannot change company setup, and still refer to the beta Pleo MCP. Per-user enablement is not available yet.",
   "source": "https://developers.pleo.io/docs/current/pleo-mcp/get-started/faq",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "freshness.watch[0].url",
   "note": "Opened and verified as the current English Pleo spend-management homepage.",
   "source": "https://www.pleo.io/en",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "freshness.watch[1].url",
   "note": "Opened and verified as the current OAuth 2.0 partner authentication overview.",
   "source": "https://developers.pleo.io/docs/current/authentication/oauth/oauth-overview",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "freshness.watch[2].url",
   "note": "Opened and verified as the current Claude connector page naming https://mcp.pleo.io/mcp, Streamable HTTP, and OAuth 2.0.",
   "source": "https://developers.pleo.io/docs/current/pleo-mcp/how-tos/enablement/claude",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "freshness.watch[3].url",
   "note": "Opened and verified as the current admin opt-in, per-entity enablement, inherited permissions, and no-payment-actions page.",
   "source": "https://developers.pleo.io/docs/current/pleo-mcp/get-started/access-and-permissions",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "freshness.watch[4].url",
   "note": "Opened and verified as the current declared expense-action coverage page. A live MCP tool catalog was not opened.",
   "source": "https://developers.pleo.io/docs/current/pleo-mcp/get-started/pleo-mcp-capabilities",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "freshness.watch[5].url",
   "note": "Opened and verified as the current developer-portal changelog, including Pleo MCP and Export API Version 3 entries.",
   "source": "https://developers.pleo.io/changelog",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "freshness.watch[6].url",
   "note": "Opened and verified as Pleo's current agent documentation index.",
   "source": "https://developers.pleo.io/llms.txt",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "freshness.watch[7].url",
   "note": "Opened and verified as the current English pricing page, including the MCP row on Optimise only.",
   "source": "https://www.pleo.io/en/pricing",
   "tier": "declared"
  },
  {
   "date": "2026-09-08",
   "fact": "freshness.watch[8].url",
   "note": "Opened and verified as the current Export API overview for jobs, items, webhooks, and polling.",
   "source": "https://developers.pleo.io/reference/export-api/export-api-overview",
   "tier": "declared"
  }
 ],
 "freshness": {
  "last_verified": "2026-09-08",
  "volatility": "high",
  "watch": [
   {
    "type": "docs",
    "url": "https://www.pleo.io/en"
   },
   {
    "type": "docs",
    "url": "https://developers.pleo.io/docs/current/authentication/oauth/oauth-overview"
   },
   {
    "type": "mcp",
    "url": "https://developers.pleo.io/docs/current/pleo-mcp/how-tos/enablement/claude"
   },
   {
    "type": "mcp",
    "url": "https://developers.pleo.io/docs/current/pleo-mcp/get-started/access-and-permissions"
   },
   {
    "type": "mcp",
    "url": "https://developers.pleo.io/docs/current/pleo-mcp/get-started/pleo-mcp-capabilities"
   },
   {
    "type": "changelog",
    "url": "https://developers.pleo.io/changelog"
   },
   {
    "type": "docs",
    "url": "https://developers.pleo.io/llms.txt"
   },
   {
    "type": "docs",
    "url": "https://www.pleo.io/en/pricing"
   },
   {
    "type": "docs",
    "url": "https://developers.pleo.io/reference/export-api/export-api-overview"
   }
  ]
 },
 "homepage": "https://www.pleo.io/en",
 "id": "pleo",
 "license": "commercial",
 "modalities": {
  "agent_docs": {
   "llms_txt": true
  },
  "api": {
   "auth": [
    "oauth2",
    "api-key"
   ],
   "coverage": "partial",
   "docs": "https://developers.pleo.io/docs/current/getting-started/platform-api-overview",
   "exists": true,
   "kinds": [
    "rest"
   ]
  },
  "cli": {
   "exists": "unknown"
  },
  "computer_use": {
   "issues": [],
   "viability": "unknown"
  },
  "data_access": {
   "export": [
    "api-json",
    "csv"
   ],
   "import": [
    "api-json"
   ]
  },
  "extensibility": {
   "scripting": [
    "openapi",
    "marketplace-apps"
   ],
   "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. Pleo's REST Export and Import APIs, HTTPS webhooks, and the first-party hosted MCP cover expense and accounting-sync automation without driving the web or mobile UI.\n",
   "ui_stack": [
    "web-dom"
   ],
   "vendor_support": []
  },
  "sdk": {
   "exists": "unknown",
   "languages": [],
   "official": "unknown"
  }
 },
 "name": "Pleo",
 "platforms": [
  "web",
  "ios",
  "android"
 ],
 "related": {
  "alternatives": [
   "sap-concur",
   "house-of-control"
  ],
  "our_products": []
 },
 "schema_version": 1,
 "score_version": 1,
 "status": "active",
 "vendor": "Pleo",
 "verdict": {
  "best_path": "mcp",
  "scores": {
   "api": 7,
   "cli": null,
   "computer_use": null,
   "integrations": null,
   "mcp": 7,
   "overall": 7,
   "rpa": null
  },
  "summary": "Pleo is automatable today through its first-party hosted MCP and documented REST APIs. This record is Pleo business spend management (cards, bills, expenses, accounting export and import), including the vendor-hosted MCP at https://mcp.pleo.io/mcp. It is not SAP Concur, House of Control, or Ramp. The MCP uses Streamable HTTP and browser OAuth 2.0 with no client credentials to configure. Access is off by default until a company admin enables it per entity under Settings \u2192 General \u2192 Pleo AI. The English pricing table lists MCP only on Optimise, not Start or Build; MCP FAQs say it is included with eligible plans at no extra charge and still refer to a beta. Vendor docs describe expense search and retrieval, completing missing details (categories, tags, tax codes, notes, attendees, receipts), review and approval, and adding ready expenses to the export queue. They also state the agent inherits the connected user's Pleo permissions, cannot change company setup, and does not support wallet top-ups, reimbursement payouts, invoice payments, or other payment actions. Named MCP tool identifiers were not taken from a live catalog. REST APIs at https://external.pleo.io use JSON over GET, POST, PUT, and DELETE, with OpenAPI specs, staging at https://external.staging.pleo.io, and a 600-request-per-minute rate limit. OAuth 2.0 with Bearer access tokens is the recommended partner method; standalone and integrated API keys exist as restricted exceptions and authenticate with HTTP Basic using the key as username. Documented surfaces include Export jobs and items, Tags, Chart of Accounts, Tax Codes, Employees, Companies, Vendors, and Webhook Subscriptions. Export jobs can also be consumed as immutable JSON, and the platform overview documents ERP-specific CSV templates from the web app. Partner OAuth sits behind the Early Access Programme; standalone API keys are not self-service; new External APIs are not broadly enabled by default. Zapier, Make, Microsoft Power Automate, and n8n catalogs were not opened. No official general-purpose SDK or CLI was established. Computer-use viability is unassessed. API and MCP each score 7. MCP is the best path because it is the vendor agent interface once an Optimise tenant admin has enabled it.\n"
 }
}