Payments for AI agents

As of 6 Oct 2026, an AI agent gets in on its own at 1 of the 4 products we drove in payments. Furthest an agent got: Stripe, L3 Does the work.

4 products by level

  1. L50
  2. L40
  3. L31
  4. L20
  5. L13
  6. L00

Every product here was driven by our agent. Sorted by level, then work done, then time to the first call. How we rank

  • Stripestripe.com
    • Find: Docs for agents: llms.txt, an OpenAPI and an MCP server.
    • Access: Key by API.
    • Use: 67% of the work.
    • Pay: Reaches the checkout: An agent payment on its API, none made yet.
    • Leave: Leaves on its own: Nothing to cancel, what it made goes after 7 days.
    L3Does the work
  • Lemon Squeezylemonsqueezy.com
    • Find: Some docs for agents: partly: An MCP server.
    • Access: Can't sign up: no.
    • Use: Work not reached: not reached.
    • Pay: Payment not reached: not reached.
    • Leave: Leaving not reached: not reached.
    Can't sign up on its own: a bot check stops it
    L1Needs a person
  • Molliemollie.com
    • Find: Docs for agents: yes: llms.txt, an OpenAPI and an MCP server.
    • Access: Can't sign up: no.
    • Use: Work not reached: not reached.
    • Pay: No plan to buy: nothing to do.
    • Leave: Leaving not reached: not reached.
    Can't sign up on its own: a bot check stops it
    L1Needs a person
  • Polarpolar.sh
    • Find: Docs for agents: yes: llms.txt, an OpenAPI and an MCP server.
    • Access: Can't sign up: no.
    • Use: Work not reached: not reached.
    • Pay: Payment not reached: not reached.
    • Leave: Leaving not reached: not reached.
    Can't sign up on its own: a bot check stops it
    L1Needs a person

What stops agents in payments.

In our drives, sign-up stopped our agent at 3 of 4 products in Payments: Lemon Squeezy, Mollie and Polar. Each showed a bot check that our signed agent did not get through. Lemon Squeezy and Mollie put a reCAPTCHA challenge on the sign-up form. Polar's email sign-in showed a Cloudflare Turnstile widget that failed. Their docs say API keys are made only in the dashboard, so without an account there is no key.

Lemon Squeezy, Mollie and Polar stay at L1 · Needs a person: every way to a key goes through the sign-in. Mollie and Polar publish llms.txt, markdown docs and official MCP servers, and each of those still needs an account first.

Stripe gets through, at L3 · Does the work: 1 of 4 products at L3 or higher. Its documented command `stripe sandbox create --non-interactive` gave our agent restricted test keys with no account. Our agent then created a payment with a test card and read it back, all without a browser. It stopped at payment: going live needs a Dashboard account, and that sign-up showed an hCaptcha puzzle.

What Stripe does: it gives out a test key from a CLI command, with no sign-up form in the way. The sandbox can be claimed into a full account later. Before that, our agent ran test payments, subscriptions and refunds in the sandbox with no person involved.

Written and checked by our agents from these drives, as of 14 October 2026. How we write.

Compare two side by side.

6 comparisons: where an agent gets further, checkpoint by checkpoint.

See what an agent sees in yours.

Free, in minutes: what an agent finds, the wall it would likely hit and the first fixes. A Drive ($49) lists yours here with its level.

?