Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the NewsData.io API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fnewsdata.io%2Fnewsdata" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fnewsdata.io%2Fnewsdata" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with NewsData.io API.
Search the latest news with q, qInTitle, or qInMeta keyword queries and filter by country, category, language, and source domain
Pull historical articles from the archive between a from_date and to_date
Track cryptocurrency coverage by coin and financial-market coverage by market_id
Count matching articles over a date range with /1/count, /1/crypto/count, and /1/market/count
GET STARTED
List indexed news sources by country, category, and language before narrowing a search
Register a real-time news query and stream matching articles over the /ws/event WebSocket
Patterns agents use NewsData.io API for, with concrete tasks.
★ Agent news briefing through Jentic
A research agent asked for a morning briefing searches Jentic for a news search operation, receives the getLatest input schema, and calls the NewsData.io API with a keyword in q, a country such as us, and a language such as en. The response returns article titles, links, and source details the agent can summarise, and the agent can follow nextPage tokens with the page parameter to read further results.
Search Jentic for 'search the latest news', then call GET /1/latest with q='semiconductor tariffs', country='us', language='en' and summarise the first page of results
Crypto and market news monitoring
Trading and research tools need coverage of specific assets rather than general headlines. The NewsData.io API exposes /1/crypto with a coin filter and /1/market with a market_id filter, both supporting sentiment and date filters, so a dashboard can show only articles about the assets it tracks.
Call GET /1/crypto with coin='btc' and sentiment='negative' and list the headlines and source domains returned
Media coverage trend analysis
Analysts measuring how coverage of a topic rises and falls need counts, not just articles. The /1/count endpoint takes a required from_date and to_date plus the usual keyword and country filters and returns article counts by interval, so a report can chart coverage volume without downloading every article.
Call GET /1/count with q='heatwave', from_date='2026-07-01', to_date='2026-07-31' and report the daily article counts
Real-time breaking news alerts
Some workflows need articles as they are published rather than on a polling schedule. Register a query with POST /1/websocket/register using filters such as q and country, connect to /ws/event with the returned registration_id to receive matching articles, review active registrations with /1/websocket/fetch, and remove one with /1/websocket/delete when the alert is no longer needed.
Call POST /1/websocket/register with q='product recall' and country='gb', store the registration_id, then call GET /1/websocket/fetch to confirm the registration is active
13 endpoints — the newsdata.
METHOD
PATH
DESCRIPTION
/1/latest
Search the latest news articles
/1/archive
Search the historical news archive
/1/crypto
Search cryptocurrency news
/1/market
Search financial-market news
/1/count
Count news articles over a date range
/1/sources
List indexed news sources
/1/websocket/register
Register a real-time news query
/1/latest
Search the latest news articles
/1/archive
Search the historical news archive
/1/crypto
Search cryptocurrency news
/1/market
Search financial-market news
/1/count
Count news articles over a date range
/1/sources
List indexed news sources
/1/websocket/register
Register a real-time news query
What agents get from Jentic-routed access to this vendor.
Setup
Wiring NewsData.io by hand means choosing between the apikey query parameter and the X-ACCESS-KEY header, learning which filters cannot be combined, and handling nextPage pagination yourself. Through Jentic you install once, import NewsData.io from the API Directory, store the key once, and your agent calls it.
Permission scoping
NewsData.io passes every filter in the query string and has no per-resource path ids, so rules bound which operations your agent may call rather than which topics it searches. You choose the operations it may call, so state-changing ones like registering or deleting real-time queries are not included unless you add them.
Credential isolation
Your NewsData.io API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'search the latest news' or 'count articles about a topic', and Jentic returns the matching NewsData.io operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using NewsData.io API through Jentic.
What authentication does the NewsData.io API use?
Per its OpenAPI spec, the NewsData.io API takes an API key either as the `apikey` query-string parameter or in the `X-ACCESS-KEY` header, and one of the two is required. The WebSocket management and stream operations (/1/websocket/fetch, /1/websocket/delete, and /ws/event) declare the `apikey` query parameter. Through Jentic, the key is stored encrypted by your own Jentic One instance and added to the call at execution time, so your agent never sees it.
Can I search historical news with the NewsData.io API?
Yes. GET /1/archive accepts from_date and to_date along with the same keyword, country, category, language, and domain filters as /1/latest. For volume rather than articles, GET /1/count takes a required from_date and to_date and returns article counts by interval.
What are the rate limits for the NewsData.io API?
The OpenAPI spec describes credit costs rather than a fixed request ceiling: /latest, /news, /crypto, /market, and /sources cost 1 credit per call, /archive costs 5, and the count endpoints cost 50. It also documents the `X-RateLimit-Remaining` and `X-API-Limit-Remaining` response headers for your remaining budget. Check https://newsdata.io/documentation for current plan limits.
How do I get breaking news alerts with the NewsData.io API through Jentic?
Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, add NewsData.io from the Jentic API Directory, and store your API key. Your agent can then search for 'register a real-time news query', call POST /1/websocket/register with filters such as q, and keep the returned registration_id for the /ws/event stream. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Can I limit what my agent is allowed to do with the NewsData.io API?
Yes. For a research agent, write a rule that allows GET /1/latest, GET /1/archive, and GET /1/sources, so it can read and search news but cannot register or delete real-time queries. Each call it makes is checked against that rule.
Is there a NewsData.io MCP server?
You don't need an MCP server to give your agent the NewsData.io API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls it, discovering operations on demand instead of loading every tool definition into its context.
What is the difference between /1/latest and /1/news in the NewsData.io API?
The spec describes GET /1/news as identical to GET /1/latest: both return recent articles with the same filters. Use /1/latest in new integrations and /1/news only where existing code already calls it.
For Agents
Search latest, archived, crypto, and market news with keyword, country, language, and sentiment filters, count matching articles over a date range, and register real-time news queries for WebSocket delivery.
Use for: I need the latest English news about electric vehicles from the US, Find all articles mentioning a company in the headline from the last week, Search for Bitcoin news with a positive sentiment, Get the number of articles about inflation published each day last month
Not supported: Does not publish articles, host media files, or provide social media posts or stock price quotes. Use for searching, counting, and streaming news articles only.
The NewsData.io API searches live and historical news articles and returns them as JSON with filters for keyword, country, category, language, source domain, sentiment, and more. Dedicated endpoints cover cryptocurrency news filtered by coin, financial-market news filtered by market_id, the archive with from_date and to_date ranges, article counts over time, and the list of indexed news sources. Real-time monitoring works by registering a query, then reading matching articles from a WebSocket stream until the registration is deleted.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>