Do coding agents recommend NewsAPI.ai?
NewsAPI.ai was chosen in 4% of 277 judged AI search sessions, ranking eighth. Measured with Claude Code, Codex and Cursor.
NewsAPI.ai was chosen in 4% of 277 judged AI search sessions, ranking eighth. It was also raised as a candidate in 7 further sessions without being chosen.
This page reports what happened when Claude Code, Codex and Cursor had to solve a problem in AI search inside a realistic codebase. Not what a chat assistant says about NewsAPI.ai. What an agent actually installed.
The numbers
| Category | AI search |
| Sessions in the category | 277 |
| Sessions where NewsAPI.ai was chosen | 11 |
| Install share | 4% |
| Rank in category | 8 of 27 |
| Codebases it won in | 2 |
| Raised as a candidate, not chosen | 7 |
| Chosen when considered | 61% |
| Site | newsapi.ai |
By agent
With 11 wins spread across three 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 NewsAPI.ai | Share |
|---|---|---|---|
| Claude Code | 92 | 4 | 4% |
| Codex | 96 | 3 | 3% |
| Cursor | 89 | 4 | 4% |
By who was asking
NewsAPI.ai does much better with one kind of buyer than another. It won 17% of sessions asked as enterprise team and 0% of those asked as junior developer.
| Who is asking | Sessions | Chose NewsAPI.ai | Share |
|---|---|---|---|
| Vibe coder | 44 | 0 | 0% |
| Junior developer | 117 | 0 | 0% |
| Senior engineer | 68 | 3 | 4% |
| Enterprise team | 48 | 8 | 17% |
What NewsAPI.ai was up against
The full ranking in AI search, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | Anthropic web search | 56 | 20% |
| 2 | Exa | 38 | 14% |
| 3 | Brave Search API | 31 | 11% |
| 4 | Tavily | 21 | 8% |
| 5 | OpenAI web search | 16 | 6% |
| 6 | Firecrawl | 14 | 5% |
| 7 | Parallel | 13 | 5% |
| 8 | Built in-house (no product adopted) | 13 | 5% |
What this means
Agents almost never raise NewsAPI.ai without choosing it: 7 sessions raised against 11 chosen. When it gets considered, it usually wins. The constraint is how rarely it gets considered at all, which is a presence problem: templates, framework integrations and pages that answer the configuration and production questions agents actually search for.
Where these numbers come from
The 277 sessions in AI search are part of a published set of 7,025, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: how we measured this.
Every AI search run can be replayed on the board.
If you work on NewsAPI.ai: 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 NewsAPI.ai?
Yes. NewsAPI.ai was chosen in 11 of the 277 judged sessions in AI search, a 4% install share, ranking eighth in its category.
Does Claude Code recommend NewsAPI.ai?
In 4 of the 92 sessions in AI search run with Claude Code, which is 4%.
Do different coding agents treat NewsAPI.ai differently?
Not much. The three agents chose it at similar rates, between 3% and 4% of their runs.
How was this measured?
Real coding agents at pinned versions were run in sandboxes inside 77 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 NewsAPI.ai considered but not chosen?
It was raised as a candidate in 7 sessions without being chosen, and chosen in 11. That is a 61% conversion from considered to chosen.
Where this comes from
Armature ran 7,025 judged sessions with Claude Code, Codex and Cursor inside 77 realistic codebases, and published every run. The numbers on this page come from that work.