Do coding agents recommend MapTiler?
MapTiler was chosen in 3% of 759 judged maps sessions, ranking ninth. Measured with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code.
MapTiler was chosen in 3% of 759 judged maps sessions, ranking ninth. It was also raised as a candidate in 196 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 maps inside a realistic codebase. Not what a chat assistant says about MapTiler. What an agent actually installed.
The numbers
| Category | Maps |
| Sessions in the category | 759 |
| Sessions where MapTiler was chosen | 25 |
| Install share | 3% |
| Rank in category | 9 of 49 |
| Codebases it won in | 7 |
| Raised as a candidate, not chosen | 196 |
| Chosen when considered | 11% |
| Site | maptiler.com |
By agent
Claude Code, Codex, Cursor, Grok Build CLI and Muse Code land within 6 points of each other on MapTiler, which is closer than most products in this experiment manage.
| Agent | Sessions | Chose MapTiler | Share |
|---|---|---|---|
| Claude Code | 164 | 6 | 4% |
| Codex | 227 | 9 | 4% |
| Cursor | 154 | 9 | 6% |
| Grok Build CLI | 37 | 0 | 0% |
| Muse Code | 177 | 1 | 1% |
By who was asking
MapTiler performs similarly across the four kinds of buyer, from 2% to 6%. That is unusual: the category leader changed with the persona in 23 of the 31 categories we measured.
| Who is asking | Sessions | Chose MapTiler | Share |
|---|---|---|---|
| Vibe coder | 163 | 9 | 6% |
| Junior developer | 247 | 8 | 3% |
| Senior engineer | 162 | 4 | 2% |
| Enterprise team | 187 | 4 | 2% |
What MapTiler was up against
The full ranking in maps, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | Google Maps | 133 | 18% |
| 2 | Leaflet | 125 | 16% |
| 3 | Apple Maps (MapKit) | 104 | 14% |
| 4 | MapLibre | 61 | 8% |
| 5 | Mapbox | 52 | 7% |
| 6 | Built in-house (no product adopted) | 43 | 6% |
| 7 | react-native-maps | 37 | 5% |
| 8 | OpenStreetMap | 37 | 5% |
What this means
This is an integration problem, not a presence problem. Agents raised MapTiler in 196 sessions and chose it in 25, 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 759 sessions in maps are part of a published set of 15,051, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: how we measured this.
Every maps run can be replayed on the board.
If you work on MapTiler: 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 MapTiler?
Yes. MapTiler was chosen in 25 of the 759 judged sessions in maps, a 3% install share, ranking ninth in its category.
Does Claude Code recommend MapTiler?
In 6 of the 164 sessions in maps run with Claude Code, which is 4%.
Do different coding agents treat MapTiler differently?
Not much. Claude Code, Codex, Cursor, Grok Build CLI and Muse Code chose it at similar rates, between 0% and 6% of their runs.
How was this measured?
Real coding agents at pinned versions were run in sandboxes inside 92 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 MapTiler considered but not chosen?
It was raised as a candidate in 196 sessions without being chosen, and chosen in 25. That is a 11% conversion from considered to chosen.
Where this comes from
Armature ran 15,051 judged sessions with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code inside 92 realistic codebases, and published every run. The numbers on this page come from that work.