2026-09-17, News · Fundamentals

Free news APIs in 2026: verified free tiers, limits and trade-offs

Most free news APIs are built for trying the API, not for running a product. On the vendors’ own pages (checked 2026-09-17), the free tiers range from 100 calls a month to 500 calls a day, and several of them forbid commercial or production use outright or deliver articles hours late. They are still the right starting point for prototypes, student projects and internal experiments.

Two kinds of “news API”

A news API searches the vendor’s own index of articles, gathered from the sources it crawls or licenses, and returns article metadata and sometimes full text.

A Google News results API returns what the Google News results page shows for a query, in a specific country, language and device, including each article’s position.

The first answers “what has been written about X”. The second answers “what does Google put in front of readers about X, and in what order”. A PR team measuring coverage share and a risk team screening names care about the second; a data scientist building a topic model often only needs the first.

Free tiers, verified

Every figure below comes from the vendor’s own pricing, documentation or FAQ page, linked in the table, checked 2026-09-17. “Not stated” means we did not find a commercial-use statement on the page cited.

Two retired or closed options still show up in older tutorials:

• Bing News Search API. Microsoft retired the Bing Search APIs on August 11, 2025 and directs customers to Grounding with Bing Search in Azure AI Agents (Microsoft lifecycle notice).
• Google Custom Search JSON API. Closed to new customers; existing customers have until January 1, 2027 to move off (Google). It was never a news API, but it was often used as one.

Google News RSS feeds are free and need no key, but the feed text restricts them to personal, non-commercial feed readers; Google News RSS feeds covers what they contain.

What the paid step looks like

Free tiers are designed to lead to a paid plan, and the jump is worth knowing before you build. From the same pages, checked 2026-09-17: NewsAPI.org’s cheapest paid plan is Business at $449 a month; GNews Essential is €49.99 a month; NewsData.io Basic is $199.99 a month; Mediastack Standard is $24.99 a month for 10,000 calls; Currents Builder is $69 a month; World News API Reporter is $39 a month for 500 points a day; NewsAPI.ai’s 5K plan is $90 a month; TheNewsAPI Basic is $19 a month for 2,500 requests a day. Prices change; check the linked page before you commit.

The trade-offs that decide

1. Delay

A 12- or 24-hour delay is invisible in a prototype and fatal in an alerting product. NewsAPI.org’s free plan delays articles by 24 hours and GNews by 12. If the use case is “tell me before my CEO hears about it”, test freshness on the plan you will pay for.

2. Commercial and production use

This is the limit teams discover last. Five of the ten free plans above say non-commercial or development-only in plain words. An internal dashboard at a company is commercial use under most of these terms, and NewsAPI.org explicitly includes internal use.

3. Articles per request

Allowances counted in requests hide how much each request returns. GNews returns up to 10 articles per request on the free plan, TheNewsAPI 3, Currents up to 20. For a watchlist of 50 entities, 100 requests a day at 3 articles each is thin.

4. History

Most free plans reach back about 30 days. Backfills, trend baselines and “has this person ever been in the news” screening need archive access, which is almost always paid.

5. Index coverage

Each vendor’s index is its own. Local and non-English publishers, paywalled outlets and trade press vary widely between vendors. Test with queries from your real watchlist, in the markets you care about, and count what each returns.

6. Full text versus metadata

The Guardian key includes article text for Guardian content; NewsData.io’s free plan excludes full content; most others return title, description, URL, source and time. If you plan to classify sentiment or extract entities, you need text, and you need the right to store it.

7. What “relevance” means

A news API ranks by its own relevance or recency. That ranking says nothing about what readers are shown. If your metric is visibility, the ranking you need is the one on the results page.

Choosing: a short decision path

1. Is it a prototype, a class project or a personal tool? Use a free tier whose terms allow it. The Guardian and NYT APIs are strong for their own content; GNews, NewsData.io and Currents give broad indexes to experiment with.
2. Is it going to production or used commercially? Rule out plans that forbid it, then compare paid plans on freshness, coverage in your markets, history and articles per request.
3. Do you need to know what Google News shows, in a given market, in order? An article index cannot tell you. Use Google News results.
4. Do you need both? Common in screening and PR: an index for recall and backfill, Google News results for visibility and prioritisation.

When a Google News results API fits

Choose results from the page itself when the question involves Google’s editorial choices:

• Coverage share. Which publishers and which stories occupy the results for your brand, your competitors or your category, per country.
• Prominence. Whether a negative story is in the top three results for a name, which matters more for reputation than whether it exists somewhere in an index.
• Market comparison. How the same story ranks in the US, Germany and Japan, queried in each language, on desktop and on mobile.
• Screening evidence. Adverse media screening that documents what a reasonable searcher would have found on a given date.

This API’s endpoint is POST /v1/monitor/google/news:

curl -X POST https://api.answerline.dev/v1/monitor/google/news \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "query": "\"acme corp\" recall", "country": "US", "hl": "en" }'

The response’s result.newsResults[] gives each article’s position, title, link, snippet, source, date, thumbnail and page, with redirectLink when Google served the link as a redirect. country (or gl) sets the geography, hl the interface language, and device switches between desktop and mobile results.

The same query from Python:

import os
import requests

resp = requests.post(
    "https://api.answerline.dev/v1/monitor/google/news",
    headers={"Authorization": f"Bearer {os.environ['ANSWERLINE_API_KEY']}"},
    json={"query": '"acme corp" recall', "country": "US", "hl": "en"},
    timeout=360,
)
resp.raise_for_status()
top3 = [r for r in resp.json()["result"]["newsResults"] if r["position"] <= 3]
for r in top3:
    print(r["position"], r["source"], r["title"], r["date"])

What it costs, compared honestly

A Google News async task is 3 credits, a synchronous call 5. The free tier includes 500 credits a month and permits building a real integration.

Unit counts are not comparable across these vendors. A news API request can return up to 10, 20 or 100 articles from an index; a Google News results request returns one results page for one query in one market. Compare on the job instead: for a watchlist of 20 entities in 2 markets checked every 4 hours, you need 20 × 2 × 6 = 240 results requests a day, or 720 credits. For plan prices see /pricing, and AI monitoring cost planning shows how to size a recurring program.

Scheduling it

For more than a handful of queries, submit async tasks in batches of up to 500 with POST /v1/async/task/batch, give each an idempotency key built from entity, market and window, and receive results through a signed webhook. Google Alerts API alternatives builds the full pipeline, including deduplication and notifications.

Combining an index with results

A pattern that works for screening and PR teams:

1. Recall from an index. Query a news API daily for each entity to collect every article it can find, with text if the plan allows.
2. Prominence from results. Query Google News results for the same entities per market on your cadence, and record positions.
3. Join on URL. Normalise both sides’ URLs (lowercase host, strip tracking parameters and fragments) and join. Articles present in both are the ones readers see.
4. Prioritise. Review first what is prominent in results, then what the index found that results did not show.

Pitfalls

• Prototyping on terms you cannot ship. Porting to a paid plan or another vendor late is expensive; pick a vendor whose production terms you can accept.
• Measuring freshness on the free plan and assuming the paid plan matches, or the reverse. Test the plan you will run.
• Counting requests instead of articles. Normalise to articles per entity per day.
• Treating index ranking as visibility. It is not what readers see.
• Following tutorials for retired APIs. Bing News Search is gone and Custom Search JSON is closed to new customers.
• Ignoring non-English markets. Index coverage and Google News results both differ most outside English; query in the local language.

For a pipeline design, see the news monitoring use case. Start with the Google News engine page.

Keep reading