Square vs Stripe for AI agents
As of 2 Nov 2026, Stripe gets an AI agent further than Square: L3 (Does the work) against L1 (Needs a person).
AgentDrives StudySquare: 2 drives, last 27 Oct 2026 (68 attempts). Stripe: 3 drives, last 2 Nov 2026 (129 attempts). Method v50.
- Find Docs it can act on
- Get in Can't sign up
- Use Work not reached
- Pay Payment not reached
- Leave Leaving not reached
Stopped at sign-up: blocked. Next: let an agent sign up on its own
The form refused our agent's browser; the page runs invisible Google reCAPTCHA Enterprise. Please try again." No visible challenge appeared. With no account there was no token, so GET /v2/locations answered 401 on production and Sandbox, and no payments, invoices, customers or orders work was reached. The docs are agent-friendly: llms.txt, Markdown pages, an OpenAPI spec and an official MCP server. No checkout was reached. Deactivating a Square account happens on the web only, in the Dashboard.
Driven 27 Oct 2026 · The drive and its evidence- Find Docs it can act on
- Get in Try first, claim later
- Use 67% of the work
- Pay No payment made
- Leave Nothing to cancel
In on its own; 67% of the work done. Next: do 80% of the core work (now 67%)
A documented CLI command made an anonymous claimable sandbox and a restricted key, with no form, email check or card. Claiming the sandbox in the Dashboard showed a visible hCaptcha picture puzzle, and our agent made no full account. With the key it created customers, products, prices, PaymentIntents, payment links, Checkout sessions, subscriptions and invoices through the API, each read back. Terminal, usage billing and Connect sat outside that key. No agent route deletes an unclaimed sandbox, and the key hit a request limit with no word on when to retry.
Driven 2 Nov 2026 · The drive and its evidenceThe two summaries: written with AI from each product's drive.
Step by step
What our agent got done at each step, and what it saw there.
Find
SquareDocs it can act on
developer.squareup.com/llms.txt (97 KB) and the get-started page name the sign-up, Sandbox, SDKs, webhooks and the MCP server.
StripeDocs it can act on
Docs read without a browser: docs.stripe.com/llms.txt (525 links) and stripe.com/llms.txt, Markdown pages (.md and Accept: text/markdown on the pages tried), the public OpenAPI 3.0.0 spec (612 operations), and an MCP server at mcp.stripe.com that answers MCP (the 28 Jul 2026 spec).
Get in
SquareCan't sign up
The developer sign-up (Email, Password, Locale, terms) was refused by the invisible reCAPTCHA Enterprise check on the agent's inbox (twice) and on our fallback address: the page said only 'Something went wrong. Please try again.'
StripeTry first, claim later
The sandbox command returns a restricted key, used for API, CLI and as Bearer on MCP. The docs give no API or CLI route to create, scope or revoke a key: that is Dashboard-only.
Use
SquareWork not reached
No token, so nothing could be created.
Stripe67% of the work
Created a customer, products, prices, PaymentIntents, payment links, Checkout sessions, subscriptions and invoices without a browser, each read back.
Pay
SquarePayment not reached
Only a card checkout, which an agent can finish once a person gives it a card.
StripeNo payment made
No self-serve purchase.
Leave
SquareLeaving not reached
No Square account was made. Account deactivation is web only (help article 3819: Dashboard > My business > About > Deactivate your business, password and a verification code).
StripeNothing to cancel
No agent route deletes an unclaimed sandbox: `stripe sandboxes delete` needs a live-account `stripe login`, there is no API or MCP delete, and the Dashboard is behind the claim. Per the docs, Stripe deletes an unclaimed sandbox after 60 days. Test objects were left in it (the API key was throttled and MCP has no delete tools).
Where each one stops
SquareStopped at sign-up: blocked
StripeIn on its own; 67% of the work done
| Checkpoint | Square | Stripe |
|---|---|---|
| Docs | On its own | On its own |
| Sign up | Blocked | Not needed |
| Verify | Not reached | Not needed |
| Key | Not reached | On its own |
| First call | Not reached | On its own |
| First action | Not reached | On its own |
| Pay | Not reached | Not tried |
| Cancel | Not reached | Not needed |
| Delete | Not reached | Blocked |
On its own, or in a browser
How our agent passed each checkpoint, and what each product offers an agent.
Checkpoints by route, API, MCP, CLI and SDK
| Square | Stripe | |
|---|---|---|
| Passed on its own | 1 | 4 |
| Passed in a browser | 0 | 0 |
| Needed a person | 0 | 0 |
| Blocked | 1 | 1 |
| Work done | Not measured | 67% of the core |
| API | Yes | Yes |
| OpenAPI | – | Yes |
| MCP server | Yes (official) | Yes (official) |
| CLI | No | Yes |
| SDK | Yes | Yes |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed
| Square | Stripe | |
|---|---|---|
| Bot check | Google reCAPTCHA Enterprise (invisible) stopped it at sign up, without a visible challenge | hCaptcha stopped one way in at sign up; it got in another way |
| Wall type | A check of our network and browser | A challenge on the form |
| First wall | The form refused our agent's browser; the page runs invisible Google reCAPTCHA Enterprise | None |
| A person helped | No | No |
A check of our network and browser: It judged where our agent connected from and its browser, not a person. Our agent, working on its own from a data center, didn't get through; the owner can open the check to agents. How agents in a person's own browser fare isn't measured yet. A challenge on the form: It asks every visitor to prove they are human. Our agent doesn't solve these, and its signature didn't change that: a person does this step, or the owner opens it for agents. Where we drive from.
Level and part scores
| Square | Stripe | |
|---|---|---|
| Level | L1 · Needs a person | L3 · Does the work |
| Holds up | Not measured | 84 of 100, good |
| Docs match | Not measured | 84 of 100, fair |
| Standards | MCP client registration (behind) · OpenAPI 3.0.0 (2 versions behind) | MCP discovery (current) · MCP client registration (behind) · OpenAPI 3.0.0 (2 versions behind) |
| Security | Reported privately to the owner | No review in this drive |
Pay, cancel and delete
| Square | Stripe | |
|---|---|---|
| Pay | Payment not reached | No payment made |
| Free plan or trial | Free plan | Free plan |
| Cancel | Not reached | Not needed |
| Delete the account | Not reached | Blocked |
How each one takes payment
- Square: Payment not reached.
- Stripe: No payment made: paying needs an account.
Square vs Stripe: the short answers
Which can an AI agent use, Square or Stripe?
Stripe gets an AI agent further than Square: L3 (Does the work) against L1 (Needs a person). With Square our agent was stopped at sign-up (blocked); with Stripe it got in on its own and did 67% of the work. Driven 27 Oct 2026 (Square) and 2 Nov 2026 (Stripe).
Can an AI agent sign up for Square and Stripe on its own?
Square: no, blocked. Stripe: not needed.
Do Square and Stripe have an MCP server?
Square: yes (official). Stripe: yes (official).
Can an AI agent delete its Square or Stripe account?
Square: not reached. Stripe: blocked.
The drives and the category
Put your own shortlist side by side
A Tool comparison drives the tools you're choosing between and shows which ones your agents can use.