Do coding agents recommend Adyen?
Adyen was chosen in 2% of 559 judged payments sessions, ranking fifth. Measured with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code.
Adyen was chosen in 2% of 559 judged payments sessions, ranking fifth. It was also raised as a candidate in 218 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 Adyen. What an agent actually installed.
The numbers
| Category | Payments |
| Sessions in the category | 559 |
| Sessions where Adyen was chosen | 9 |
| Install share | 2% |
| Rank in category | 5 of 9 |
| Codebases it won in | 3 |
| Raised as a candidate, not chosen | 218 |
| Chosen when considered | 4% |
| Site | adyen.com |
By agent
With 9 wins spread across 5 agents, the rates below are small numbers and a difference between them is not yet a finding. They are here because the direction is worth knowing, not because the gap is established.
| Agent | Sessions | Chose Adyen | Share |
|---|---|---|---|
| Claude Code | 165 | 4 | 2% |
| Codex | 165 | 0 | 0% |
| Cursor | 164 | 4 | 2% |
| Grok Build CLI | 33 | 1 | 3% |
| Muse Code | 32 | 0 | 0% |
By who was asking
Adyen performs similarly across the four kinds of buyer, from 0% to 6%. That is unusual: the category leader changed with the persona in 23 of the 29 categories we measured.
| Who is asking | Sessions | Chose Adyen | Share |
|---|---|---|---|
| Vibe coder | 101 | 0 | 0% |
| Junior developer | 153 | 0 | 0% |
| Senior engineer | 153 | 0 | 0% |
| Enterprise team | 152 | 9 | 6% |
What Adyen was up against
The full ranking in payments, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | Stripe | 490 | 88% |
| 2 | Paddle | 22 | 4% |
| 3 | Mollie | 17 | 3% |
| 4 | GoCardless | 13 | 2% |
| 5 | Adyen (this page) | 9 | 2% |
| 6 | Bottomline PTX | 3 | 1% |
| 7 | AccessPay | 2 | 0% |
| 8 | Helcim | 2 | 0% |
What this means
This is an integration problem, not a presence problem. Agents raised Adyen in 218 sessions and chose it in 9, so it reaches the shortlist and then loses. Something at the last step is costing the session, and in our data that is usually a quickstart that does not run when pasted, documentation describing an interface that changed, or a package name that does not match the product name.
That is the cheaper of the two problems to have. The reason is written down in each losing transcript.
Where these numbers come from
The 559 sessions in payments are part of a published set of 11,878, 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 Adyen: 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 Adyen?
Yes. Adyen was chosen in 9 of the 559 judged sessions in payments, a 2% install share, ranking fifth in its category.
Does Claude Code recommend Adyen?
In 4 of the 165 sessions in payments run with Claude Code, which is 2%.
Do different coding agents treat Adyen differently?
Not much. Claude Code, Codex, Cursor, Grok Build CLI and Muse Code chose it at similar rates, between 0% and 3% of their runs.
How was this measured?
Real coding agents at pinned versions were run in sandboxes inside 91 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 Adyen considered but not chosen?
It was raised as a candidate in 218 sessions without being chosen, and chosen in 9. That is a 4% conversion from considered to chosen.
Where this comes from
Armature ran 11,878 judged sessions with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code inside 91 realistic codebases, and published every run. The numbers on this page come from that work.