Install Jentic One Beta

Connect the AI Act Radar API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AI Act Radar 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%2Faiactradar.com%2Faiactradar" | 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%2Faiactradar.com%2Faiactradar" | 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 AI Act Radar API.

Query EU AI Act regulatory events and read a single event by its id

List the available topics and the active data sources behind the feed

Create a webhook subscription to receive new AI Act updates

List and delete your webhook subscriptions

Check the data pipeline's health status

GET STARTED

Start building with AI Act Radar API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use AI Act Radar API for, with concrete tasks.

★ Agent-Monitored AI Act Updates

An AI agent connecting through Jentic can keep a compliance watch running: it queries events for new EU AI Act activity and reads any event in full by its id. Jentic injects the bearer token at call time and returns each operation's input schema, so the agent polls the feed without holding the credential in its prompt.

Query the events endpoint for recent AI Act activity, then read any new event by its id and summarise it for the user

Webhook Update Subscriptions

Receive EU AI Act updates as they publish instead of polling. The AI Act Radar API creates a webhook subscription that delivers new events to your endpoint, and lists or deletes existing subscriptions so an agent can manage which updates it listens for across the available topics and sources.

Create a webhook subscription for a chosen topic, then list subscriptions to confirm it is active

Event Query and Lookup

Pull and inspect specific regulatory events for a report. The AI Act Radar API queries events across topics and returns a single event by id, with the topics and sources endpoints describing what the feed covers, so an agent can assemble a grounded summary of recent EU AI Act activity with its sources named.

List the available topics, query events for one topic, and read a selected event by its id for a briefing

Key Endpoints

9 endpoints — the ai act radar api is a structured json and webhook feed of eu ai act regulatory updates.

METHOD

PATH

DESCRIPTION

GET

/v1/events

Query regulatory events

GET

/v1/events/{id}

Read a single event by id

GET

/v1/topics

List available topics

GET

/v1/sources

List active data sources

POST

/v1/subscriptions

Create a webhook subscription

DELETE

/v1/subscriptions/{id}

Delete a subscription

GET

/v1/health

Report pipeline health

GET

/v1/events

Query regulatory events

GET

/v1/events/{id}

Read a single event by id

GET

/v1/topics

List available topics

GET

/v1/sources

List active data sources

POST

/v1/subscriptions

Create a webhook subscription

DELETE

/v1/subscriptions/{id}

Delete a subscription

GET

/v1/health

Report pipeline health

Why Jentic?

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

Setup

Wiring the AI Act Radar API by hand means handling its bearer token issued at onboarding, tier-based rate limits, and webhook subscription wiring yourself. Through Jentic you install once, import AI Act Radar from the API Directory, store the token once, and your agent calls it.

Permission scoping

You choose which AI Act Radar operations your agent may call, so it can query events, topics, and sources while creating or deleting a subscription stays out unless you add it. Event and subscription ids travel in the URL path, so a rule can also pin reads to a single event.

Credential isolation

Your AI Act Radar token 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 'query AI Act events' or 'subscribe to updates', and Jentic returns the matching AI Act Radar operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using AI Act Radar API through Jentic.

What authentication does the AI Act Radar API use?

The AI Act Radar API authenticates with a bearer token issued at customer onboarding per its OpenAPI spec. A few endpoints, such as pipeline health and the topic and source listings, need no token. Through Jentic the token is injected at call time rather than living in the agent's prompt or logs.

Can I receive EU AI Act updates by webhook with the AI Act Radar API?

Yes. You create a webhook subscription that delivers new events to your endpoint as they are published, and you can list your subscriptions or delete one to stop a soft-disabled feed. This is the push alternative to polling the events query endpoint.

What are the rate limits for the AI Act Radar API?

The spec notes that tier-based rate limits apply but does not publish the numbers. Check the AI Act Radar documentation at https://docs.aiactradar.com for the current limits for your tier before running a high-frequency poll.

How do I monitor AI Act updates with the AI Act Radar API through Jentic?

Search Jentic for 'query AI Act events' and it returns the events operation with its input schema. Your agent queries recent events, reads any event by its id, and can create a webhook subscription for new updates. 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 AI Act Radar API?

Yes. Write a rule that allows only the events, topics, and sources read operations, so the agent can monitor updates while creating or deleting a subscription stays out unless you add it, and every action it takes is logged. Because event and subscription ids appear in the URL path, a rule can also pin reads to a single event.

Is there an AI Act Radar MCP server?

You don't need an MCP server to give your agent the AI Act Radar API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the events, topics, and subscription operations on demand without loading another server's tool definitions into its context.

AI Act Radar API

AI ReadinessNon-Ready (F)40/100

See full scorecard

Official vendor OpenAPI document · agent-readySecurityCompliancebearer9 EndpointsREST

For Agents

Query EU AI Act regulatory events, browse topics and sources, and create webhook subscriptions that push new updates as they are published.

Use for: Query recent EU AI Act regulatory events, Get a specific AI Act update by its id, List the topics I can subscribe to, Create a webhook to receive AI Act updates

Not supported: Does not provide legal advice, compliance certification, or regulatory filing. Use for monitoring EU AI Act regulatory updates through its event feed and webhooks only.

The AI Act Radar API is a structured JSON and webhook feed of EU AI Act regulatory updates. It lets you query events, read a single event by id, and browse the topics and active data sources behind the feed. Webhook subscriptions deliver new updates as they are published, and a health endpoint reports pipeline status. It is an information service, not legal advice: it reports regulatory activity rather than certifying compliance.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: B+Signals: 4

94%

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

75%

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: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

39%

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

15%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

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

53%

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: B-Signals: 1

60%

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: B-Signals: 1

62%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the AI Act Radar API to your agent

Capabilities

Start building with AI Act Radar API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

AI Act Radar API

Jentic AI Readiness Score

AI Act Radar 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