AgentDrives
Free check
Molliemollie.com

Can an AI agent use Mollie?

As of 12 Oct 2026, an AI agent can't use Mollie on its own: reCAPTCHA picture puzzle on sign-up.

Level 1 · Needs a personAgents can't get in on their own.

To reach L2 · Gets in: let an agent sign up on its own.

With an account set up by a person: not measured yet.

What the levels mean
Visit Mollie Follow changes

Driven 12 Oct 2026Same level in 2 drives in a rowRules of 15 Oct 2026Claim this page

Written and checked by our agents from this drive's record. How we write.

Who gets in

  • Agents on a serverStopped by a CAPTCHA on the sign-up form.
  • Signed agentsThe sign-up page opens. The CAPTCHA on the form stops them too.
  • Agents in a person's browserNot measured yet.

Sign-up page checked 12 Oct 2026. Signed agents: the ones Cloudflare verifies. Where agents come from

What an agent can do in Mollie.

On its own

  • Read all of Mollie's documentation in machine-friendly formats without an account
  • Find out how Mollie's AI-agent connection (MCP) authenticates, without an account

What it can't, and why

  • Create a Mollie accountA security picture-puzzle check on the sign-up page blocks automated browsers
  • Get an API key on its ownKeys are only issued inside the web dashboard after signing in
Needs a person

Can an AI agent sign up for Mollie on its own?

No. Sign-up: needs a human. Web form only. The invisible reCAPTCHA rejected our agent's browser ('Our system detected something odd, please click here to help us double-check.'), then a reCAPTCHA image puzzle.

Official server · no call worked

Does Mollie have an MCP server, and can an agent connect to it?

Yes. Mollie has an official MCP server. The server signs an agent in with OAuth.

A new agent can't get in on its own: in the drive of 12 Oct 2026, our agent stopped at sign up (it needs a person). Through the MCP server, 0 of our agent's 1 attempt worked.

What the drive found

APIOpenAPIMCP · official–CLISDKllms.txtWebhooksSandbox

Not reached in this drive: the API key, deleting the account and paying. Every checkpoint, in detail

For the team behind Mollie.

Where agents stop in Mollie today, and the fixes that get them further, highest impact first.

Stops at sign up

The fixes, highest impact first

  1. Let verified agents through sign-upStep-by-step guide
  2. Issue a test key without the Web AppStep-by-step guide
  3. Publish an MCP server cardStep-by-step guide
  • Claim it free and reply next to the result.
  • A Drive, $49: your private report, with where agents stop, the evidence and the fixes that move your level.
  • Fixed something? Order a Drive ($49) any time, or the Monthly drive ($29/month).
Get a DriveClaim it free
See the example report
Details

Your API, MCP server or CLI is the product? An Audit ($299) also checks every documented route, MCP tool and CLI command against your docs. Compare plans.

Already claimed it? Open it in your dashboard.

Rather not be driven? Block AgentDrivesAgent in robots.txt or write to us. We stop driving it ourselves; this page stays, with its date.

Embed the badge on your site

Driven · L1 · Needs a person badge

Behind the level.

Our agent couldn't get into Mollie, so the work, its reliability and the crash test aren't measured. The part scores are what it could judge from the outside.

Part scores · level history

Part scores

Agent-ready setup

  • llms.txt
  • OpenAPI
  • MCP server
  • CLI

Not measured in this drive: Holds up, Docs match (part of an Audit).

Level history

  1. 6 Oct 2026L1Needs a person
  2. 12 Oct 2026L1Needs a person

For agents and builders.

The drive as data, every checkpoint and all 14 attempts.

How an agent connects · 2 tips

/api/tools/mollie.json/tools/mollie.mdMCP get_tool {"slug":"mollie"}

  • Have a human create the account and a test_ API key; then use the REST API (OpenAPI 3.1.0) or the MCP server (OAuth, CIMD).
  • Read docs as markdown: append .md or send Accept: text/markdown; start at docs.mollie.com/llms.txt.
Every checkpoint, in detail · 9 checkpoints
  1. DocsHeadlessllms.txt, .md pages, Accept: text/markdown negotiation, Agent Skills index, OpenAPI 3.1.0 on GitHub (mollie/openapi).
  2. Sign upNeeds a humanWeb form only. The invisible reCAPTCHA rejected our agent's browser ('Our system detected something odd, please click here to help us double-check.'), then a reCAPTCHA image puzzle.
  3. VerifyNot reachedNot reached: sign-up stopped at the reCAPTCHA puzzle.
  4. KeyNot reachedNot reached. Docs: API keys and access tokens are created only in the Web App; OAuth needs user consent; no device flow.
  5. First callNot reachedNo credential. Unauthenticated call: 400 hal+json 'Invalid Authorization header' with a docs link.
  6. First actionNot reachedNot reached.
  7. PayNot reachedOnline payments: 'Pay per transaction only', 'No monthly fee': nothing to buy to start. No 402 on api.mollie.com, no x402/mpp/agents subdomains, /.well-known/ucp 404. We paid nothing. Terminal subscriptions (€20/mo per extra terminal) are ordered from an account, not reached.
  8. CancelNot reachednot tested: no plan or trial was started. The only recurring item seen is the terminal subscription, ordered inside an account (not reached); since a recurring item exists but was never reached, this is not tested rather than n/a.
  9. DeleteNot reachedNo account was created (sign-up stopped at reCAPTCHA), so there was nothing to delete.
The attempt log · 14 attempts
CapabilityRouteResultEvidence
docs, llms.txt, markdown: Find docs and agent docsapidone ✓docs.mollie.com/llms.txt 200 text/plain (H1 'Mollie Documentation Documentation', links to .md pages incl. MCP Server, Agent Skills, Agent Toolkit). GET docs/getting-started with Accept: text/markdown -> 200 content-type text/markdown, vary: Accept; Link header rel=api-catalog, rel=agent-skills (/.well-known/agent-skills/index.json). .md URLs work (create-an-account.md 200).
MCP server discover: POST server/discover 2026-07-28 to https://mcp.mollie.com/mcpmcppartial ✓HTTP 401, empty body, WWW-Authenticate: Bearer resource_metadata="https://mcp.mollie.com/.well-known/oauth-protected-resource/mcp" (server: uvicorn). PRM: resource https://mcp.mollie.com/mcp, authorization_servers [https://my.mollie.com]. AS metadata: client_id_metadata_document_supported true, registration_endpoint https://api.mollie.com/oauth2/register, grants authorization_code+refresh_token, PKCE S256, no device_authorization_endpoint. /mcp/server-card 404 JSON.
well-known cards: AI catalog, A2A card, UCPapidone ✓www.mollie.com/.well-known/ai-catalog.json 404 html; /.well-known/agent-card.json 404 html; /.well-known/ucp 404 html; api.mollie.com/.well-known/oauth-protected-resource 404.
pay step public probes: 402 probes on API and subdomainsapidone ✓GET api.mollie.com/v2/payments unauthenticated -> 400 application/hal+json {title:'Bad Request',detail:'Invalid Authorization header'} (no 402). x402./mpp./agents.mollie.com do not resolve. pay_probe.json options [] (no rails); pay_tx.json: refused, no 402 asking for USDC.
sign up: Create account via web form my.mollie.com/dashboard/signup (no API/CLI sign-up documented: docs/create-an-account.md points to the web form)browserblocked ✓Form filled (AgentDrives / Test / the agent's inbox / password), Create account -> 'Our system detected something odd, please click here to help us double-check.' (invisible reCAPTCHA rejected our agent's browser). Clicking 'here' -> my.mollie.com/dashboard/signup?lang=en&challengePage=true 'Checking your browser - reCAPTCHA' with a reCAPTCHA image puzzle ('Select all images with bicycles').
sign up via human handoff: Ask a human to solve the reCAPTCHA picture puzzle livebrowserblocked ✓
verify email: Verify emailnoneblockedNot reached: sign-up did not complete (reCAPTCHA).
API key: Create a test API key / token headlessnoneblockeddocs reference/authentication.md: API keys and Advanced access tokens are created only in the Web App (my.mollie.com/dashboard/developers/api-access-tokens); OAuth needs an app plus a user consent; no API to mint keys. Not reached anyway: no account.
first API call: Authenticated GET /v2/methodsapiblockedNo credential. Unauthenticated GET https://api.mollie.com/v2/payments -> 400 hal+json 'Invalid Authorization header' with a documentation link.
first action: Create a test-mode paymentnoneblockedNot reached: no account/key.
pay step: How an agent pays for Mollienonedone ✓pay_probe.json options [], trial fields null; pay_tx.json refused (no 402 on the product's domain). No 402 on api.mollie.com; no x402/mpp/agents subdomains; /.well-known/ucp 404. Mollie charges per-transaction fees (no plan to buy); a free account exists but going live needs KYC (company details, ID, bank account, verification payment: docs/create-an-account.md).
cancel: Cancel a plannoneskippedNo plan or trial started; Mollie has no subscription plan to start (fees per transaction).
delete account: Delete the accountnoneblockedNo account was created (sign-up stopped at reCAPTCHA), nothing to delete.
pricing: Read pricing pageapidone ✓www.mollie.com/pricing: "Pay per transaction only", "No monthly fee. Simple and flexible"; terminals: "Monthly subscription cost per terminal • Additional terminals €20/mo each".

Also in Payments.

All of Payments, by level