From the experiment

Do coding agents recommend NewsAPI.ai?

NewsAPI.ai was chosen in 4% of 639 judged AI search sessions, ranking ninth. Measured with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code.

Published September 28, 2026 Updated September 29, 2026 Read as Markdown

NewsAPI.ai was chosen in 4% of 639 judged AI search sessions, ranking ninth. It was also raised as a candidate in 14 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 AI search inside a realistic codebase. Not what a chat assistant says about NewsAPI.ai. What an agent actually installed.

The numbers

CategoryAI search
Sessions in the category639
Sessions where NewsAPI.ai was chosen25
Install share4%
Rank in category9 of 42
Codebases it won in3
Raised as a candidate, not chosen14
Chosen when considered64%
Sitenewsapi.ai

By agent

Claude Code, Codex, Cursor, Grok Build CLI and Muse Code agree closely on NewsAPI.ai, choosing it at rates within 5 points of each other.

AgentSessionsChose NewsAPI.aiShare
Claude Code14096%
Codex19274%
Cursor13664%
Grok Build CLI3513%
Muse Code13621%

By who was asking

NewsAPI.ai performs similarly across the four kinds of buyer, from 0% to 11%. That is unusual: the category leader changed with the persona in 23 of the 31 categories we measured.

Who is askingSessionsChose NewsAPI.aiShare
Vibe coder10600%
Junior developer20800%
Senior engineer15764%
Enterprise team1681911%

What NewsAPI.ai was up against

The full ranking in AI search, from the same sessions:

#ProductRuns wonShare
1Exa9214%
2Brave Search API8914%
3Anthropic web search8613%
4Tavily7912%
5OpenAI web search325%
6Built in-house (no product adopted)325%
7Firecrawl315%
8Parallel295%

What this means

Agents almost never raise NewsAPI.ai without choosing it: 14 sessions raised against 25 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 639 sessions in AI search 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 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 25 of the 639 judged sessions in AI search, a 4% install share, ranking ninth in its category.

Does Claude Code recommend NewsAPI.ai?

In 9 of the 140 sessions in AI search run with Claude Code, which is 6%.

Do different coding agents treat NewsAPI.ai differently?

Not much. Claude Code, Codex, Cursor, Grok Build CLI and Muse Code chose it at similar rates, between 1% 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 NewsAPI.ai considered but not chosen?

It was raised as a candidate in 14 sessions without being chosen, and chosen in 25. That is a 64% 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.

Read next

All library pages