Do coding agents recommend Stripe?
Stripe is the most chosen payment provider, taking 88% of 657 judged payments sessions. Measured with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code.
Stripe is the most chosen payment provider, taking 88% of 657 judged payments sessions. It was also raised as a candidate in 75 further sessions without being chosen.
This page reports what happened when Claude Code, Codex, Cursor, Grok Build CLI and Muse Code had to solve a problem in payments inside a realistic codebase. Not what a chat assistant says about Stripe. What an agent actually installed.
The numbers
| Category | Payments |
| Sessions in the category | 657 |
| Sessions where Stripe was chosen | 578 |
| Install share | 88% |
| Rank in category | 1 of 9 |
| Codebases it won in | 11 |
| Raised as a candidate, not chosen | 75 |
| Chosen when considered | 89% |
| Site | stripe.com |
By agent
Claude Code, Codex, Cursor, Grok Build CLI and Muse Code land within 9 points of each other on Stripe, which is closer than most products in this experiment manage.
| Agent | Sessions | Chose Stripe | Share |
|---|---|---|---|
| Claude Code | 165 | 155 | 94% |
| Codex | 198 | 169 | 85% |
| Cursor | 164 | 139 | 85% |
| Grok Build CLI | 33 | 29 | 88% |
| Muse Code | 97 | 86 | 89% |
By who was asking
Stripe does much better with one kind of buyer than another. It won 100% of sessions asked as junior developer and 77% of those asked as senior engineer.
| Who is asking | Sessions | Chose Stripe | Share |
|---|---|---|---|
| Vibe coder | 119 | 111 | 93% |
| Junior developer | 180 | 180 | 100% |
| Senior engineer | 180 | 139 | 77% |
| Enterprise team | 178 | 148 | 83% |
What Stripe was up against
The full ranking in payments, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | Stripe (this page) | 578 | 88% |
| 2 | Paddle | 27 | 4% |
| 3 | Mollie | 18 | 3% |
| 4 | GoCardless | 17 | 3% |
| 5 | Adyen | 9 | 1% |
| 6 | Bottomline PTX | 3 | 0% |
| 7 | AccessPay | 2 | 0% |
| 8 | Helcim | 2 | 0% |
What this means
Leading a category is a position to defend rather than a result to celebrate. In our data, leaders lose ground in exactly two situations: when the person asking is an enterprise buyer with procurement constraints, and when a competitor's documentation is easier for an agent to integrate correctly.
The defence is unglamorous. Keep the quickstart running. Keep the version current on the page. Keep the names aligned. Stay in the templates.
Where these numbers come from
The 657 sessions in payments are part of a published set of 15,287, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: how we measured this.
Every payments run can be replayed on the board.
If you work on Stripe: the judge recorded a reason for every session where it was raised and passed over. Those reasons are in the transcripts.
<!-- generated by scripts/write-data-pages.mjs -->
Common questions
Do coding agents recommend Stripe?
Yes. Stripe was chosen in 578 of the 657 judged sessions in payments, a 88% install share, ranking first in its category.
Does Claude Code recommend Stripe?
In 155 of the 165 sessions in payments run with Claude Code, which is 94%.
Do different coding agents treat Stripe differently?
Not much. Claude Code, Codex, Cursor, Grok Build CLI and Muse Code chose it at similar rates, between 85% and 94% of their runs.
How was this measured?
Real coding agents at pinned versions were run in sandboxes inside 110 realistic codebases and asked to solve real tasks. A simulated project owner approved or questioned each recommendation before any code was written, and a judge from a model family that builds none of the agents read every session blind.
How often is Stripe considered but not chosen?
It was raised as a candidate in 75 sessions without being chosen, and chosen in 578. That is a 89% conversion from considered to chosen.
Where this comes from
Armature ran 15,287 judged sessions with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code inside 110 realistic codebases, and published every run. The numbers on this page come from that work.