No quota, because there is no key it could attach to
FreeNewsAPI is a full-text news search API for AI agents with no API key, no signup and no quota, pulling in over 150,000 articles a day from more than 25,000 publishers, refreshed continuously rather than on a fixed schedule set in advance. Most news APIs answer a request made without a key with a 401 error; this one answers the request itself directly.
A quota needs something to attach to before it can apply at all โ a key, an account, a plan tier with a number written on it somewhere. FreeNewsAPI has none of those three things, and the absence of a quota follows from that directly, rather than being a separate promise layered on top of the API.
Related tools
On this page
No key, so nothing to meter against
FreeNewsAPI requires no API key and no signup, and states no quota anywhere in its terms. Where most news APIs would answer an unauthenticated request with a 401 error and nothing else, this one answers the query directly instead โ there is no account layer sitting between the request and the result to meter usage against at all, on this call or the next one.
The scale the API states about itself
Over 150,000 articles a day come in from more than 25,000 publishers, and the feed refreshes continuously rather than on a fixed interval set a few times daily. Those are the two figures the API publishes about its own coverage; how far its archive reaches back historically is not one of them, and is left unstated anywhere on the site.
An MCP connector, same access as the REST API
Agents built around the MCP protocol can reach the same news search through a connector rather than wiring the REST endpoint directly into their own code, with no separate quota or access tier attached to using one integration path over the other one.
What no quota does not cover
FreeNewsAPI does not publish a latency figure for its responses, does not offer sentiment analysis on the articles it returns, and lists no paid tier above the free one it already offers. A stated absence of a quota describes the request limit specifically โ it says nothing at all about which features the API does or does not include, past that one specific number.
What still limits an agent using it
No quota on requests does not mean no limit on what comes back: an agent still only sees what is inside the 25,000-plus publishers FreeNewsAPI covers, and a story that has not been picked up by any of them will not appear no matter how many times the query is repeated. Removing the request ceiling does not remove the coverage ceiling underneath it.