# AX Check: mollie.com Checked 2026-09-29. Mollie's docs and pricing are fully readable without logging in. Setup guide, API reference, MCP server and Agent Skills are all directly reachable, and pricing tables list exact fees like 1.80%+€0.25 per card payment. ## Onboarding needs a login ## Coding sessions Two of three independent agent sessions completed and both reported concrete Mollie pricing (around 1.80%+€0.25 for cards) sourced straight from the pricing page, noting rates vary by region and method. The third session did not complete. ### DeepSeek V4.1 Flash [View public run](https://agents.withgauge.com/p/runs/4b0febb2-f7fb-4d23-9a7b-c69f31ee235b) · [Read transcript](https://www.ax-check.com/mollie.com/sessions/deepseek.json) Final output gives concrete Mollie pricing (1.80%+€0.25 EEA consumer cards, etc.) explicitly sourced from mollie.com/pricing and flagged as 'regional/locale-dependent, shown for EU/EEA in EUR'. #### End-to-end onboarding - **Onboarding needs a login**: The agent never obtained a real Mollie API key. It checked the environment for MOLLIE_API_KEY, confirmed none was set, and explicitly noted that creating one requires interactive Mollie signup/KYC it cannot do itself. Every 'successful' call in the session used a fake placeholder key (test_not_a_real_key) that only proved the request reached Mollie and returned an auth-rejection error, not a real authenticated operation like creating a payment. Event 25: ```text MOLLIE_API_KEY= MOLLIE_KEY= no mollie env vars ``` Event 71: ```text ApiError: request to https://api.mollie.com/v2/payments failed, reason: unable to verify the first certificate ``` Event 115: ```text No API key available. The environment has no `MOLLIE_API_KEY`, and getting one requires an interactive Mollie signup/KYC that I can't perform. So I could not create a live/test payment ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No Mollie API key available in the sandbox**: The environment has no MOLLIE_API_KEY or similar credential, and obtaining one requires an interactive Mollie account signup that the agent cannot complete on its own. This is a missing-credentials limitation of the test setup, not a product defect, and it prevented the agent from actually creating a live/test payment. Event 25: ```text MOLLIE_API_KEY= MOLLIE_KEY= no mollie env vars ``` Event 115: ```text No API key available. The environment has no `MOLLIE_API_KEY`, and getting one requires an interactive Mollie signup/KYC that I can't perform. ``` - **SDK's bundled CA certificates reject the sandbox's proxy TLS**: The official @mollie/api-client SDK pins its own Mozilla CA bundle inside an https.Agent, which does not include the sandbox's gateway/proxy CA, so any SDK call fails with 'unable to verify the first certificate' even though plain fetch() to the same endpoint succeeds through the sandbox proxy. This is an artifact of the test sandbox's network interception, not a Mollie product issue; the agent confirmed this by disabling TLS verification and getting the expected Mollie auth-error response. Event 71: ```text ApiError: request to https://api.mollie.com/v2/payments failed, reason: unable to verify the first certificate ``` Event 66: ```text OK {"_links":{"documentation":{"type":"text/html","href":"https://docs.mollie.com/r ``` Event 99: ```text ApiError: Invalid Authorization header ``` #### Suggested Changes - **Document the SDK's pinned CA bundle behavior**: In the @mollie/api-client README or docs, note that the Node SDK constructs its own https.Agent with a bundled Mozilla CA list (visible at dist/mollie.cjs.js around the NetworkClient constructor, 'const agent = new https.Agent({ ca: caCertificates })'), which can break in environments with corporate proxies or custom CAs that plain fetch would otherwise trust. Verify by running the SDK behind a MITM/corporate proxy and confirming the documented workaround (e.g. an option to supply a custom CA or disable the pinned bundle) resolves the 'unable to verify the first certificate' error. Event 81: ```text const agent = new https.Agent({ ca: caCertificates }); ``` Event 71: ```text ApiError: request to https://api.mollie.com/v2/payments failed, reason: unable to verify the first certificate ``` ### Kimi K3 [View public run](https://agents.withgauge.com/p/runs/b9b0fcf6-9725-4f6a-837f-fc9d2da59064) · [Read transcript](https://www.ax-check.com/mollie.com/sessions/kimi.json) Final output gives pricing (no setup fee, ~1.8%+€0.25 cards, ~€0.29 iDEAL) and flags assumptions explicitly: 'Rates vary by payment method and region... my figures may be stale' pointing to mollie.com/pricing. #### End-to-end onboarding - **Onboarding needs a login**: Agent found no Mollie API key in the sandbox, could not self-provision an account/API key, and stopped after building the example script. It never obtained real credentials or made an authenticated API call to Mollie; the script exits at the auth-check before any network request. Event 4: ```text env | grep -i mollie; ls /sandbox/repo; node --version 2>/dev/null; npm --version 2>/dev/null ``` Event 20: ```text Set MOLLIE_API_KEY (a test_ key from the Mollie dashboard) and re-run. exit: 1 ``` Event 22: ```text Mollie's API requires an API key, and there is **no unauthenticated developer workflow** — every endpoint needs a key from a Mollie account dashboard. No credentials exist in this environment, and I can't sign up for an account myself. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No Mollie API key available in the sandbox**: The environment had no Mollie credentials, and the agent has no way to self-serve account signup or key generation (that requires a human to visit the Mollie dashboard). This is a normal authentication requirement of the product, not a defect — Mollie's API legitimately requires an account-issued key for every call. The agent correctly identified this, built a runnable script, and stopped rather than faking success. Event 7: ```text No credentials are present, but Node 22 is available. I'll set up a minimal example with the official SDK. ``` Event 22: ```text No credentials exist in this environment, and I can't sign up for an account myself. ``` #### Suggested Changes None identified in this transcript. ### Qwen 3.8 Max [View public run](https://agents.withgauge.com/p/runs/2c6760ab-5209-4155-911c-a3bb9db03458) · [Read transcript](https://www.ax-check.com/mollie.com/sessions/qwen.json) #### End-to-end onboarding - **End-to-end onboarding not demonstrated**: No Mollie API credentials were ever obtained inside the session. The agent only found a generic PI_GATEWAY_API_KEY unrelated to Mollie, then explicitly built the example around a placeholder/test key the user must supply from the Mollie dashboard. The smoke test used a syntactically fake key by design and failed on a TLS certificate error before ever reaching an authentication check, so no authenticated Mollie operation was demonstrated. Event 6: ```text PI_GATEWAY_API_KEY= ``` Event 101: ```text message request to https://api.mollie.com/v2/payments failed, reason: unable to verify the first certificate FAIL: rejected for a non-auth reason - check the code. ``` Event 100: ```text Mollie API error: MOLLIE_API_KEY is not set. Run: cp .env.example .env and paste a test key from https://dashboard.mollie.com/account/api-keys (Test mode). ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No real Mollie API key available in the sandbox**: The environment only exposed an internal gateway key, not a Mollie credential. The agent correctly required the human to paste a real test_ key into .env, which was never supplied, so create-payment.js failed with a clear 'not set' error. This is a session/credential limitation, not a product defect — Mollie normally expects a human to copy a key from its dashboard. Event 100: ```text Mollie API error: MOLLIE_API_KEY is not set. Run: cp .env.example .env and paste a test key from https://dashboard.mollie.com/account/api-keys (Test mode). ``` - **Smoke test failed on TLS certificate verification, not the intended auth check**: scripts/smoke.js was designed to hit the Mollie API with a fake key and expect a 401/authorization error, proving the request path works. Instead it failed earlier with an 'unable to verify the first certificate' TLS error via the SDK's HTTP client, even though a raw curl and a plain Node https.get to the same URL had succeeded earlier in the session. This points to the bundled SDK/its HTTP layer not picking up the sandbox's custom CA bundle (NODE_EXTRA_CA_CERTS), an environment/agent-tooling interaction issue rather than a Mollie API defect. Event 101: ```text message request to https://api.mollie.com/v2/payments failed, reason: unable to verify the first certificate FAIL: rejected for a non-auth reason - check the code. ``` Event 105: ```text NODE_EXTRA_CA_CERTS=/usr/local/share/ca-certificates/alg-gateway.crt ``` #### Suggested Changes - **Document the SDK's HTTP client CA-bundle behavior for sandboxed/proxied environments**: The @mollie/api-client smoke test failed with 'unable to verify the first certificate' even though NODE_EXTRA_CA_CERTS was set and plain curl/https.get to the same endpoint succeeded, suggesting the SDK's internal request layer does not respect standard Node CA environment variables the same way. Add a troubleshooting note in the SDK README or docs about configuring custom CA bundles/corporate proxies for the client, and verify by rerunning a create-payment call in an environment with a custom CA bundle after the fix. Event 101: ```text request to https://api.mollie.com/v2/payments failed, reason: unable to verify the first certificate ``` Event 105: ```text node fetch ok 400 ``` ### Task given to each agent Help me build a simple example using Mollie. Tell me how pricing works, and briefly tell me whether this product will be easy for you to manage. Let me know if you get blocked. If this product has no developer workflow you can act on, say so plainly and stop. Stay light: use the hosted product through its SDK or API. Do not start local service stacks or wait for long-running commands; if the quickstart requires either, say so plainly and stop. No product credentials were supplied and no purchases were authorized. ## Score: A · 100/100 (provisional) Grades come from completed site checks. Coding sessions and skipped checks do not affect the score. ### Clarity - **Pass** — Homepage answers Markdown requests ```text Homepage returned text/markdown (2269 tokens) for a Markdown Accept header. ``` - **Pass** — llms.txt provides an actionable documentation index ```text llms.txt links docs, developer portal, MCP server, integrations and pricing. ``` - **Pass** — llms.txt provides navigation guidance ```text llms.txt documents URL structure, regional prefixes, sitemaps and crawling guidance. ``` - **Pass** — llms.txt mentions offered API, MCP, and skills ```text llms.txt covers API docs, MCP server endpoint and Agent Skills. ``` - **Pass** — A compact guide representation exists ```text Homepage served text/markdown (2269 tokens) and docs pages offer .md versions. ``` - **Pass** — A focused guide is directly retrievable ```text docs.mollie.com/docs/getting-started.md returns a focused Markdown setup guide. ``` - **Pass** — Equivalent instructions fit a token budget ```text Markdown guide measured 1107 tokens, well under the 8000-token budget. ``` - **Pass** — Product-docs links survive format changes ```text Homepage Markdown retains docs, pricing, integrations and developer links. ``` - **Pass** — The compact guide is independently actionable ```text Getting-started page offers concrete paths: prebuilt integrations, libraries, API reference, testing, and an Accepting payments guide. ``` - **Pass** — Install and next-step links resolve ```text Fetched install/next-step links resolve: signup, getting-started, MCP server, agent skills, and libraries pages all returned 200. ``` ### Onboarding - **Pass** — Docs lead to a relevant quickstart ```text Getting-started page links to Accepting payments guide and prebuilt integrations as concrete first steps. ``` - **Skipped** — Installation commands are extractable ```text Fetched pages describe libraries and integrations but no extractable install commands. ``` - **Skipped** — Code examples are available without interaction ```text No code examples appear in the fetched getting-started or integration pages. ``` - **Pass** — Prerequisites and auth boundaries are explicit ```text MCP server requires Advanced access token with profile.read scope; account creation documented. ``` ### Pricing - **Pass** — Pricing is readable without interaction ```text Pricing page renders full fee tables as static Markdown with no interaction required. ``` - **Pass** — Prices are stated, not gated ```text Concrete rates stated: cards 1.80% + €0.25, SEPA €0.35, terminals €95–€350. ``` - **Pass** — Pricing units and limits are explicit ```text Units explicit: percentages plus fixed euro fees, monthly terminal fees, payout thresholds. ``` - **Pass** — Agents identify pricing and its assumptions ```text 2 of 3 sessions were judged on pricing; 0 fell short. DeepSeek V4.1 Flash: Final output gives concrete Mollie pricing (1.80%+€0.25 EEA consumer cards, etc.) explicitly sourced from mollie.com/pricing and flagged as 'regional/locale-dependent, shown for EU/EEA in EUR'. Kimi K3: Final output gives pricing (no setup fee, ~1.8%+€0.25 cards, ~€0.29 iDEAL) and flags assumptions explicitly: 'Rates vary by payment method and region... my figures may be stale' pointing to mollie.com/pricing. This behavioural item does not affect the fast grade. ``` ### Activation - **Pass** — An API reference or OpenAPI spec is reachable ```text API reference index and OpenAPI endpoints listed at docs.mollie.com/reference/llms.txt. ``` - **Pass** — An MCP server is documented and well-formed ```text MCP server documented at mcp.mollie.com/mcp with OAuth auth, tools, and client setup. ``` - **Skipped** — A CLI install path is documented ```text No CLI install path documented; only npx mcp-remote proxy for MCP clients. ``` - **Skipped** — SDK packages resolve on their registries ```text Libraries page referenced but no registry lookup result supplied for any SDK package. ``` - **Pass** — Agent skills are published ```text Mollie Agent Skills documented with install commands for Claude Code, Cursor, Gemini CLI. ``` [Full report data](https://www.ax-check.com/mollie.com/report.json)