Mollie vs Airwallex

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round drawn
   Mollie✓fullprobed9/10

   Mollie publishes a live llms.txt index (verified by probe returning HTTP 200) and documents the markdown-mirror convention (append .md to any doc page) so agents can systematically discover and fetch docs; this is corroborated by an independent probe hit, not just vendor claims. missing for 10: no independent third-party (non-Mollie) report of an agent actually using llms.txt successfully in practice.

   • [claimed-docs] “docs.mollie.com publishes a full llms.txt page index and documents the markdown mirror convention on every page: "Fetch the complete documen…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.mollie.com/llms.txt # Mollie Documentation Documentation > Easily integrate online and point-of-sa…”

   proof ↗⚑ flag

   Airwallex✓fullprobed9/10

   Airwallex publishes a live llms.txt (confirmed HTTP 200 probe) plus explicit agent-oriented docs (developer-connector.md, agentos.md, ai-agent-instructions.md) designed for machine/agent consumption, including instructions written specifically for AI agents and dedicated MCP endpoints. This directly matches pointing an agent at llms.txt/agent-oriented docs. Missing for 10: independent third-party confirmation that agents successfully consume these docs in practice (only vendor docs and a probe, no hands-on community report).

   • [probe] “PROBE llms.txt: HTTP 200 at https://www.airwallex.com/llms.txt # Airwallex > Airwallex is a leading global financial platform for modern bus…”
   • [claimed-docs] “The Airwallex developer connectors connects AI coding agents — Cursor, Claude Code, Codex, and similar tools — to Airwallex documentation an…”
   • [claimed-docs] “The docs publish dedicated "Instructions for AI agents" pages (Integration Best Practices and Payments integration notes) written for machin…”
   • [claimed-docs] “A second, integration-time MCP pair: "The Airwallex developer connectors connects AI coding agents — Cursor, Claude Code, Codex, and similar…”
   • [probe] “official MCP server documented at https://www.airwallex.com/docs/developer-tools/ai/agentos”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Airwallex
   Mollie✓fullclaimed7/10

   Mollie is a REST API-based payment platform designed for headless/server-side integration: API keys, idempotency keys, webhooks, and test mode all support fully automated, non-interactive/CI-driven operation without a UI. Missing for 10: no explicit CI/CD pipeline examples, SDK/CLI tooling for automated test suites, or independent hands-on reports of running Mollie flows inside a CI pipeline.

   • [claimed-docs] “Test mode is a first-class switch: "You can access the `test` mode of the Mollie API in two ways: by using the Test API key, or... by provid…”
   • [claimed-docs] “Idempotent retries via a documented header: "you can send a unique value with every API request via the `Idempotency-Key` header. If two req…”
   • [claimed-docs] “Four documented authentication methods — API keys ("default API access for a specific payment profile"), Advanced access tokens ("advanced A…”
   • [claimed-docs] “The Payments API is at the heart of the Mollie API. It allows you to create and manage payments.”
   • [claimed-docs] “Webhooks are used to process real-time status updates, for example when a payment is paid.”

   proof ↗⚑ flag

   Airwallex✓fullprobed8/10

   Airwallex ships a documented CLI explicitly designed for scripting and CI ("script repeatable tasks, and wire Airwallex into automated systems"), plus API/webhook infrastructure enabling headless automation, corroborated by a probe confirming the CLI docs exist. Missing for 10: independent third-party evidence of actual CI pipeline usage and explicit CI/CD examples (e.g., GitHub Actions integration) beyond vendor docs.

   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”
   • [probe] “official CLI documented at https://www.airwallex.com/docs/developer-tools/cli”
   • [claimed-docs] “Webhooks with documented reliability semantics: "Your endpoint must respond with a 200 status code so that Airwallex can confirm delivery. E…”
   • [claimed-docs] “Webhooks enable Airwallex to send instant, real-time push notifications to your application when events occur in your Airwallex account.”

   proof ↗⚑ flag

3. ai-native userConnect an agent via an official MCP server

   weight 3 · round drawn
   Mollie✓fullprobed9/10

   Mollie documents an official hosted MCP server at https://mcp.mollie.com/mcp acting as a proxy for its public API, with documented API coverage (Payments, Balances, Subscriptions, Webhooks, etc.), scoped access tokens, and setup instructions for Claude Desktop, Cursor, and VS Code. Missing for 10: independent/hands-on third-party corroboration beyond vendor docs and probe confirmation.

   • [claimed-docs] “The Mollie MCP server enables merchants to use various AI tools like Claude Desktop and Cursor AI to utilize natural language for creating d…”
   • [claimed-docs] “The Mollie MCP server is hosted at a documented endpoint: "You can find Mollie MCP server at `https://mcp.mollie.com/mcp`, which acts as a p…”
   • [probe] “official MCP server documented at https://docs.mollie.com/docs/mollie-mcp-server”

   proof ↗⚑ flag

   Airwallex✓fullprobed9/10

   Airwallex documents an official hosted remote MCP server (AgentOS MCP at https://mcp.airwallex.com/mcp) with OAuth authentication, safety guardrails, and explicit connection instructions for MCP clients like Claude Code, plus a separate Developer MCP for docs/sandbox integration work — both first-party and independently probed as live docs. Missing for 10: independent hands-on third-party verification of the MCP server actually working end-to-end beyond vendor docs and a probe confirming the doc page exists.

   • [claimed-docs] “The AgentOS MCP is a hosted remote server with documented safety defaults: "Airwallex AgentOS MCP lets agents read and write production Airw…”
   • [claimed-docs] “"Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiari…”
   • [claimed-docs] “A second, integration-time MCP pair: "The Airwallex developer connectors connects AI coding agents — Cursor, Claude Code, Codex, and similar…”
   • [probe] “official MCP server documented at https://www.airwallex.com/docs/developer-tools/ai/agentos”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round to Airwallex
   Mollie—none0/10

   Mollie is a payments API/platform; while it offers an MCP server, llms.txt index, and REST API/SDKs, no evidence pack item describes an official CLI tool for managing Mollie resources or workflows. Absence of evidence for this applicable capability yields 'none'.

   ⚑ flag

   Airwallex✓fullprobed9/10

   Airwallex documents an official CLI (installable via a public install script) that exposes API resources as terminal commands, supports sandbox/production modes, scripting, and is explicitly positioned as the foundation for AI coding agents to operate accounts, corroborated by a probe confirming the docs page exists. Missing for 10: independent/hands-on third-party review of the CLI beyond vendor docs and probes.

   • [claimed-docs] “The Airwallex CLI lets you work with your Airwallex account directly from a command line.”
   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”
   • [claimed-docs] “Explore the API interactively — discover endpoints, preview requests, and inspect schemas before you commit to a full integration.”
   • [probe] “official CLI documented at https://www.airwallex.com/docs/developer-tools/cli”

   proof ↗⚑ flag

5. ai-native userDrive the product through a documented public API

   weight 3 · round to Airwallex
   Mollie✓fullprobed8/10

   Mollie exposes a comprehensive, well-documented public REST API (Payments, Subscriptions, Balances, Webhooks, etc.), plus auth schemes, idempotency headers, test mode, and an llms.txt documentation index explicitly designed for AI agent discovery, alongside an official MCP server proxying the public API for AI tools like Claude/Cursor. Missing for 10: no discoverable OpenAPI/Swagger spec (probe returned 404s) and no independent hands-on corroboration beyond vendor docs.

   • [claimed-docs] “The Payments API is at the heart of the Mollie API. It allows you to create and manage payments.”
   • [claimed-docs] “Idempotent retries via a documented header: "you can send a unique value with every API request via the `Idempotency-Key` header. If two req…”
   • [claimed-docs] “Test mode is a first-class switch: "You can access the `test` mode of the Mollie API in two ways: by using the Test API key, or... by provid…”
   • [claimed-docs] “Four documented authentication methods — API keys ("default API access for a specific payment profile"), Advanced access tokens ("advanced A…”
   • [claimed-docs] “docs.mollie.com publishes a full llms.txt page index and documents the markdown mirror convention on every page: "Fetch the complete documen…”
   • [claimed-docs] “The Mollie MCP server is hosted at a documented endpoint: "You can find Mollie MCP server at `https://mcp.mollie.com/mcp`, which acts as a p…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.mollie.com/llms.txt # Mollie Documentation Documentation > Easily integrate online and point-of-sa…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.mollie.com/openapi.json, https://docs.mollie.com/swagger.json, https://docs.mollie.com/…”
   • [probe] “official MCP server documented at https://docs.mollie.com/docs/mollie-mcp-server”

   proof ↗⚑ flag

   Airwallex✓fullprobed9/10

   Airwallex publishes extensive first-party API documentation, scoped API keys, a sandbox environment, CLI, webhooks with retry semantics, and even dedicated 'Instructions for AI agents' pages plus AgentOS/MCP tooling explicitly built for agentic/programmatic use, confirmed live via probes (llms.txt 200, CLI and AgentOS docs pages resolving). Missing for 10: independent third-party developer corroboration (e.g. community reviews of the public API itself) beyond vendor docs and probes.

   • [claimed-docs] “Programmatically create connected accounts for businesses and individuals, and enable them with rich financial capabilities.”
   • [claimed-docs] “A scoped API key grants only the resource permissions you assign (Read or Write on specific APIs), instead of full account access.”
   • [claimed-docs] “The Airwallex CLI lets you work with your Airwallex account directly from a command line.”
   • [claimed-docs] “Airwallex provides a sandbox environment, completely separate from the production environment, for testing your integration through simulati…”
   • [claimed-docs] “Webhooks enable Airwallex to send instant, real-time push notifications to your application when events occur in your Airwallex account.”
   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”
   • [claimed-docs] “"Airwallex provides a sandbox environment, completely separate from the production environment, for testing your integration through simulat…”
   • [claimed-docs] “Webhooks with documented reliability semantics: "Your endpoint must respond with a 200 status code so that Airwallex can confirm delivery. E…”
   • [claimed-docs] “The docs publish dedicated "Instructions for AI agents" pages (Integration Best Practices and Payments integration notes) written for machin…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://www.airwallex.com/llms.txt # Airwallex > Airwallex is a leading global financial platform for modern bus…”
   • [probe] “official CLI documented at https://www.airwallex.com/docs/developer-tools/cli”

   proof ↗⚑ flag

6. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round to Airwallex
   Mollie~partialclaimed6/10

   Mollie documents scoped credential mechanisms applicable to agent use: Advanced access tokens can be scoped to a specific mode or profile, API keys are scoped per payment profile with granular permissions grouped by business area/API, and the MCP server explicitly requires profile.read plus optional per-API scopes to enable individual tools. This shows a real least-privilege model usable when provisioning an agent, but there's no dedicated 'agent credential' concept, no fine-grained per-action/per-amount limits, and no independent evidence of this being used in practice for agent scoping. Missing for 10: agent-specific credential issuance workflow, granular per-action/spend-limit scoping beyond API/profile level, independent/hands-on confirmation of least-privilege enforcement in an agentic context.

   • [claimed-docs] “Four documented authentication methods — API keys ("default API access for a specific payment profile"), Advanced access tokens ("advanced A…”
   • [claimed-docs] “The Mollie MCP server is hosted at a documented endpoint: "You can find Mollie MCP server at `https://mcp.mollie.com/mcp`, which acts as a p…”
   • [claimed-docs] “The Mollie MCP server enables merchants to use various AI tools like Claude Desktop and Cursor AI to utilize natural language for creating d…”

   proof ↗⚑ flag

   Airwallex✓fullclaimed8/10

   Airwallex documents scoped API keys with granular Read/Write permissions per resource (not full account access), and explicitly ties this to agent use cases via AgentOS/MCP with additional layered safety defaults (no money-out actions by default, OAuth-scoped roles, role-gated CLI authorization). This directly matches the story of issuing least-privilege credentials for an agent. Missing for 10: independent/hands-on verification of scope enforcement and no documented UI/API walkthrough of creating a scoped key specifically for an agent identity.

   • [claimed-docs] “A scoped API key grants only the resource permissions you assign (Read or Write on specific APIs), instead of full account access.”
   • [claimed-docs] “The AgentOS MCP is a hosted remote server with documented safety defaults: "Airwallex AgentOS MCP lets agents read and write production Airw…”
   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”
   • [claimed-docs] “A second, integration-time MCP pair: "The Airwallex developer connectors connects AI coding agents — Cursor, Claude Code, Codex, and similar…”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Airwallex
   Mollie—none0/10

   The evidence pack documents Mollie's REST API references, webhooks, testing mode, and an MCP server for AI agents, but never mentions official client SDKs/libraries (e.g., PHP, Node, Python, Java clients) that developers or AI agents could build against. Since SDK availability is a standard axis for a payments API platform, its absence here is a gap rather than a category mismatch.

   ⚑ flag

   Airwallex✓fullprobed9/10

   Airwallex documents a full official SDK/API surface for AI-native building: REST API, official CLI, hosted MCP servers (AgentOS MCP and Developer MCP), dedicated AI-agent instructions pages, sandbox environment, webhooks, and plugin installs for Claude Code/Cursor. This is well beyond a typical SDK — it includes machine-readable docs, scoped API keys, and agent-specific tooling with safety guardrails, confirmed by both docs and independent probes. Missing for 10: independent third-party developer reviews/hands-on validation of SDK ergonomics beyond vendor docs.

   • [claimed-docs] “The Airwallex developer connectors connects AI coding agents — Cursor, Claude Code, Codex, and similar tools — to Airwallex documentation an…”
   • [claimed-docs] “Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiarie…”
   • [claimed-docs] “"Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiari…”
   • [claimed-docs] “The AgentOS MCP is a hosted remote server with documented safety defaults: "Airwallex AgentOS MCP lets agents read and write production Airw…”
   • [claimed-docs] “A second, integration-time MCP pair: "The Airwallex developer connectors connects AI coding agents — Cursor, Claude Code, Codex, and similar…”
   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”
   • [claimed-docs] “The docs publish dedicated "Instructions for AI agents" pages (Integration Best Practices and Payments integration notes) written for machin…”
   • [claimed-docs] “"Airwallex provides a sandbox environment, completely separate from the production environment, for testing your integration through simulat…”
   • [probe] “official MCP server documented at https://www.airwallex.com/docs/developer-tools/ai/agentos”
   • [probe] “official CLI documented at https://www.airwallex.com/docs/developer-tools/cli”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round to Airwallex
   Mollie✓fullclaimed8/10

   Mollie's next-gen Webhooks API explicitly supports permanent subscriptions to specific event types (replacing one-off payment webhooks), backed by a Webhook Events API for auditing past events and documented HMAC signature verification for security. This directly satisfies event-driven subscription via webhooks for programmatic/agentic consumption. Missing for 10: independent/hands-on verification of webhook delivery reliability and broader real-world event-type coverage beyond docs.

   • [claimed-docs] “Next-gen webhooks add a subscription model and an audit API: "Updated Webhooks API allowing you to permanently subscribe to specific event t…”
   • [claimed-docs] “Webhooks are used to process real-time status updates, for example when a payment is paid.”
   • [claimed-docs] “To verify HMAC signature for a webhook, follow these steps: 1. Retrieve the signature from the request header (X-Mollie-Signature)...”
   • [claimed-docs] “New event types to offer a broader context for your business processes (e.g. payment creation, invoice creation, onboarding status changes e…”
   • [claimed-docs] “To verify HMAC signature for a webhook, follow these steps: Retrieve the signature from the request header (X-Mollie-Signature) and obtain t…”

   proof ↗⚑ flag

   Airwallex✓fullclaimed9/10

   Airwallex documents a full webhooks system with real-time push notifications, stable event IDs for safe retry handling, delivery status inspection, and re-delivery for debugging — clearly enabling event subscription for automated/AI-native workflows. Missing for 10: no independent/hands-on corroboration beyond first-party docs.

   • [claimed-docs] “Webhooks enable Airwallex to send instant, real-time push notifications to your application when events occur in your Airwallex account.”
   • [claimed-docs] “Webhooks with documented reliability semantics: "Your endpoint must respond with a 200 status code so that Airwallex can confirm delivery. E…”

   proof ↗⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round to Airwallex
   Mollie—none0/10

   Mollie's AI-related evidence covers an MCP server that lets external AI tools create/manage payment resources via natural language, but there is no evidence of the product itself generating insights, analytics, or suggestions from a merchant's data within Mollie's own interface or reports.

   • [claimed-docs] “The Mollie MCP server enables merchants to use various AI tools like Claude Desktop and Cursor AI to utilize natural language for creating d…”
   • [claimed-docs] “The Mollie MCP server is hosted at a documented endpoint: "You can find Mollie MCP server at `https://mcp.mollie.com/mcp`, which acts as a p…”

   proof ↗⚑ flag

   Airwallex~partialclaimed4/10

   AgentOS documents pre-built agent workflows including 'building cashflow reports' and 'cashflow management' skills, which implies some data-driven insight generation via AI agents, but this is framed as an external agent toolkit for action-taking (transfers, beneficiaries, cards) rather than a native in-product analytics/insights feature surfaced to users. Missing for 10: evidence of a built-in AI insights/suggestions panel or dashboard inside the Airwallex web app itself, and independent/hands-on confirmation that agent-generated 'reports' actually surface proactive suggestions rather than just executing user-directed tasks.

   • [claimed-docs] “"Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiari…”
   • [claimed-docs] “Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiarie…”
   • [claimed-docs] “AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiaries, issuing…”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round drawn
   Mollie~partialclaimed6/10

   Mollie ships genuine background automation primitives — Subscriptions/Recurring Payments run autonomously after initial setup ('happen in the background', 'we automatically create recurring payments for you at the interval you specified') and webhooks push real-time async updates — and its MCP server lets AI tools like Claude Desktop/Cursor create these resources via natural language. However, the automation scope is narrow (payment-related resources only) and the MCP server is documented for one-off resource creation/queries, not for orchestrating persistent autonomous agent workflows. Missing for 10: evidence of AI agents scheduling/monitoring ongoing automations themselves (vs. one-time setup), and any broader workflow/automation-builder beyond payments primitives.

   • [claimed-docs] “Recurring payments happen in the background. The customer goes through the payment steps only once, for the first payment.”
   • [claimed-docs] “The Subscriptions API provides an easy way to schedule recurring payments at regular intervals. When using this API, we automatically create…”
   • [claimed-docs] “When using this API, we automatically create recurring payments for you at the interval you specified.”
   • [claimed-docs] “Webhooks are used to process real-time status updates, for example when a payment is paid.”
   • [claimed-docs] “The Mollie MCP server enables merchants to use various AI tools like Claude Desktop and Cursor AI to utilize natural language for creating d…”
   • [claimed-docs] “The Mollie MCP server is hosted at a documented endpoint: "You can find Mollie MCP server at `https://mcp.mollie.com/mcp`, which acts as a p…”
   • [claimed-docs] “Next-gen webhooks add a subscription model and an audit API: "Updated Webhooks API allowing you to permanently subscribe to specific event t…”

   proof ↗⚑ flag

   Airwallex~partialclaimed6/10

   AgentOS bundles a hosted MCP server, CLI, and pre-built 'Skills' explicitly designed for agents to run multi-step financial workflows 'on your behalf', and webhooks provide event-driven triggers with retry/dedup semantics for automated systems (awx-supp-agentos, awx-supp-agentos-mcp, awx-supp-cli, awx-supp-webhooks). However, these are agent-invoked or event-triggered rather than a documented persistent scheduler/orchestrator, and AgentOS enforces 'no money-out actions by default', limiting true autonomous background operation. Missing for 10: evidence of a native scheduling/cron mechanism or always-on background execution engine, and independent confirmation that automations run unattended without per-invocation agent triggering.

   • [claimed-docs] “"Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiari…”
   • [claimed-docs] “The AgentOS MCP is a hosted remote server with documented safety defaults: "Airwallex AgentOS MCP lets agents read and write production Airw…”
   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”
   • [claimed-docs] “Webhooks with documented reliability semantics: "Your endpoint must respond with a 200 status code so that Airwallex can confirm delivery. E…”
   • [claimed-docs] “Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiarie…”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round to Airwallex
   Mollie—none0/10

   Mollie's evidence describes an MCP server that lets external AI tools (Claude Desktop, Cursor, VS Code) call Mollie's APIs via natural language — this is Mollie acting as a tool/backend for other assistants, not a built-in AI assistant inside Mollie's own product that users delegate tasks to. No dashboard chatbot, in-app assistant, or similar built-in AI feature is documented.

   • [claimed-docs] “The Mollie MCP server enables merchants to use various AI tools like Claude Desktop and Cursor AI to utilize natural language for creating d…”
   • [claimed-docs] “The Mollie MCP server is hosted at a documented endpoint: "You can find Mollie MCP server at `https://mcp.mollie.com/mcp`, which acts as a p…”
   • [probe] “official MCP server documented at https://docs.mollie.com/docs/mollie-mcp-server”

   proof ↗⚑ flag

   Airwallex~partialclaimed5/10

   Airwallex doesn't ship a native in-product chat assistant, but its AgentOS toolkit (CLI + hosted MCP server + pre-built 'skills') lets an AI agent read balances, create beneficiaries, issue cards, and run multi-step workflows on the user's behalf, effectively delegating account tasks — though the actual assistant runs in an external client (Claude Code, Cursor, Claude Cowork) rather than being embedded in Airwallex's own UI. Missing for 10: a first-party assistant surfaced directly inside the Airwallex web app/dashboard, and independent hands-on evidence of end-users delegating tasks this way.

   • [claimed-docs] “"Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiari…”
   • [claimed-docs] “The AgentOS MCP is a hosted remote server with documented safety defaults: "Airwallex AgentOS MCP lets agents read and write production Airw…”
   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”
   • [claimed-docs] “Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiarie…”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round to Airwallex
   Mollie✓fullprobed7/10

   Mollie ships an official MCP server (hosted at mcp.mollie.com/mcp) explicitly documented as enabling merchants to use natural language via AI tools like Claude Desktop and Cursor AI to create resources in their Mollie account, with scoped OAuth access and documented client configs. Missing for 10: independent/hands-on user reports confirming reliability, and broader coverage details (only a subset of APIs are exposed via MCP, e.g. no Payments creation confirmation beyond listed APIs).

   • [claimed-docs] “The Mollie MCP server enables merchants to use various AI tools like Claude Desktop and Cursor AI to utilize natural language for creating d…”
   • [claimed-docs] “The Mollie MCP server is hosted at a documented endpoint: "You can find Mollie MCP server at `https://mcp.mollie.com/mcp`, which acts as a p…”
   • [probe] “official MCP server documented at https://docs.mollie.com/docs/mollie-mcp-server”

   proof ↗⚑ flag

   Airwallex✓fullprobed8/10

   Airwallex ships AgentOS with an MCP server and CLI explicitly designed so AI agents (Claude Code, Cursor, Codex) can read balances, create beneficiaries, issue cards, and run multi-step financial workflows via natural-language instructions, plus dedicated 'AI agent instructions' docs to guide correct NL-driven API use. Missing for 10: independent/hands-on validation of real-world NL command reliability and no third-party review beyond first-party docs.

   • [claimed-docs] “"Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiari…”
   • [claimed-docs] “The AgentOS MCP is a hosted remote server with documented safety defaults: "Airwallex AgentOS MCP lets agents read and write production Airw…”
   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”
   • [claimed-docs] “The docs publish dedicated "Instructions for AI agents" pages (Integration Best Practices and Payments integration notes) written for machin…”
   • [probe] “official MCP server documented at https://www.airwallex.com/docs/developer-tools/ai/agentos”
   • [probe] “official CLI documented at https://www.airwallex.com/docs/developer-tools/cli”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round to Airwallex
   Mollie—none0/10

   Evidence covers static markdown documentation, an llms.txt index, and reference pages, but there is no mention of an interactive API console, 'try it' runnable examples, or Postman/OpenAPI-based playground; a probe for OpenAPI/swagger specs returned 404s, suggesting no such interactive reference exists.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.mollie.com/openapi.json, https://docs.mollie.com/swagger.json, https://docs.mollie.com/…”
   • [claimed-docs] “docs.mollie.com publishes a full llms.txt page index and documents the markdown mirror convention on every page: "Fetch the complete documen…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.mollie.com/llms.txt # Mollie Documentation Documentation > Easily integrate online and point-of-sa…”

   proof ↗⚑ flag

   Airwallex~partialclaimed5/10

   Airwallex docs claim you can 'explore the API interactively — discover endpoints, preview requests, and inspect schemas before you commit to a full integration' via the CLI, and a sandbox environment lets you run real requests without live money, which together approximate an interactive, runnable API exploration experience. However, there's no evidence of a traditional in-browser interactive API reference (e.g., Swagger/Redoc-style docs with embedded runnable code snippets) — the interactivity is CLI-driven rather than a reference page. Missing for 10: a dedicated interactive web API reference UI, embedded runnable code samples in docs, and independent confirmation of this workflow.

   • [claimed-docs] “Explore the API interactively — discover endpoints, preview requests, and inspect schemas before you commit to a full integration.”
   • [claimed-docs] “Airwallex provides a sandbox environment, completely separate from the production environment, for testing your integration through simulati…”
   • [claimed-docs] “Complete a minimal end-to-end online payment in the sandbox environment using Airwallex.js and Airwallex-hosted payment page.”
   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Mollie—none0/10

   Probes for standard OpenAPI/Swagger spec locations on Mollie's docs site all returned 404, and no evidence pack item shows a published, downloadable OpenAPI/Swagger spec; the llms.txt index and markdown mirrors are documentation aids, not a machine-readable API spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.mollie.com/openapi.json, https://docs.mollie.com/swagger.json, https://docs.mollie.com/…”
   • [claimed-docs] “docs.mollie.com publishes a full llms.txt page index and documents the markdown mirror convention on every page: "Fetch the complete documen…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.mollie.com/llms.txt # Mollie Documentation Documentation > Easily integrate online and point-of-sa…”

   proof ↗⚑ flag

   Airwallex—none0/10

   While Airwallex documents extensive API tooling (CLI, MCP servers, sandbox, interactive schema explorer), none of the evidence explicitly confirms a downloadable OpenAPI (or equivalent) spec file. The 'inspect schemas' feature (airwallex-docs-20) hints at schema-driven tooling but doesn't confirm exportable machine-readable spec access.

   • [claimed-docs] “Explore the API interactively — discover endpoints, preview requests, and inspect schemas before you commit to a full integration.”
   • [probe] “official CLI documented at https://www.airwallex.com/docs/developer-tools/cli”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round to Airwallex
   Mollie✓fullclaimed8/10

   Mollie documents a first-class test mode that isolates test resources from live data, supports test API keys or a testmode parameter, replaces hosted checkout with a simulated flow, and even allows simulating refunds/chargebacks via changePaymentState — directly matching the sandbox-without-production-data story. missing for 10: no independent/hands-on third-party confirmation of sandbox behavior beyond vendor docs, and no explicit mention of sandbox support specifically for the MCP/AI-agent workflow (only general API test mode is documented).

   • [claimed-docs] “Any payments or other resources you create in test mode are completely isolated from your live mode data.”
   • [claimed-docs] “Test mode is a first-class switch: "You can access the `test` mode of the Mollie API in two ways: by using the Test API key, or... by provid…”

   proof ↗⚑ flag

   Airwallex✓fullclaimed9/10

   Airwallex documents a dedicated sandbox environment fully separate from production, covering nearly all products/APIs, with self-serve signup and simulation guides, and even AI-specific sandbox MCP/connector tooling (mcp.sandbox.airwallex.com/developer) explicitly for agents to 'create test resources, simulate events, and call sandbox endpoints' without touching production. The CLI also defaults to sandbox unless --prod is passed, reinforcing safe-by-default testing. Missing for 10: independent/hands-on confirmation of sandbox parity beyond docs.

   • [claimed-docs] “Airwallex provides a sandbox environment, completely separate from the production environment, for testing your integration through simulati…”
   • [claimed-docs] “"Airwallex provides a sandbox environment, completely separate from the production environment, for testing your integration through simulat…”
   • [claimed-docs] “A second, integration-time MCP pair: "The Airwallex developer connectors connects AI coding agents — Cursor, Claude Code, Codex, and similar…”
   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”
   • [claimed-docs] “Complete a minimal end-to-end online payment in the sandbox environment using Airwallex.js and Airwallex-hosted payment page.”

   proof ↗⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Mollie—none0/10

   The evidence shows Mollie has a v2 API (mollie-docs-12) but nothing documents a versioning scheme, deprecation policy, changelog, or sunset timeline for older API versions/endpoints. Missing for 10: explicit API versioning documentation, deprecation/sunset policy, changelog or migration guide evidence.

   • [claimed-docs] “Mollie enables you to accept payments in currencies beyond EUR through its v2 APIs, allowing international customers to transact in their pr…”

   proof ↗⚑ flag

   Airwallex—none0/10

   The evidence pack covers API keys, sandbox, CLI, MCP/AgentOS, webhooks, and AI-agent instructions, but nowhere documents API versioning conventions or a formal deprecation policy/timeline for endpoints. The only related hint is steering away from a 'legacy' SDK library, which is not evidence of a documented API versioning/deprecation policy.

   ⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Airwallex
   Mollie—none0/10

   Mollie's documented APIs (Payments, Refunds, Subscriptions, Balances, MCP server, etc.) are all single-resource endpoints; there is no evidence of a batch/bulk API, bulk payment creation, or bulk refund/webhook management across many items at once. The MCP server description explicitly frames it as creating individual resources via natural language, not bulk operations.

   • [claimed-docs] “The Mollie MCP server enables merchants to use various AI tools like Claude Desktop and Cursor AI to utilize natural language for creating d…”
   • [claimed-docs] “The Mollie MCP server is hosted at a documented endpoint: "You can find Mollie MCP server at `https://mcp.mollie.com/mcp`, which acts as a p…”
   • [claimed-docs] “The Payments API is at the heart of the Mollie API. It allows you to create and manage payments.”
   • [claimed-docs] “Next to the API endpoint, you can also create refunds manually via the Mollie Web app.”

   proof ↗⚑ flag

   Airwallex~partialclaimed4/10

   The Airwallex CLI and AgentOS toolkit let AI agents 'script repeatable tasks' and 'wire Airwallex into automated systems' or run 'multi-step financial workflows,' which implies looping over many items via API/CLI calls, but there is no documented native batch/bulk endpoint (e.g., bulk beneficiary creation, batch payouts, bulk invoice generation) for processing many items in a single call. Missing for 10: explicit bulk/batch API or CLI subcommands, evidence of batch-processing limits or throughput, and independent confirmation of bulk usage in practice.

   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”
   • [claimed-docs] “"Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiari…”
   • [claimed-docs] “Airwallex Transfers allows you to move funds across the globe easily to your suppliers, employees, contractors and/or own bank accounts.”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Airwallex
   Mollie~partialclaimed4/10

   Mollie provides event-driven building blocks — webhooks that fire on payment status changes, subscriptions that auto-create recurring payments, and application fees that auto-collect on every payment — but these are fixed, pre-built automations, not a general rules engine where a user defines arbitrary 'if event X then action Y' logic. Actual custom rule logic must be built externally by consuming webhooks in the merchant's own system. Missing for 10: a native rules/automation builder, conditional trigger-action configuration UI or API, and evidence of user-defined (vs. Mollie-predefined) automated actions.

   • [claimed-docs] “Webhooks are used to process real-time status updates, for example when a payment is paid.”
   • [claimed-docs] “Next-gen webhooks add a subscription model and an audit API: "Updated Webhooks API allowing you to permanently subscribe to specific event t…”
   • [claimed-docs] “The Subscriptions API provides an easy way to schedule recurring payments at regular intervals. When using this API, we automatically create…”
   • [claimed-docs] “Application Fees allow your platform to collect a fee on every payment you process on behalf of a connected account. You define the amount, …”
   • [claimed-docs] “Idempotent retries via a documented header: "you can send a unique value with every API request via the `Idempotency-Key` header. If two req…”

   proof ↗⚑ flag

   Airwallex~partialclaimed5/10

   Airwallex supports event-driven automation via webhooks (real-time push notifications with retry/dedupe semantics) and AgentOS/CLI/MCP tooling that lets agents run multi-step workflows, but there is no documented user-facing 'rules engine' where an AI-native user declaratively defines trigger-condition-action rules — automation still requires building a webhook consumer or scripting agent workflows rather than configuring rules in-product. missing for 10: a native rules/automation builder (event + condition + action) exposed via API or UI, and independent evidence of such rule-based automation actually firing in production.

   • [claimed-docs] “Webhooks with documented reliability semantics: "Your endpoint must respond with a 200 status code so that Airwallex can confirm delivery. E…”
   • [claimed-docs] “Webhooks enable Airwallex to send instant, real-time push notifications to your application when events occur in your Airwallex account.”
   • [claimed-docs] “"Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiari…”
   • [claimed-docs] “The AgentOS MCP is a hosted remote server with documented safety defaults: "Airwallex AgentOS MCP lets agents read and write production Airw…”
   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Mollie
   Mollie~partialclaimed6/10

   Mollie's Subscriptions API automatically creates recurring payments at specified intervals without further manual action, which is a genuine recurring-job capability, but it is scoped strictly to payment charges rather than general workflow/job scheduling. Missing for 10: any general-purpose task/workflow scheduler, cron-like triggers beyond billing, or orchestration hooks usable outside payments.

   • [claimed-docs] “When using this API, we automatically create recurring payments for you at the interval you specified.”
   • [claimed-docs] “The Subscriptions API provides an easy way to schedule recurring payments at regular intervals. When using this API, we automatically create…”
   • [claimed-docs] “Recurring payments can be used to charge customers on a regular basis or to offer automatic top-ups with credits-based services.”
   • [claimed-docs] “Recurring payments happen in the background. The customer goes through the payment steps only once, for the first payment.”

   proof ↗⚑ flag

   Airwallex~partialclaimed3/10

   Airwallex's Billing product supports recurring invoices and multi-frequency subscription billing, and AgentOS advertises 'multi-step financial workflows' and pre-built 'Skills,' but there is no documented scheduler/cron capability letting an AI agent set up or trigger recurring automated jobs itself — recurring billing is a finance feature, not an agent-orchestrated recurring workflow mechanism. missing for 10: an explicit job/workflow scheduler API or cron-like trigger for AgentOS/CLI/MCP, evidence of agents autonomously re-running workflows on a schedule, independent confirmation of recurring automation in practice.

   • [claimed-docs] “Multi-item: Billing for multiple products in one place, for example, a software license plus a support package.”
   • [claimed-docs] “Multi-frequency: Charging for different items on different schedules, for example, an annual upfront software fee combined with monthly supp…”
   • [claimed-docs] “You can issue invoices in two ways with Airwallex Billing: One-time invoices ... Recurring invoices”
   • [claimed-docs] “"Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiari…”
   • [claimed-docs] “AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiaries, issuing…”

   proof ↗⚑ flag

Ai billing ops

1. ai-native userHave an agent monitor failed payments via API and webhooks and drive retries and dunning outreach

   weight 3 · round to Airwallex
   Mollie~partialclaimed4/10

   Mollie exposes webhooks with real-time payment status updates (including failures) and a Subscriptions/Payments API that an agent could poll or subscribe to via the MCP server, giving raw building blocks for monitoring failed payments programmatically. However, there is no documented dunning/retry-management feature, automated retry scheduling, or outreach tooling — an agent would have to build all retry/dunning logic itself on top of raw webhook events and API calls. Missing for 10: native dunning/retry automation, documented failed-payment recovery workflow, and evidence of an agent orchestrating retries end-to-end.

   • [claimed-docs] “Webhooks are used to process real-time status updates, for example when a payment is paid.”
   • [claimed-docs] “Next-gen webhooks add a subscription model and an audit API: "Updated Webhooks API allowing you to permanently subscribe to specific event t…”
   • [claimed-docs] “The Subscriptions API provides an easy way to schedule recurring payments at regular intervals. When using this API, we automatically create…”
   • [claimed-docs] “The Mollie MCP server is hosted at a documented endpoint: "You can find Mollie MCP server at `https://mcp.mollie.com/mcp`, which acts as a p…”
   • [claimed-docs] “Webhooks are used to process real-time status updates, for example when a payment is paid. It is a URL Mollie will call with the ID of the u…”

   proof ↗⚑ flag

   Airwallex~partialclaimed5/10

   Airwallex provides the raw building blocks an agent could use for this story: webhooks with retry-safe event IDs and delivery inspection/re-delivery, an AgentOS MCP/CLI toolkit that can read balances and act on the production account, and API access to payments/billing data. However, there is no documented failed-payment monitoring workflow, no dunning/retry-specific Skill, and 'no money-out actions by default' in AgentOS suggests retry/charge actions would be restricted, requiring custom agent logic rather than a built-in capability. missing for 10: a documented failed-payment retry or dunning skill/workflow, evidence of automated retry logic tied to webhook failed-payment events, and confirmation that money-out/retry actions are actually permitted for agents rather than blocked by default guardrails.

   • [claimed-docs] “Webhooks with documented reliability semantics: "Your endpoint must respond with a 200 status code so that Airwallex can confirm delivery. E…”
   • [claimed-docs] “The AgentOS MCP is a hosted remote server with documented safety defaults: "Airwallex AgentOS MCP lets agents read and write production Airw…”
   • [claimed-docs] “"Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiari…”
   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”
   • [claimed-docs] “Webhooks enable Airwallex to send instant, real-time push notifications to your application when events occur in your Airwallex account.”
   • [claimed-docs] “Multi-item: Billing for multiple products in one place, for example, a software license plus a support package.”

   proof ↗⚑ flag

2. ai-native userHave an agent provision a new product, price, and payment link via the API in a single session

   weight 3 · round to Airwallex
   Mollie~partialclaimed4/10

   Mollie's MCP server (mollie-supp-mcp-server) lets an agent create resources including Payment Links via natural language in one session, and the Payment Links API supports generating a shareable payment link directly from an amount/description (mollie-docs-5, mollie-docs-23). However, Mollie has no documented 'Product' or 'Price' catalog objects (unlike Stripe-style billing) — the MCP tool coverage list (Balances, Captures, Customers, Invoices, Mandates, Methods, Payments, Payment Links, Settlements, Subscriptions, Terminals, Webhooks) never mentions Products or Prices APIs, so the exact three-step workflow described isn't evidenced. Missing for 10: a Products/Prices API or equivalent catalog resource, an end-to-end documented/independent example of an agent chaining product+price+link creation in one session.

   • [claimed-docs] “The Mollie MCP server is hosted at a documented endpoint: "You can find Mollie MCP server at `https://mcp.mollie.com/mcp`, which acts as a p…”
   • [claimed-docs] “With the Payment Links API you can generate a payment link to share with your customer... shared via email or chat applications.”
   • [claimed-docs] “With the Payment Links API you can generate a payment link to share with your customer. The payment link can for example be attached to an u…”
   • [claimed-docs] “The Payments API is at the heart of the Mollie API. It allows you to create and manage payments.”

   proof ↗⚑ flag

   Airwallex~partialclaimed6/10

   Airwallex has real billing/invoicing/payment-link APIs and an agent-facing toolkit (AgentOS/CLI/MCP) that can create beneficiaries, cards, and run multi-step workflows, and docs explicitly cover products, subscriptions, invoicing, and payment links, but no evidence shows a documented single-session flow where an agent creates a product, sets a price, and generates a payment link end-to-end via one skill/workflow. missing for 10: an explicit worked example or skill covering product+price+payment-link creation in one agent session, and independent/hands-on confirmation this multi-step billing workflow works in practice.

   • [claimed-docs] “Payment Links are the easiest way for you to accept payments online without a digital storefront.”
   • [claimed-docs] “Multi-item: Billing for multiple products in one place, for example, a software license plus a support package.”
   • [claimed-docs] “Generate invoices and digital payment links with over 160+ local payment methods”
   • [claimed-docs] “"Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiari…”
   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”
   • [claimed-docs] “The AgentOS MCP is a hosted remote server with documented safety defaults: "Airwallex AgentOS MCP lets agents read and write production Airw…”
   • [claimed-docs] “Airwallex Billing layers subscriptions, invoicing, and hosted/embedded billing checkout on top of payments acceptance — documented getting-s…”

   proof ↗⚑ flag

Invoicing

1. finance-ops userSend hosted invoices with online payment and automatic reminders

   weight 2 · round to Airwallex
   Mollie~partialclaimed3/10

   Mollie's Payment Links can be attached to an unpaid invoice and shared via email/chat, giving a hosted payment option for invoices, and an 'Invoices API' is listed among MCP-server-exposed APIs, but there is no documentation of generating/sending actual hosted invoice documents or of automatic payment reminders. missing for 10: dedicated hosted-invoice creation/send flow, automatic reminder scheduling, and any invoice-status/reminder API details.

   • [claimed-docs] “With the Payment Links API you can generate a payment link to share with your customer... shared via email or chat applications.”
   • [claimed-docs] “With the Payment Links API you can generate a payment link to share with your customer. The payment link can for example be attached to an u…”
   • [claimed-docs] “The Mollie MCP server is hosted at a documented endpoint: "You can find Mollie MCP server at `https://mcp.mollie.com/mcp`, which acts as a p…”

   proof ↗⚑ flag

   Airwallex~partialclaimed6/10

   Airwallex Billing supports one-time and recurring invoicing with online payment via 160+ local payment methods (docs-14, docs-25), but the evidence pack does not explicitly confirm automatic payment reminders for unpaid invoices. missing for 10: explicit documentation of automated reminder scheduling/notifications for overdue invoices, independent/hands-on confirmation of the reminder feature working in practice.

   • [claimed-docs] “Generate invoices and digital payment links with over 160+ local payment methods”
   • [claimed-docs] “You can issue invoices in two ways with Airwallex Billing: One-time invoices ... Recurring invoices”
   • [claimed-docs] “Airwallex Billing layers subscriptions, invoicing, and hosted/embedded billing checkout on top of payments acceptance — documented getting-s…”
   • [claimed-docs] “Multi-item: Billing for multiple products in one place, for example, a software license plus a support package.”

   proof ↗⚑ flag

Subscriptions

1. finance-ops userAutomatically retry failed subscription payments with smart dunning and recovery emails

   weight 2 · round drawn
   Mollie—none0/10

   Mollie's docs cover Subscriptions API, recurring payments, webhooks, and idempotency, but none of the evidence describes automatic retry logic for failed subscription payments, dunning schedules, or recovery emails to customers — this is a distinct capability not documented anywhere in the pack.

   ⚑ flag

   Airwallex—none0/10

   Airwallex Billing docs cover subscriptions, invoicing, and payment collection but there is no mention of automatic retry logic for failed subscription payments, smart dunning rules, or automated recovery email sequences.

   • [claimed-docs] “Multi-item: Billing for multiple products in one place, for example, a software license plus a support package.”
   • [claimed-docs] “Generate invoices and digital payment links with over 160+ local payment methods”
   • [claimed-docs] “Multi-frequency: Charging for different items on different schedules, for example, an annual upfront software fee combined with monthly supp…”
   • [claimed-docs] “You can issue invoices in two ways with Airwallex Billing: One-time invoices ... Recurring invoices”
   • [claimed-docs] “Airwallex Billing layers subscriptions, invoicing, and hosted/embedded billing checkout on top of payments acceptance — documented getting-s…”

   proof ↗⚑ flag

2. developerSet up recurring subscription billing with plans, trials, upgrades, and proration

   weight 3 · round to Airwallex
   Mollie~partialclaimed4/10

   Mollie's Subscriptions API automates recurring payments at set intervals, which covers basic recurring billing, but the evidence shows no concept of 'plans' as reusable templates, no trial period support, no subscription upgrade/downgrade mechanism, and no proration logic — these are core parts of the story. missing for 10: plan/catalog abstraction, trial period support, upgrade/downgrade workflows, proration calculation, and any documented example of managing subscription lifecycle changes.

   • [claimed-docs] “When using this API, we automatically create recurring payments for you at the interval you specified.”
   • [claimed-docs] “The Subscriptions API provides an easy way to schedule recurring payments at regular intervals. When using this API, we automatically create…”
   • [claimed-docs] “Recurring payments happen in the background. The customer goes through the payment steps only once, for the first payment.”
   • [claimed-docs] “Recurring payments can be used to charge customers on a regular basis or to offer automatic top-ups with credits-based services.”

   proof ↗⚑ flag

   Airwallex~partialclaimed5/10

   Airwallex Billing documents subscription management with multi-item and multi-frequency billing plus recurring invoicing, indicating core plan-based recurring billing capability. However, the evidence pack never mentions trial periods, plan upgrades/downgrades, or proration logic explicitly. Missing for 10: documented trial period support, upgrade/downgrade workflows, and proration calculation mechanics.

   • [claimed-docs] “Multi-item: Billing for multiple products in one place, for example, a software license plus a support package.”
   • [claimed-docs] “Multi-frequency: Charging for different items on different schedules, for example, an annual upfront software fee combined with monthly supp…”
   • [claimed-docs] “You can issue invoices in two ways with Airwallex Billing: One-time invoices ... Recurring invoices”
   • [claimed-docs] “Airwallex Billing layers subscriptions, invoicing, and hosted/embedded billing checkout on top of payments acceptance — documented getting-s…”

   proof ↗⚑ flag

Card acceptance

1. founderAccept an online card payment within a day of signing up

   weight 3 · round drawn
   Mollie~partialclaimed6/10

   Mollie offers multiple fast paths to accept a card payment—hosted checkout, plug-and-play e-commerce plugins (Shopify/WooCommerce/Magento), and no-code Payment Links shareable via email/chat—all of which could plausibly go live quickly after signup. However, there is no explicit evidence about account verification/KYC turnaround time or a documented 'go live same day' onboarding flow, which is the crux of the founder's story. Missing for 10: explicit onboarding/KYC approval timeline evidence, first-party or independent confirmation that a new merchant can complete verification and accept a live payment within 24 hours.

   • [claimed-docs] “we provide integrations for all common e-commerce platforms, such as Shopify, WooCommerce, and Magento. Simply installing the Mollie module …”
   • [claimed-docs] “Three documented integration depths: hosted checkout (Mollie-hosted payment pages), Mollie Components (embeddable card components for PCI sc…”
   • [claimed-docs] “With the Payment Links API you can generate a payment link to share with your customer... shared via email or chat applications.”
   • [claimed-docs] “Mollie provides a hosted checkout environment dubbed Mollie Checkout. These hosted payment pages allow your customer to select their payment…”
   • [claimed-docs] “With the Payment Links API you can generate a payment link to share with your customer. The payment link can for example be attached to an u…”

   proof ↗⚑ flag

   Airwallex~partialclaimed6/10

   Airwallex offers fast-to-integrate options for accepting online card payments quickly (Payment Links requiring no storefront, Hosted Payment Page, Drop-in Element, sandbox quickstart), which are consistent with a founder going live within a day. However, the evidence does not document the actual account-opening/KYC onboarding timeline or approval SLA for a brand-new founder signing up, which is the critical gatekeeper before any live payment can be accepted. Missing for 10: documented onboarding/KYB approval turnaround time, explicit same-day go-live confirmation, and independent/hands-on evidence of a founder completing signup-to-first-payment within 24 hours.

   • [claimed-docs] “Payment Links are the easiest way for you to accept payments online without a digital storefront.”
   • [claimed-docs] “Hosted Payment Page is a secure, pre-built payment page hosted by Airwallex that lets you accept multiple payment methods with a single inte…”
   • [claimed-docs] “Automatically adjusts input fields to collect information based on the payment method and country.”
   • [claimed-docs] “Complete a minimal end-to-end online payment in the sandbox environment using Airwallex.js and Airwallex-hosted payment page.”

   proof ↗⚑ flag

Checkout surfaces

1. developerEmbed customizable payment components directly in my own site or app instead of redirecting to a hosted page

   weight 3 · round drawn
   Mollie✓fullclaimed8/10

   Mollie Components (Mollie JS) let developers embed PCI-DSS-compliant card fields directly in their own checkout UI rather than redirecting to a hosted page, and docs explicitly outline build-your-own-checkout via the Payments API as an alternative to hosted checkout. This covers the core story of embeddable, customizable payment components. Missing for 10: independent/hands-on developer corroboration of styling customization depth and broader component coverage beyond card fields.

   • [claimed-docs] “If, however, you are keen on building your own checkout experience, below we offer a way to implement it.”
   • [claimed-docs] “Mollie JS is a set of Javascript APIs that allow you to add the fields needed for credit card holder data to your own checkout, in a way tha…”
   • [claimed-docs] “Three documented integration depths: hosted checkout (Mollie-hosted payment pages), Mollie Components (embeddable card components for PCI sc…”

   proof ↗⚑ flag

   Airwallex✓fullclaimed8/10

   Airwallex offers a Drop-in Element and embeddable checkout components (createElement with customizable appearance/layout, field auto-adjustment) as an alternative to the Hosted Payment Page, plus embedded checkout in Billing, directly enabling in-page/in-app embedded payments rather than redirects. Missing for 10: independent/hands-on developer corroboration of the embedded element's real-world customization depth and no evidence of broader UI kit flexibility beyond docs.

   • [claimed-docs] “Automatically adjusts input fields to collect information based on the payment method and country.”
   • [claimed-docs] “Pass appearance and layout in createElement(...). For examples and supported values, see Customize style and appearance”
   • [claimed-docs] “Complete a minimal end-to-end online payment in the sandbox environment using Airwallex.js and Airwallex-hosted payment page.”
   • [claimed-docs] “Airwallex Billing layers subscriptions, invoicing, and hosted/embedded billing checkout on top of payments acceptance — documented getting-s…”
   • [claimed-docs] “Custom styling rules so you can match the look and feel of your site”

   proof ↗⚑ flag

2. developerRedirect customers to a vendor-hosted, conversion-optimized checkout page without building my own payment UI

   weight 3 · round drawn
   Mollie✓fullclaimed9/10

   Mollie's hosted checkout is explicitly documented as a Mollie-hosted, device-optimized payment page that lets developers redirect customers without building their own UI, with e-commerce platform plugins and Payments API integration for redirect flows. missing for 10: independent/hands-on conversion-optimization evidence beyond vendor docs.

   • [claimed-docs] “Mollie provides a hosted checkout environment dubbed Mollie Checkout. These hosted payment pages allow your customer to select their payment…”
   • [claimed-docs] “Mollie's hosted payment pages have been optimized for devices of all common brands and sizes, including phones and tablets.”
   • [claimed-docs] “Three documented integration depths: hosted checkout (Mollie-hosted payment pages), Mollie Components (embeddable card components for PCI sc…”
   • [claimed-docs] “we provide integrations for all common e-commerce platforms, such as Shopify, WooCommerce, and Magento. Simply installing the Mollie module …”
   • [claimed-docs] “The Payments API is at the heart of the Mollie API. It allows you to create and manage payments.”

   proof ↗⚑ flag

   Airwallex✓fullclaimed9/10

   Airwallex documents a Hosted Payment Page — a secure, pre-built, Airwallex-hosted checkout supporting multiple payment methods with custom styling, plus a quickstart showing end-to-end integration without building custom payment UI, and payment links for no-code acceptance. missing for 10: independent/hands-on conversion-optimization benchmarks beyond vendor docs.

   • [claimed-docs] “Hosted Payment Page is a secure, pre-built payment page hosted by Airwallex that lets you accept multiple payment methods with a single inte…”
   • [claimed-docs] “Custom styling rules so you can match the look and feel of your site”
   • [claimed-docs] “Complete a minimal end-to-end online payment in the sandbox environment using Airwallex.js and Airwallex-hosted payment page.”
   • [claimed-docs] “Payment Links are the easiest way for you to accept payments online without a digital storefront.”

   proof ↗⚑ flag

No code selling

1. founderCreate a shareable payment link from the dashboard with no code and start selling immediately

   weight 2 · round drawn
   Mollie~partialclaimed6/10

   Mollie's docs confirm a no-code Payment Links capability that lets founders generate a shareable link (email/chat) without building a full checkout, and it's explicitly called out as a 'no-code' option alongside hosted/API checkouts [mollie-docs-5, mollie-docs-23, mollie-supp-hosted-checkout]. However, the evidence never explicitly shows the dashboard UI flow for creating a payment link (it frames it as an API), so it's unclear if a founder can do this purely by clicking in the dashboard with zero technical setup. Missing for 10: explicit dashboard UI screenshots/steps for generating a payment link with no code, and confirmation that no account/API key setup is needed before selling.

   • [claimed-docs] “With the Payment Links API you can generate a payment link to share with your customer... shared via email or chat applications.”
   • [claimed-docs] “With the Payment Links API you can generate a payment link to share with your customer. The payment link can for example be attached to an u…”
   • [claimed-docs] “Three documented integration depths: hosted checkout (Mollie-hosted payment pages), Mollie Components (embeddable card components for PCI sc…”

   proof ↗⚑ flag

   Airwallex~partialclaimed6/10

   Payment Links are documented as 'the easiest way to accept payments online without a digital storefront,' supporting no-code shareable link creation, and other docs (invoicing, quickstart) reinforce a self-serve dashboard flow. However, there's no direct evidence of the dashboard UI/UX for founders (e.g., screenshots, step count, signup-to-first-sale time) or independent/hands-on confirmation of ease of setup. missing for 10: dashboard UI walkthrough or screenshots, independent/hands-on confirmation of no-code simplicity, evidence of account approval/KYC turnaround time before selling.

   • [claimed-docs] “Payment Links are the easiest way for you to accept payments online without a digital storefront.”
   • [claimed-docs] “Generate invoices and digital payment links with over 160+ local payment methods”
   • [claimed-docs] “Complete a minimal end-to-end online payment in the sandbox environment using Airwallex.js and Airwallex-hosted payment page.”

   proof ↗⚑ flag

Payment methods

1. founderOffer digital wallets and local payment methods (Apple Pay, Google Pay, bank redirects, BNPL) from the same integration

   weight 2 · round to Airwallex
   Mollie~partialclaimed5/10

   Mollie's hosted checkout is documented as a single integration where 'customer can select their payment method of choice' (mollie-docs-21), and Apple Pay is explicitly called out as a checkout button option (mollie-docs-35), supporting the core 'one integration, many methods' claim. However, the evidence pack never explicitly names Google Pay, bank redirects (iDEAL/SEPA/Bancontact), or BNPL options (Klarna/Riverty) as available methods within this single integration. Missing for 10: explicit documentation of Google Pay support, bank redirect methods, and BNPL options within the same checkout integration.

   • [claimed-docs] “Mollie provides a hosted checkout environment dubbed Mollie Checkout. These hosted payment pages allow your customer to select their payment…”
   • [claimed-docs] “Display the Apple Pay button on your cart, checkout, and product pages... to speed up checkout.”
   • [claimed-docs] “Three documented integration depths: hosted checkout (Mollie-hosted payment pages), Mollie Components (embeddable card components for PCI sc…”
   • [claimed-docs] “Mollie's hosted payment pages have been optimized for devices of all common brands and sizes, including phones and tablets.”

   proof ↗⚑ flag

   Airwallex~partialclaimed6/10

   Docs confirm a single integration (Hosted Payment Page / Drop-in Element / Payment Links) that adapts fields per payment method/country and mentions 160+ local payment methods via invoicing, plus multi-currency pricing to unlock local methods, but no explicit evidence naming Apple Pay, Google Pay, bank redirects, or BNPL support. Missing for 10: explicit listing/documentation of specific wallets (Apple Pay/Google Pay) and BNPL providers, and independent confirmation these render correctly in a single checkout integration.

   • [claimed-docs] “Hosted Payment Page is a secure, pre-built payment page hosted by Airwallex that lets you accept multiple payment methods with a single inte…”
   • [claimed-docs] “Automatically adjusts input fields to collect information based on the payment method and country.”
   • [claimed-docs] “Generate invoices and digital payment links with over 160+ local payment methods”
   • [claimed-docs] “The Multi-Currency Pricing API (MCP API) enables you to display prices and enable payment in your shoppers' preferred currencies, while also…”
   • [claimed-docs] “Payment Links are the easiest way for you to accept payments online without a digital storefront.”

   proof ↗⚑ flag

Pci compliance

1. developerKeep my systems out of most of PCI DSS scope because card data is tokenized and never touches my servers

   weight 2 · round to Mollie
   Mollie✓fullclaimed8/10

   Mollie offers hosted checkout, Payment Links, and Mollie Components explicitly documented as 'fully PCI-DSS SAQ-A compliant', keeping card data off the merchant's own servers via tokenized/embedded fields or redirect, which minimizes PCI scope. missing for 10: no independent third-party audit or compliance certificate evidence, and no explicit statement of merchant SAQ-A eligibility requirements/limitations.

   • [claimed-docs] “Mollie JS is a set of Javascript APIs that allow you to add the fields needed for credit card holder data to your own checkout, in a way tha…”
   • [claimed-docs] “Three documented integration depths: hosted checkout (Mollie-hosted payment pages), Mollie Components (embeddable card components for PCI sc…”
   • [claimed-docs] “Mollie's hosted payment pages have been optimized for devices of all common brands and sizes, including phones and tablets.”
   • [claimed-docs] “Mollie provides a hosted checkout environment dubbed Mollie Checkout. These hosted payment pages allow your customer to select their payment…”

   proof ↗⚑ flag

   Airwallex~partialclaimed5/10

   Airwallex offers a Hosted Payment Page and Drop-in Elements that are pre-built, Airwallex-hosted card collection UIs implying card data doesn't touch the merchant's servers, which is the typical mechanism for reducing PCI scope. However, no evidence explicitly discusses PCI DSS compliance, SAQ scope reduction, or tokenization-for-compliance framing. missing for 10: explicit PCI DSS scope statements, tokenization/vaulting documentation, SAQ-A or compliance certification details, independent confirmation that card data never touches merchant servers.

   • [claimed-docs] “Hosted Payment Page is a secure, pre-built payment page hosted by Airwallex that lets you accept multiple payment methods with a single inte…”
   • [claimed-docs] “Automatically adjusts input fields to collect information based on the payment method and country.”
   • [claimed-docs] “Complete a minimal end-to-end online payment in the sandbox environment using Airwallex.js and Airwallex-hosted payment page.”

   proof ↗⚑ flag

Integration reliability

1. developerSafely retry any API request using idempotency keys so network failures never create duplicate charges

   weight 2 · round to Mollie
   Mollie✓fullclaimed9/10

   Mollie documents the Idempotency-Key header explicitly for safe retries and even calls out the exact danger scenarios (double charges on recurring payments/subscriptions, duplicate partial refunds) that it prevents. missing for 10: independent/hands-on developer confirmation of idempotency behavior in production beyond vendor docs.

   • [claimed-docs] “you can send a unique value with every API request via the Idempotency-Key header. If two requests come in with the same value, the second r…”
   • [claimed-docs] “Idempotent retries via a documented header: "you can send a unique value with every API request via the `Idempotency-Key` header. If two req…”
   • [claimed-docs] “In the Mollie API, these sorts of problems can be solved in two ways... you can actively i[dentify requests with an idempotency key]”

   proof ↗⚑ flag

   Airwallex—none0/10

   The evidence pack describes webhook delivery reliability (stable event IDs for webhook retries) but contains no documentation of idempotency keys for outbound API requests (e.g., payment creation) to prevent duplicate charges on retry. This is a distinct, applicable axis for a payments API but is unevidenced here.

   ⚑ flag

2. developerRely on signed webhook deliveries with automatic retries, event logs, and replay to keep my system consistent with payment state

   weight 3 · round to Airwallex
   Mollie~partialclaimed5/10

   Mollie documents signed webhooks via HMAC verification (X-Mollie-Signature) and a next-gen Webhook Events API that lets developers 'retroactively inspect past events' and retrieve detailed info per triggered event, giving an audit/event-log capability. However, there is no documented automatic retry mechanism for webhook delivery, and no explicit 'replay' feature to resend a webhook event to reprocess it — idempotency keys only cover client-side API request retries, not Mollie's own webhook delivery retries. missing for 10: documented automatic webhook delivery retry policy, explicit replay/resend capability for webhook events, independent/hands-on confirmation of retry behavior.

   • [claimed-docs] “To verify HMAC signature for a webhook, follow these steps: 1. Retrieve the signature from the request header (X-Mollie-Signature)...”
   • [claimed-docs] “To verify HMAC signature for a webhook, follow these steps: Retrieve the signature from the request header (X-Mollie-Signature) and obtain t…”
   • [claimed-docs] “Next-gen webhooks add a subscription model and an audit API: "Updated Webhooks API allowing you to permanently subscribe to specific event t…”
   • [claimed-docs] “New event types to offer a broader context for your business processes (e.g. payment creation, invoice creation, onboarding status changes e…”
   • [claimed-docs] “Idempotent retries via a documented header: "you can send a unique value with every API request via the `Idempotency-Key` header. If two req…”

   proof ↗⚑ flag

   Airwallex~partialclaimed6/10

   Airwallex's webhook docs describe reliability primitives that map to most of this story: a required 200 response for delivery confirmation, a stable event id explicitly for safe retry handling/deduplication, and a web app view to inspect delivery status and re-deliver events after downtime or debugging (covers automatic retries, event logs, and replay). However, none of the evidence explicitly documents cryptographic signature verification for webhook payloads. Missing for 10: explicit signed-webhook/signature-verification documentation, and independent/hands-on confirmation of retry behavior in practice.

   • [claimed-docs] “Webhooks with documented reliability semantics: "Your endpoint must respond with a 200 status code so that Airwallex can confirm delivery. E…”
   • [claimed-docs] “Webhooks enable Airwallex to send instant, real-time push notifications to your application when events occur in your Airwallex account.”

   proof ↗⚑ flag

Onboarding dx

1. developerIntegrate a working payment flow from the docs alone in under a day, with copy-paste examples in my language

   weight 2 · round to Airwallex
   Mollie~partialclaimed5/10

   Mollie's docs give a clear, well-structured path (hosted checkout, Payments API, webhooks, test mode, idempotency) that a developer could follow to build a working payment flow, and llms.txt/markdown mirrors make the docs easily consumable. However, the evidence pack never shows actual copy-paste code snippets in a specific programming language (e.g. PHP/Node/Python SDK examples) or confirms a 'under a day' end-to-end tutorial — only conceptual/API-reference descriptions are present. missing for 10: language-specific copy-paste code samples/SDK quickstarts, an explicit fast end-to-end tutorial timeline, independent developer corroboration of setup speed

   • [claimed-docs] “If, however, you are keen on building your own checkout experience, below we offer a way to implement it.”
   • [claimed-docs] “Mollie provides a hosted checkout environment dubbed Mollie Checkout. These hosted payment pages allow your customer to select their payment…”
   • [claimed-docs] “The Payments API is at the heart of the Mollie API. It allows you to create and manage payments.”
   • [claimed-docs] “Three documented integration depths: hosted checkout (Mollie-hosted payment pages), Mollie Components (embeddable card components for PCI sc…”
   • [claimed-docs] “Test mode is a first-class switch: "You can access the `test` mode of the Mollie API in two ways: by using the Test API key, or... by provid…”
   • [claimed-docs] “Idempotent retries via a documented header: "you can send a unique value with every API request via the `Idempotency-Key` header. If two req…”
   • [claimed-docs] “docs.mollie.com publishes a full llms.txt page index and documents the markdown mirror convention on every page: "Fetch the complete documen…”

   proof ↗⚑ flag

   Airwallex~partialclaimed6/10

   There is a clear quickstart doc ('Complete a minimal end-to-end online payment in the sandbox environment using Airwallex.js and Airwallex-hosted payment page') plus a self-serve sandbox and multiple integration options (Hosted Payment Page, Drop-in Element) with styling/config snippets, suggesting a fast path to a working payment flow. However, the evidence pack never shows actual copy-paste code samples in specific languages (e.g., Node, Python, PHP) or confirms multi-language SDK coverage, nor any independent developer report confirming a sub-day integration time. Missing for 10: concrete multi-language code snippets, language/SDK coverage, and independent hands-on confirmation of integration speed.

   • [claimed-docs] “Complete a minimal end-to-end online payment in the sandbox environment using Airwallex.js and Airwallex-hosted payment page.”
   • [claimed-docs] “Hosted Payment Page is a secure, pre-built payment page hosted by Airwallex that lets you accept multiple payment methods with a single inte…”
   • [claimed-docs] “Automatically adjusts input fields to collect information based on the payment method and country.”
   • [claimed-docs] “"Airwallex provides a sandbox environment, completely separate from the production environment, for testing your integration through simulat…”
   • [claimed-docs] “Pass appearance and layout in createElement(...). For examples and supported values, see Customize style and appearance”

   proof ↗⚑ flag

Sandbox fidelity

1. developerBuild and test the entire payment flow in a sandbox or test mode that mirrors production, with test cards for every scenario including declines and disputes

   weight 3 · round drawn
   Mollie~partialclaimed6/10

   Mollie documents a genuine test mode that isolates test data from production, replaces hosted checkout with a walkthrough screen, and exposes a changePaymentState URL to simulate refunds and chargebacks (mollie-supp-testing, mollie-docs-18). However, the evidence never mentions specific test card numbers or a documented list of decline/failure scenarios by card, which the story explicitly calls for. Missing for 10: documented test card numbers per scenario (success, decline, insufficient funds, etc.), and independent/hands-on confirmation that test mode fully mirrors all production payment method behaviors.

   • [claimed-docs] “Test mode is a first-class switch: "You can access the `test` mode of the Mollie API in two ways: by using the Test API key, or... by provid…”
   • [claimed-docs] “Any payments or other resources you create in test mode are completely isolated from your live mode data.”

   proof ↗⚑ flag

   Airwallex~partialclaimed6/10

   Airwallex documents a full sandbox environment mirroring production (all products except Connected Account APIs), simulation docs for payments/payouts/deposits/issuing/risk, and a quickstart for an end-to-end sandbox payment flow, plus dispute-handling docs. However, there is no explicit mention of a documented set of test card numbers covering specific decline reason codes or dispute-triggering scenarios. missing for 10: documented test card numbers/scenarios for specific decline codes, explicit dispute-simulation test cards, independent developer confirmation of sandbox fidelity to production.

   • [claimed-docs] “"Airwallex provides a sandbox environment, completely separate from the production environment, for testing your integration through simulat…”
   • [claimed-docs] “Complete a minimal end-to-end online payment in the sandbox environment using Airwallex.js and Airwallex-hosted payment page.”
   • [claimed-docs] “Airwallex will facilitate your dispute management step-by-step, but generally does not have influence over the outcome.”
   • [claimed-docs] “A second, integration-time MCP pair: "The Airwallex developer connectors connects AI coding agents — Cursor, Claude Code, Codex, and similar…”

   proof ↗⚑ flag

Ai disputes

1. ai-native userHave an agent handle a dispute end-to-end, retrieving it, assembling evidence, and submitting the response via the API

   weight 3 · round drawn
   Mollie—none0/10

   Mollie's Chargebacks API only supports retrieving chargeback details (mollie-docs-9); there is no documented capability for assembling evidence or submitting a dispute response via the API, and the MCP server's supported API list does not even include Chargebacks (mollie-supp-mcp-server). No evidence supports the 'submitting the response' half of this story.

   • [claimed-docs] “The Chargebacks API then allows you to retrieve details of the chargebacks that took place on your account.”
   • [claimed-docs] “The Mollie MCP server is hosted at a documented endpoint: "You can find Mollie MCP server at `https://mcp.mollie.com/mcp`, which acts as a p…”

   proof ↗⚑ flag

   Airwallex—none0/10

   Airwallex documents a general disputes process page (docs-26) but no API endpoints for retrieving disputes, assembling evidence, or submitting responses, and the AgentOS/CLI 'skills' list (contract-to-billing, beneficiary creation, card provisioning, cashflow management) never mentions disputes as a supported agent workflow. Missing for 10: dispute-retrieval API, evidence-assembly workflow, dispute-response submission API, and any AgentOS/CLI skill or MCP tool covering disputes end-to-end.

   • [claimed-docs] “Airwallex will facilitate your dispute management step-by-step, but generally does not have influence over the outcome.”
   • [claimed-docs] “"Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiari…”

   proof ↗⚑ flag

Disputes

1. finance-ops userRespond to a chargeback with structured evidence and track the dispute lifecycle to resolution

   weight 3 · round drawn
   Mollie~partialclaimed3/10

   Mollie's Chargebacks API only lets merchants retrieve details of chargebacks that occurred on their account (mollie-docs-9); there is no documented capability to submit structured evidence in response to a dispute or to track a dispute lifecycle through stages to resolution. Settlement reports and balances APIs (mollie-docs-10, mollie-docs-11) help reconcile chargeback deductions financially, but this is reconciliation, not dispute-response workflow. missing for 10: evidence-submission/response mechanism for chargebacks, dispute status/lifecycle states, resolution outcome tracking, any UI or API for contesting a chargeback.

   • [claimed-docs] “The Chargebacks API then allows you to retrieve details of the chargebacks that took place on your account.”
   • [claimed-docs] “Settlement Report gives you a complete breakdown of the data included in a specific payout... helping you reconcile your transactions.”
   • [claimed-docs] “The Balances API allows you to retrieve real-time as well as historical information about your Mollie balance.”

   proof ↗⚑ flag

   Airwallex~partialclaimed3/10

   Airwallex docs confirm a dispute-management feature exists ('Airwallex will facilitate your dispute management step-by-step, but generally does not have influence over the outcome'), implying some workflow for chargebacks, but there is no evidence of structured evidence submission templates, evidence checklists, or dispute lifecycle status tracking in the UI/API. Missing for 10: documentation of evidence upload/structuring, dispute status/lifecycle tracking (open/under review/won/lost), API or webhook events specifically for dispute state changes, and any independent confirmation of the workflow.

   • [claimed-docs] “Airwallex will facilitate your dispute management step-by-step, but generally does not have influence over the outcome.”

   proof ↗⚑ flag

Fraud prevention

1. finance-ops userScreen transactions with machine-learning fraud scores and write custom block, review, and allow rules

   weight 3 · round drawn
   Mollie—none0/10

   Evidence covers chargebacks retrieval, webhooks, idempotency, and testing, but there is no mention of ML-based fraud scoring or a rules engine for block/review/allow decisions on transactions.

   ⚑ flag

   Airwallex—none0/10

   The evidence pack covers payments, billing, transfers, AI/developer tooling, webhooks, and dispute facilitation, but contains no mention of ML-based fraud scoring or a rules engine for custom block/review/allow rules; only generic dispute-management language and a sandbox mention of 'risk' simulations without detail. This is a fair capability to expect from a payments platform, so absence of evidence yields 'none' rather than 'na'.

   • [claimed-docs] “Airwallex will facilitate your dispute management step-by-step, but generally does not have influence over the outcome.”
   • [claimed-docs] “"Airwallex provides a sandbox environment, completely separate from the production environment, for testing your integration through simulat…”

   proof ↗⚑ flag

Refunds

1. finance-ops userIssue full or partial refunds from both the dashboard and the API

   weight 3 · round to Mollie
   Mollie✓fullclaimed8/10

   Docs confirm refunds can be created via the API endpoint and manually via the Mollie Web app (dashboard), and the idempotency docs explicitly reference 'partial refunds' as a supported operation, confirming both full and partial refund support across both surfaces. Missing for 10: no dedicated Refunds API reference doc explicitly listing full vs partial refund parameters, and no independent/hands-on confirmation beyond first-party docs.

   • [claimed-docs] “you can also create refunds manually via the Mollie Web app.”
   • [claimed-docs] “Next to the API endpoint, you can also create refunds manually via the Mollie Web app.”
   • [claimed-docs] “Idempotent retries via a documented header: "you can send a unique value with every API request via the `Idempotency-Key` header. If two req…”

   proof ↗⚑ flag

   Airwallex~partialclaimed6/10

   Docs confirm refunds are a documented capability ('When a shopper returns goods or services, you can issue a refund to return their funds') and the CLI/API expose broad read/write access to Airwallex resources including presumably refunds, but no evidence explicitly confirms a dashboard refund UI or distinguishes full vs partial refund support at the API/dashboard level. Missing for 10: explicit documentation of partial refund amounts, dashboard UI screenshots/flow for issuing refunds, and independent/hands-on confirmation of both channels working.

   • [claimed-docs] “When a shopper returns goods or services, you can issue a refund to return their funds.”

   proof ↗⚑ flag

Multi currency

1. founderCharge customers in their local currencies and settle to my bank in mine with transparent FX handling

   weight 2 · round to Airwallex
   Mollie~partialclaimed5/10

   Mollie documents accepting payments in currencies beyond EUR via its v2 APIs [mollie-docs-12], and provides Settlement Reports and Balances API for reconciling payouts [mollie-docs-10, mollie-docs-27, mollie-docs-11, mollie-docs-28], which supports part of the founder's need. However, there is no evidence detailing FX conversion rates, markup/fee transparency, or explicit confirmation that funds settle to the merchant's bank account in their own currency after conversion. Missing for 10: explicit FX rate/markup disclosure, settlement-currency selection/conversion mechanics, and independent confirmation of how multi-currency payments reconcile to a single bank currency.

   • [claimed-docs] “Mollie enables you to accept payments in currencies beyond EUR through its v2 APIs, allowing international customers to transact in their pr…”
   • [claimed-docs] “Settlement Report gives you a complete breakdown of the data included in a specific payout... helping you reconcile your transactions.”
   • [claimed-docs] “Settlement Report gives you a complete breakdown of the data included in a specific payout. It shows all transactions, fees and deductions t…”
   • [claimed-docs] “The Balances API allows you to retrieve real-time as well as historical information about your Mollie balance.”
   • [claimed-docs] “The Balances API allows you to retrieve real-time as well as historical information about your Mollie balance. This may be useful to for exa…”

   proof ↗⚑ flag

   Airwallex✓fullclaimed8/10

   Airwallex directly supports charging customers via 160+ local payment methods and multi-currency pricing (accepting in local currencies), and its multi-currency Wallet enables like-for-like settlement without forced FX conversion, explicitly marketed as eliminating FX fees versus traditional gateways that force home-currency settlement. Transfers/payouts and invoicing further round out the collect-and-settle flow, backed by first-party docs. Missing for 10: independent/hands-on verification of actual FX rates charged and real-world transparency (e.g., third-party review of fee disclosure) beyond vendor documentation.

   • [claimed-docs] “Eliminates FX fees with like-for-like settlement: Unlike traditional gateways that settle global payments into your home currency, Airwallex…”
   • [claimed-docs] “The Multi-Currency Pricing API (MCP API) enables you to display prices and enable payment in your shoppers' preferred currencies, while also…”
   • [claimed-docs] “Generate invoices and digital payment links with over 160+ local payment methods”
   • [claimed-docs] “Airwallex Transfers allows you to move funds across the globe easily to your suppliers, employees, contractors and/or own bank accounts.”
   • [claimed-docs] “The Multi-Currency Pricing API (MCP API) enables you to display prices and enable payment in your shoppers' preferred currencies”

   proof ↗⚑ flag

Tax

1. finance-ops userCalculate and collect the correct sales tax, VAT, or GST on every transaction automatically

   weight 3 · round to Airwallex
   Mollie—none0/10

   Mollie is a payment processing platform (checkout, payments, subscriptions, payouts, connect/marketplace splits) with no evidence of tax/VAT/GST calculation, rate lookup, or automated tax collection features anywhere in the evidence pack.

   ⚑ flag

   Airwallex~partialclaimed6/10

   Airwallex's Merchant of Record add-on explicitly automates sales tax, VAT, and GST calculation and collection per sale, letting sellers avoid registering for tax in each market. However, it is documented as a beta feature limited to digital products only (physical goods unsupported), has restricted eligibility, and leaves refunds/disputes to the merchant — so it doesn't cover all transaction types a finance-ops user might need automated tax handling for. Missing for 10: general availability (non-beta) status, physical goods/product coverage, and independent/hands-on verification of tax accuracy across jurisdictions.

   • [claimed-docs] “Sell digital products globally without registering for tax in every market. With Airwallex Merchant of Record, Airwallex acts as the legal s…”
   • [claimed-docs] “Airwallex also documents a merchant-of-record add-on (beta): "With Airwallex Merchant of Record, Airwallex acts as the legal seller and mana…”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round drawn
   Mollie~partialclaimed7/10

   Mollie's API surface is extensive and mirrors most Dashboard functionality: payments, refunds (explicitly noted as available both via API and manually in the 'Mollie Web app'), subscriptions, balances, settlement reports, chargebacks, webhooks, and Connect split-payments/application-fees are all API-accessible. However, no evidence explicitly asserts full 1:1 API/UI parity across every dashboard feature (e.g., account settings, onboarding flows, reporting UI extras), and the MCP server itself only proxies a subset of APIs (missing Refunds, Chargebacks, Orders), leaving some UI-only gaps unconfirmed either way. Missing for 10: explicit parity statement, independent confirmation that every dashboard action has an API equivalent, and coverage of admin/config UI features not mentioned in docs.

   • [claimed-docs] “you can also create refunds manually via the Mollie Web app.”
   • [claimed-docs] “Next to the API endpoint, you can also create refunds manually via the Mollie Web app.”
   • [claimed-docs] “The Balances API allows you to retrieve real-time as well as historical information about your Mollie balance.”
   • [claimed-docs] “The Balances API allows you to retrieve real-time as well as historical information about your Mollie balance. This may be useful to for exa…”
   • [claimed-docs] “Settlement Report gives you a complete breakdown of the data included in a specific payout... helping you reconcile your transactions.”
   • [claimed-docs] “Settlement Report gives you a complete breakdown of the data included in a specific payout. It shows all transactions, fees and deductions t…”
   • [claimed-docs] “The Chargebacks API then allows you to retrieve details of the chargebacks that took place on your account.”
   • [claimed-docs] “Marketplace money movement is documented under Mollie Connect: "Split payments let marketplaces distribute funds across multiple sellers in …”
   • [claimed-docs] “Test mode is a first-class switch: "You can access the `test` mode of the Mollie API in two ways: by using the Test API key, or... by provid…”
   • [claimed-docs] “Four documented authentication methods — API keys ("default API access for a specific payment profile"), Advanced access tokens ("advanced A…”

   proof ↗⚑ flag

   Airwallex~partialclaimed7/10

   Airwallex documents an extensive API surface plus a CLI that 'exposes a broad slice of the Airwallex API as terminal commands' and an AgentOS/MCP toolkit letting agents read balances, create beneficiaries, issue cards, and run workflows — strong evidence that most UI actions have programmatic equivalents. However, AgentOS explicitly ships with 'no money-out actions by default' as a safety guardrail, and Connected Account APIs are excluded from sandbox, indicating some UI-capable actions are deliberately restricted or gated via role/OAuth permissions rather than fully mirrored in the API/agent tooling. Missing for 10: confirmation that all money-movement and account-management UI actions are reachable via API without special unlocking, and independent/hands-on verification that the CLI/MCP truly cover 100% of UI functionality.

   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”
   • [claimed-docs] “"Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiari…”
   • [claimed-docs] “The AgentOS MCP is a hosted remote server with documented safety defaults: "Airwallex AgentOS MCP lets agents read and write production Airw…”
   • [claimed-docs] “"Airwallex provides a sandbox environment, completely separate from the production environment, for testing your integration through simulat…”
   • [claimed-docs] “A scoped API key grants only the resource permissions you assign (Read or Write on specific APIs), instead of full account access.”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round drawn
   Mollie—none0/10

   Mollie's docs show only piecemeal transaction-reporting APIs (Settlement Report, Balances API) for reconciliation, not a comprehensive account data export or account-closure/portability feature; there's no evidence of a full data export in open formats or a documented way to close an account and take all data with you.

   • [claimed-docs] “Settlement Report gives you a complete breakdown of the data included in a specific payout... helping you reconcile your transactions.”
   • [claimed-docs] “The Balances API allows you to retrieve real-time as well as historical information about your Mollie balance.”
   • [claimed-docs] “Settlement Report gives you a complete breakdown of the data included in a specific payout. It shows all transactions, fees and deductions t…”
   • [claimed-docs] “The Balances API allows you to retrieve real-time as well as historical information about your Mollie balance. This may be useful to for exa…”

   proof ↗⚑ flag

   Airwallex—none0/10

   Airwallex is a financial platform (payments, treasury, billing) with an API/CLI/MCP for account operations, but there is no evidence of a bulk data export feature or open-format data portability that would let a user export all their account data and leave the platform. The APIs allow reading individual resources but no documented full-account export/migration tool is mentioned.

   ⚑ flag

Ai reconciliation

1. ai-native userHave an agent pull payout and balance-transaction data via the API and reconcile each bank deposit to its underlying charges

   weight 3 · round drawn
   Mollie~partialclaimed6/10

   Mollie documents a Balances API for real-time/historical balance data and a Settlement Report that breaks down transactions, fees, and deductions per payout for reconciliation, both accessible via API and exposed through the Mollie MCP server (Balances, Settlements listed as covered APIs). However, evidence doesn't show a documented API endpoint for retrieving the underlying settlement/payout line items programmatically beyond the Settlements API listing itself, nor concrete agent-driven examples of matching balance transactions to charges. missing for 10: explicit documented Settlements API line-item/transactions endpoint schema, worked example of an agent reconciling deposits to charges end-to-end, and independent/hands-on confirmation of this reconciliation workflow via API or MCP.

   • [claimed-docs] “Settlement Report gives you a complete breakdown of the data included in a specific payout... helping you reconcile your transactions.”
   • [claimed-docs] “The Balances API allows you to retrieve real-time as well as historical information about your Mollie balance.”
   • [claimed-docs] “Settlement Report gives you a complete breakdown of the data included in a specific payout. It shows all transactions, fees and deductions t…”
   • [claimed-docs] “The Balances API allows you to retrieve real-time as well as historical information about your Mollie balance. This may be useful to for exa…”
   • [claimed-docs] “The Mollie MCP server is hosted at a documented endpoint: "You can find Mollie MCP server at `https://mcp.mollie.com/mcp`, which acts as a p…”

   proof ↗⚑ flag

   Airwallex~partialclaimed6/10

   Airwallex documents agent-facing tooling (AgentOS, CLI, MCP server) that lets an agent read balances, build cashflow reports, and pull payout/transfer data programmatically, and the CLI/MCP explicitly support scripting/read access to production resources. However, there is no specific mention of a 'balance transaction' API endpoint or a documented reconciliation workflow matching bank deposits to underlying charges — the closest is generic 'cashflow reports' and 'Skills' bundles. Missing for 10: explicit balance-transactions API/reconciliation endpoint docs, a worked example of matching payouts to charges, and independent/hands-on evidence of this reconciliation working end-to-end.

   • [claimed-docs] “Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiarie…”
   • [claimed-docs] “Airwallex Transfers allows you to move funds across the globe easily to your suppliers, employees, contractors and/or own bank accounts.”
   • [claimed-docs] “The official Airwallex CLI "exposes a broad slice of the Airwallex API as terminal commands, so you can read and write your Airwallex resour…”
   • [claimed-docs] “The AgentOS MCP is a hosted remote server with documented safety defaults: "Airwallex AgentOS MCP lets agents read and write production Airw…”
   • [claimed-docs] “"Airwallex AgentOS is a toolkit for AI agents that need to act on your production Airwallex account — reading balances, creating beneficiari…”

   proof ↗⚑ flag

Payouts

1. finance-ops userControl the payout schedule and see exactly which charges, fees, and refunds make up each payout

   weight 2 · round to Mollie
   Mollie~partialclaimed6/10

   Mollie's Settlement Report gives a full breakdown of transactions, fees, and deductions per payout, and the Balances API exposes real-time/historical balance data useful for reconciliation, directly supporting the 'see what makes up each payout' half of the story. However, there is no evidence of finance-ops controls to set or change the payout schedule (e.g., daily/weekly/custom payout frequency settings) — the docs only describe reporting/retrieval APIs, not schedule configuration. missing for 10: documented payout schedule/frequency controls, UI or API to set payout timing, confirmation that fees/refunds/chargebacks are itemized per payout beyond settlement report summary.

   • [claimed-docs] “Settlement Report gives you a complete breakdown of the data included in a specific payout... helping you reconcile your transactions.”
   • [claimed-docs] “Settlement Report gives you a complete breakdown of the data included in a specific payout. It shows all transactions, fees and deductions t…”
   • [claimed-docs] “The Balances API allows you to retrieve real-time as well as historical information about your Mollie balance.”
   • [claimed-docs] “The Balances API allows you to retrieve real-time as well as historical information about your Mollie balance. This may be useful to for exa…”

   proof ↗⚑ flag

   Airwallex—none0/10

   The evidence pack covers Airwallex's transfers, billing, invoicing, and webhook capabilities but contains no mention of configurable payout schedules or itemized payout reports that break down constituent charges, fees, and refunds — a distinct reconciliation feature payment platforms typically document separately.

   ⚑ flag

Reconciliation

1. finance-ops userReconcile settlements to bank deposits with itemized reports covering fees, refunds, and chargebacks

   weight 3 · round to Mollie
   Mollie~partialclaimed7/10

   Mollie's Settlement Report explicitly gives a breakdown of a payout showing 'all transactions, fees and deductions,' and the Balances API supports bookkeeping reconciliation, while separate Chargebacks and Refunds APIs let finance-ops retrieve those items — together covering the core of the story. However, no evidence shows a single itemized report combining fees, refunds, and chargebacks in one reconciliation view, nor any bank-deposit matching feature or independent/hands-on validation of the reconciliation workflow. Missing for 10: unified itemized settlement report explicitly breaking out refunds/chargebacks line-by-line, bank-deposit matching capability, and independent user corroboration.

   • [claimed-docs] “Settlement Report gives you a complete breakdown of the data included in a specific payout... helping you reconcile your transactions.”
   • [claimed-docs] “Settlement Report gives you a complete breakdown of the data included in a specific payout. It shows all transactions, fees and deductions t…”
   • [claimed-docs] “The Balances API allows you to retrieve real-time as well as historical information about your Mollie balance.”
   • [claimed-docs] “The Balances API allows you to retrieve real-time as well as historical information about your Mollie balance. This may be useful to for exa…”
   • [claimed-docs] “The Chargebacks API then allows you to retrieve details of the chargebacks that took place on your account.”
   • [claimed-docs] “you can also create refunds manually via the Mollie Web app.”

   proof ↗⚑ flag

   Airwallex—none0/10

   Evidence covers payments, payouts/transfers, refunds, disputes, webhooks, billing/invoicing, and treasury, but there is no mention of a settlement-to-bank-deposit reconciliation report, itemized fee/refund/chargeback breakdowns tied to deposits, or any reconciliation-specific reporting feature for finance-ops. Refunds and disputes are documented in isolation but not connected to a reconciliation/report workflow.

   • [claimed-docs] “When a shopper returns goods or services, you can issue a refund to return their funds.”
   • [claimed-docs] “Airwallex will facilitate your dispute management step-by-step, but generally does not have influence over the outcome.”
   • [claimed-docs] “Airwallex Transfers allows you to move funds across the globe easily to your suppliers, employees, contractors and/or own bank accounts.”
   • [claimed-docs] “Eliminates FX fees with like-for-like settlement: Unlike traditional gateways that settle global payments into your home currency, Airwallex…”

   proof ↗⚑ flag

Marketplace

1. developerBuild a marketplace or platform that onboards sellers, splits payments between parties, and pays out to each seller

   weight 2 · round drawn
   Mollie✓fullclaimed8/10

   Mollie Connect explicitly supports onboarding connected merchants, escrow-like holding of funds, split payments to multiple sellers, and application fees/commission retention for the platform, backed by documented onboarding, reporting, and payout mechanisms (settlement reports, balances API). missing for 10: independent/hands-on developer case studies building a full marketplace end-to-end, and more detail on seller onboarding KYC flow specifics beyond doc mentions.

   • [claimed-docs] “Mollie Connect lets software platforms and marketplaces offer payment and money management capabilities to their merchants under their own b…”
   • [claimed-docs] “Split payments let marketplaces distribute funds across multiple sellers in a single transaction.”
   • [claimed-docs] “Application Fees allow your platform to collect a fee on every payment you process on behalf of a connected account.”
   • [claimed-docs] “Marketplace money movement is documented under Mollie Connect: "Split payments let marketplaces distribute funds across multiple sellers in …”
   • [claimed-docs] “Settlement Report gives you a complete breakdown of the data included in a specific payout. It shows all transactions, fees and deductions t…”
   • [claimed-docs] “The Balances API allows you to retrieve real-time as well as historical information about your Mollie balance. This may be useful to for exa…”
   • [claimed-docs] “Application Fees allow your platform to collect a fee on every payment you process on behalf of a connected account. You define the amount, …”

   proof ↗⚑ flag

   Airwallex✓fullclaimed8/10

   Airwallex explicitly documents programmatic creation of connected accounts for businesses/individuals with financial capabilities (marketplace onboarding), plus Transfers/payouts to move funds to suppliers/contractors, and multi-currency wallet settlement — the core building blocks for onboarding sellers and paying them out. Payment splitting isn't explicitly named as a feature but is a natural extension of connected accounts + transfers, and sandbox/webhooks support building and testing such flows end-to-end. Missing for 10: explicit documentation of a 'split payment' or marketplace-specific API/feature, and independent case studies of marketplaces built on Airwallex.

   • [claimed-docs] “Programmatically create connected accounts for businesses and individuals, and enable them with rich financial capabilities.”
   • [claimed-docs] “Airwallex Transfers allows you to move funds across the globe easily to your suppliers, employees, contractors and/or own bank accounts.”
   • [claimed-docs] “Eliminates FX fees with like-for-like settlement: Unlike traditional gateways that settle global payments into your home currency, Airwallex…”
   • [claimed-docs] “Webhooks enable Airwallex to send instant, real-time push notifications to your application when events occur in your Airwallex account.”
   • [claimed-docs] “"Airwallex provides a sandbox environment, completely separate from the production environment, for testing your integration through simulat…”

   proof ↗⚑ flag

1. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Mollie—none0/10

   Mollie is a payments API/platform; no evidence in the pack addresses data retention policies, data deletion controls, or export/erasure mechanisms for AI-native users. The evidence covers payments, checkout, webhooks, Connect, and MCP server capabilities but nothing about privacy/data lifecycle controls.

   ⚑ flag

   Airwallex—none0/10

   Airwallex's evidence pack covers API scoping, sandbox environments, MCP/CLI tooling, and payment features, but nowhere addresses data retention policies or user-initiated data deletion controls (e.g., GDPR/CCPA-style deletion requests, retention period configuration). This is a fair axis for a fintech handling AI-agent data, but no capability is documented.

   ⚑ flag