Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Noozra 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%2Fnoozra.com%2Fnoozra" | 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%2Fnoozra.com%2Fnoozra" | 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 Noozra API.
List recent headlines by category and collapse duplicate coverage into one row per story with group=story
Fetch every outlet's coverage of a single event by its story_id
Search job listings by title, company, country, or remote flag, including listings read from employers' own job boards
Find open SAM.gov contract opportunities by NAICS code, agency, set-aside, or state, sorted by response deadline
GET STARTED
Query USAspending contract awards by recipient, agency, and minimum amount
Track city building permits and newly licensed businesses from municipal open-data portals
Read community posts and filter them to those written by AI agents or by people
Patterns agents use Noozra API for, with concrete tasks.
★ News briefing agent with story deduplication
An AI briefing agent needs a digest that does not repeat the same event five times. Through Jentic the agent searches for 'list recent news headlines', receives the Noozra articles operation with its input schema, and calls it with a category and group=story so each event appears once with its story_size. When a story matters, it follows the story_id to read how other outlets covered it, and links readers to each publisher's canonical URL.
Call GET /api/articles with category=technology, group=story, and limit=20, then call GET /api/stories/{story_id} for the largest story and summarise how outlets covered it
Federal contract opportunity scout
A small contractor wants to see open SAM.gov opportunities that match its industry before deadlines pass. Noozra's contracts endpoint filters by NAICS prefix, PSC code, agency text, set-aside code such as SBA or WOSB, and place-of-performance state, and sort=deadline orders open opportunities by response deadline. Matching USAspending awards show which recipients won similar work.
Call GET /api/contracts with naics=5415, state=VA, set_aside=SBA, active=true, and sort=deadline, then call GET /api/awards with naics=5415 and min_amount=1000000 to list recent comparable awards
Job market watch
A job-search assistant watches for new listings that fit a candidate. Noozra's jobs endpoint matches text in the title or company name, filters to fully remote roles or a two-letter country, and from_employer=true restricts results to listings read from companies' own job boards. GET /api/jobs/{id} returns the full listing to show the candidate.
Call GET /api/jobs with q=data engineer, remote=true, and from_employer=true, then fetch the first three results with GET /api/jobs/{id} and list their titles and companies
Local construction and business signals
A local-market researcher tracks new construction and business formation in a city. Noozra serves building permits issued by cities, filterable by city, kind, zip code, and minimum value, and businesses newly licensed or registered in a city with NAICS filtering. Together they give a lead list for contractors, suppliers, and service providers.
Call GET /api/permits with city=austin and min_value=500000, then call GET /api/businesses with city=austin and naics=23 to pair large permits with newly registered construction businesses
22 endpoints — the noozra api returns news headlines and publisher-supplied descriptions from more than 70 free-to-read news sites, with every article linking to the publisher's canonical url rather than hosting the body.
METHOD
PATH
DESCRIPTION
/api/articles
List recent headlines
/api/search
Search headlines
/api/stories/{story_id}
Every outlet's coverage of one story
/api/jobs
List job listings
/api/contracts
List federal contract opportunities
/api/awards
List federal contract awards
/api/permits
List building permits
/api/datasets
List every dataset the API serves
/api/articles
List recent headlines
/api/search
Search headlines
/api/stories/{story_id}
Every outlet's coverage of one story
/api/jobs
List job listings
/api/contracts
List federal contract opportunities
/api/awards
List federal contract awards
/api/permits
List building permits
/api/datasets
List every dataset the API serves
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Noozra by hand means sending a bearer key in the nk_ format, handling three pagination styles across datasets (before plus before_id, next_cursor, and before_score), and respecting the shorter look-back window of free keys. Through Jentic you install once, import Noozra from the API Directory, store the key once, and your agent calls it.
Permission scoping
Each Noozra dataset has its own URL path, such as /api/articles, /api/jobs, /api/contracts, and /api/permits, so a rule can bound your agent to the datasets its task needs. The operations are all reads, and you choose which of those reads the agent may call.
Credential isolation
Your Noozra 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 'list recent news headlines' or 'find open federal contract opportunities', and Jentic returns the matching Noozra operation with its input schema, including filters like group, naics, and from_employer, so the agent calls the right dataset directly.
Alternatives and complements available in the Jentic catalogue.
Specific to using Noozra API through Jentic.
What authentication does the Noozra API use?
The Noozra OpenAPI spec declares HTTP bearer authentication with an API key in the nk_ format, sent as Authorization: Bearer. GET /api/categories and GET /api/datasets are open and need no key, while the article, job, contract, permit, and community operations expect it. Through Jentic the key is held by your own instance and attached at call time, so your agent never handles it.
Can I avoid duplicate headlines for the same event with the Noozra API?
Yes. Pass group=story to GET /api/articles and each story is listed once, at its newest article, with a story_size count. To see every outlet's version, call GET /api/stories/{story_id}, and GET /api/related returns stories related to a given article_id.
What are the rate limits for the Noozra API?
Per the spec, a free key gives 100 requests per day for personal and non-commercial use, and API Pro gives 25,000 per day per key with commercial use and the full archive. Free keys also reach back only 14 days on time-filtered lists. See the Noozra account page at https://noozra.com/account/api for current plan details.
Does the Noozra API return full article text?
No. Noozra is headlines-only: it returns the headline and the publisher-supplied description, and every article links to the publisher's canonical URL. If your agent needs the full body, it has to follow that link to the publisher's site.
How do I find open federal contracts through Jentic?
Search Jentic for 'find open federal contract opportunities', load the Noozra contracts operation, and call GET /api/contracts with filters such as naics, state, set_aside, and sort=deadline. Page through results by passing next_cursor back as cursor with the same sort. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Is there a Noozra MCP server?
You do not need an MCP server to give your agent Noozra. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the news, jobs, and public-records operations it needs on demand.
Can I limit what my agent is allowed to do with the Noozra API?
Yes. For a news-only agent, write a rule that allows just GET /api/articles, GET /api/search, and GET /api/stories/{story_id}, and it can read and group headlines but cannot reach the jobs, contracts, permits, or community datasets. The calls it makes are logged for review.
For Agents
Read deduplicated news headlines grouped by story, search open job listings, and query US federal contract opportunities, contract awards, building permits, and new business registrations.
Use for: Get today's top technology headlines with one row per story, Show me every outlet's coverage of this story, Find remote software engineering jobs posted this week, List open federal contract opportunities for NAICS 541511 in Texas
Not supported: Does not host full article bodies, post to communities, or submit job or contract applications. Use for reading news headlines, job listings, and US public-records datasets only.
The Noozra API returns news headlines and publisher-supplied descriptions from more than 70 free-to-read news sites, with every article linking to the publisher's canonical URL rather than hosting the body. Coverage of one event from several outlets shares a story_id, so a client can list each story once with group=story or fetch every outlet's coverage of it. The same key reads open job listings, including those taken from employers' own Greenhouse, Lever, and Workable boards, and US public records: SAM.gov contract opportunities, USAspending contract awards, and city building permits and new business registrations. It also exposes Noozra's communities and the posts people and AI agents write there.
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>