Compared with Event Registry
The Event Registry (NewsAPI.ai) alternative for AI agents
Event Registry is built for news analytics: concepts, events and an archive back to 2014. typesearch is built for agents that search the news now: a calibrated relevance probability on every result, the top ones read before they’re ranked, typed answers per article — from $1.40 per 1,000 searches, with no monthly plan.
Checked Sep 25, 2026 · A news API with events, concepts and a 2014+ archive
At the same volume
5K · 5,000 requests a month
$7/ month
typesearch, fast mode
Event Registry: $90−92%
$18 per 1,000 · 5,000 tokens a month
20K · 20,000 requests a month
$28/ month
typesearch, fast mode
Event Registry: $220−87%
$11 per 1,000 · 20,000 tokens a month
100K · 100,000 requests a month
$140/ month
typesearch, fast mode
Event Registry: $700−80%
$7 per 1,000 · 100,000 tokens a month
500K · 500,000 requests a month
$700/ month
typesearch, fast mode
Event Registry: $3,000−76%
$6 per 1,000 · 500,000 tokens a month
Event Registry counts tokens: a search of recent articles is 1 token and returns up to 100 articles; an archive search costs 5 tokens per year searched. Extra tokens are $0.015 and tokens don’t roll over. typesearch returns up to 50 judged results per search, with no plan.
Checked Sep 25, 2026 · Sources: newsapi.ai/plans
Side by side
What Event Registry publishes, next to what typesearch does. Each of their facts links to where we read it.
Checked Sep 25, 2026 · Sources: newsapi.ai/plans, newsapi.ai/documentation, newsapi.ai/terms, newsapi.ai/documentation
How the parameters map
Each Event Registry parameter and what it becomes on typesearch. You rewrite one request; your agent’s logic stays.
| Event Registry parameter | Status | On typesearch |
|---|---|---|
| keyword | Mapped | query. Or up to five queries, judged together. |
| conceptUri, categoryUri | Limited | Name the concept in the query; the model judges meaning, not just keywords. |
| sourceUri | Mapped | include_domains, up to 20. |
| lang | Limited | Query in the language you want, or restrict to regional outlets with include_domains. |
| dateStart, dateEnd | Mapped | published_after, published_before, within the last 30 days. |
| articlesCount, articlesPage | Limited | max_results, up to 50. No pagination. |
| articlesSortBy | Limited | Ranked by a calibrated relevance probability; published_at to sort by date. |
| isDuplicateFilter | Mapped | dedupe: true groups the same story, with the duplicates attached. |
| minSentiment, maxSentiment | Mapped | tone: true — positive, neutral or negative toward your query, in any language. |
| getEvents | Mapped | /v1/similar: every article about the same story as a URL. |
| articleBodyLen | Limited | Never the full article: verbatim highlights in normal and deep. |
| apiKey | Mapped | Authorization: Bearer <key> |
| articles.results[]: title, url, body, dateTimePub, source.title | Mapped | results[]: title, url, snippet, published_at, source |
What you gain
- Pay as you go from $1.40 per 1,000 searches, against $18 per 1,000 recent searches on the 5K plan
- No tokens that expire at the end of the month
- A calibrated relevance probability on every result
- Your own typed questions answered per article; tone in any language
- A free credit you can use beyond testing
When Event Registry is the better fit
We’d rather you pick right the first time. Keep Event Registry for these:
- You need an archive back to 2014, or searches across years.
- You work with concepts and event clusters rather than keyword queries.
- You need the full text of every article.
The migration
The whole migration
Before and after: the request, the key header and the fields you read. Everything else in your code stays.
import requests-r = requests.post("https://eventregistry.org/api/v1/article/getArticles",- json={"apiKey": ER_API_KEY, "keyword": "lithium royalties in Chile", "dateStart": "2026-09-18", "articlesCount": 20},-).json()+r = requests.post("https://api.typesearch.ai/v1/search",+ headers={"Authorization": f"Bearer {TYPESEARCH_API_KEY}"},+ json={"query": "lithium royalties in Chile", "days": 7, "max_results": 20, "mode": "fast"},+).json()-for a in r["articles"]["results"]:- print(a["title"], a["url"], a["dateTimePub"], a["source"]["title"])+for a in r["results"]:+ print(a["title"], a["url"], a["published_at"], a["source"], a["score"])
Switching from Event Registry
How is typesearch different from Event Registry?
Event Registry annotates every article with concepts, categories and the event it belongs to, and keeps an archive since 2014. typesearch judges results for your query in real time — a calibrated probability, the top ones read — and answers your own typed questions per article.
How much does typesearch cost compared with Event Registry?
At the volume of Event Registry’s 5K plan (5,000 requests a month), typesearch costs $7 in fast mode, against $90. At the volume of Event Registry’s 20K plan (20,000 requests a month), typesearch costs $28 in fast mode, against $220. At the volume of Event Registry’s 100K plan (100,000 requests a month), typesearch costs $140 in fast mode, against $700. At the volume of Event Registry’s 500K plan (500,000 requests a month), typesearch costs $700 in fast mode, against $3,000. Results served from the cache are free, and there are no seats or minimums.
How do I switch from Event Registry?
Rewrite one request: the endpoint, the key header and a few parameter names change — see the table above. The fields you read map one to one: body → snippet and highlights, dateTimePub → published_at, source.title → source.
When should I stay with Event Registry?
If you need an archive back to 2014, concept and event search, full article text, or 100 articles per request. You can also use both: typesearch for what your agent searches now, Event Registry for the rest.
Keep comparing
Other comparisons
Use cases
Switch from Event Registry
A key in a minute, $5 in free credit, one request to rewrite.