Install Jentic One Beta

Connect the Event Registry REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Event Registry REST 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%2Feventregistry.org%2Feventregistry" | sh

Step 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%2Feventregistry.org%2Feventregistry" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with Event Registry REST API.

Annotate text to identify people, locations, organizations, and topics

Score sentiment and categorize documents into predefined categories

Detect the language of a document and measure semantic similarity between two

Search news articles by concept, source, and date

Retrieve news events and the articles that report them

GET STARTED

Start building with Event Registry REST API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Event Registry REST API for, with concrete tasks.

★ Agent-Driven Text Intelligence

An AI agent connected through Jentic enriches raw text by annotating its entities, scoring its sentiment, and categorizing it, then detects its language when the source is unknown. Because each analysis is its own operation, the agent assembles exactly the pipeline a task needs, such as entity extraction followed by sentiment, without pulling an all-in-one model.

Annotate an article to extract its organizations, then score the article's sentiment

News Monitoring

A monitoring workflow tracks coverage of a topic by searching news articles and the events that group them. The Event Registry API queries articles by concept, source, and date and returns the matching events, so an agent builds a running feed of relevant coverage from across many sources.

Search articles for a concept over the last week and group the matches by the events they belong to

Query Building with URIs

Before a precise search, an agent resolves human names into the identifiers Event Registry expects. The autosuggest operations map a concept, category, source, or location label to its URI, letting an agent turn 'articles about renewable energy from Reuters' into a URI-based query that returns clean results.

Resolve a concept label and a source name to their URIs and build an article search from them

Key Endpoints

25 endpoints — the event registry rest api runs text analytics over news content and retrieves the articles and events behind it.

METHOD

PATH

DESCRIPTION

GET

/api/v1/article/getArticles

Search news articles by conditions

GET

/api/v1/event/getEvents

Retrieve news events by conditions

GET

/annotate

Identify entities mentioned in text

GET

/categorize

Categorize text into predefined categories

GET

/sentiment

Vocabulary-based sentiment detection

GET

/detectLanguage

Detect the language of input text

GET

/semanticSimilarity

Compute semantic similarity of two documents

GET

/api/v1/getEventForText

Identify the event that best matches input text

GET

/api/v1/article/getArticles

Search news articles by conditions

GET

/api/v1/event/getEvents

Retrieve news events by conditions

GET

/annotate

Identify entities mentioned in text

GET

/categorize

Categorize text into predefined categories

GET

/sentiment

Vocabulary-based sentiment detection

GET

/detectLanguage

Detect the language of input text

GET

/semanticSimilarity

Compute semantic similarity of two documents

GET

/api/v1/getEventForText

Identify the event that best matches input text

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Event Registry by hand means managing the `apiKey` query parameter and learning which operations are analytics versus news search across its surface. Through Jentic you install once, import the Event Registry REST API from the API Directory, store the key once, and your agent calls the operations it needs.

Permission scoping

Every Event Registry operation is a read that queries by parameters, so a rule can allow only the ones your agent needs, such as article search and sentiment analysis. There are no write or delete operations to expose, and the agent is held to the analyses you intend.

Credential isolation

Your Event Registry API key is held by your own Jentic One instance, encrypted, and injected into the query string at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'extract entities from text' or 'search recent news', and Jentic returns the matching Event Registry operation with its input schema so the agent calls the right analysis or search endpoint.

FAQs

Specific to using Event Registry REST API through Jentic.

What authentication does the Event Registry REST API use?

The Event Registry REST API authenticates with an API key passed as the `apiKey` query parameter, per its OpenAPI spec. Through Jentic the key is held by your own Jentic One instance and attached to each request at execution time, so it never appears in your agent's prompt or logs.

Can I extract entities and sentiment from text with the Event Registry API?

Yes. The API annotates text to identify people, locations, and organizations, scores sentiment, categorizes documents, and detects language. Your agent can chain these analyses, for example annotating an article and then scoring its sentiment, as separate calls.

What are the rate limits for the Event Registry REST API?

The OpenAPI spec does not specify rate limits, and Event Registry meters usage by token allowance per plan. Check the Event Registry documentation at https://eventregistry.org for the current token limits before running high-volume analysis.

Is there an Event Registry MCP server?

You do not need an MCP server to give your agent the Event Registry REST API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent discovers the analytics and news-search operations it needs on demand without loading an extra server's tool definitions into its context.

Can I limit what my agent is allowed to do with the Event Registry REST API?

Yes. Every operation here is a read, so write a rule that allows only the ones your agent needs, such as article search and sentiment analysis, and leave the rest unavailable. The agent can analyze and search but cannot change anything, and every call it makes is logged.

How do I analyze news text through Jentic?

Install the Jentic One command line with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, then add the Event Registry REST API from the Jentic directory and search by intent such as 'extract entities from an article'. Jentic returns the matching operation with its input schema so your agent builds a valid request. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Event Registry REST API

AI ReadinessNon-Ready (F)35/100

See full scorecard

Community OpenAPI document · agent-readyAI/MLMl InferenceapiKey25 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Run NLP over news text: annotate entities, score sentiment, categorize and detect language, measure semantic similarity, and search news articles and events.

Use for: Identify the people and organizations mentioned in an article, Score the sentiment of a block of text, Search for recent news articles about a topic, Retrieve the news events matching a set of conditions

Not supported: Does not publish content, send alerts, or store your own documents. Use for retrieving news articles and events and running text analytics only.

The Event Registry REST API runs text analytics over news content and retrieves the articles and events behind it. Your agent annotates text to identify people, locations, and organizations, classifies sentiment, categorizes documents, detects language, and measures semantic similarity between documents. It also searches news articles and the real-world events that group them, and resolves concept, category, source, and location names into the URIs those searches expect.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: CSignals: 4

85%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

42%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: FSignals: 4

Example Density

How richly the API is illustrated with examples.

Example Validity

Percentage of examples that conform to their schemas.

25%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

44%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

15%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1

15%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: ASignals: 1

90%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Event Registry REST API to your agent

Capabilities

Start building with Event Registry REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Event Registry REST API

Jentic AI Readiness Score

Event Registry REST API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness