Install Jentic One Beta

Connect the AIS API: CVE intelligence + Agent Flight Recorder to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AIS API: CVE intelligence + Agent Flight Recorder, 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%2Faislabs.ai%2Faislabs" | 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%2Faislabs.ai%2Faislabs" | 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 AIS API: CVE intelligence + Agent Flight Recorder API.

Rank today's CVEs by real-world exploitation using KEV, EPSS, and KEV-recency signals

Pull a single CVE's verdict and priority from today's ranked set

List KEV additions from the last seven days with their current ranks

Retrieve a historical daily brief for any past date

GET STARTED

Start building with AIS API: CVE intelligence + Agent Flight Recorder API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use AIS API: CVE intelligence + Agent Flight Recorder API for, with concrete tasks.

★ AI agent CVE triage

A security agent needs grounded, exploitation-aware CVE priorities instead of raw severity scores. Through Jentic the agent searches for today's ranked CVE priorities, the matching AIS operation is loaded with the credential already injected, and the agent returns a ranked list driven by KEV membership, EPSS, and KEV-recency. The agent never has to reconstruct the ranking logic itself.

Call GET /v1/brief/today and return the five highest-ranked CVEs with their KEV and EPSS signals

Daily vulnerability prioritization

A vulnerability-management workflow pulls the day's ranked brief and the fresh KEV additions each morning to decide what to patch first. AIS regenerates its ranking daily from CISA KEV membership, EPSS probability, and how recently a CVE was added to KEV, so the list reflects active exploitation rather than static CVSS. This replaces manually cross-referencing several public feeds.

Call GET /v1/kev/fresh and flag any new KEV entry that also appears in the top of GET /v1/brief/today

Single CVE lookup during an incident

During incident response an analyst asks whether one specific CVE is being exploited and how it ranks today. The agent resolves the identifier against today's ranked set and returns the verdict, so the responder gets a prioritization answer for that CVE without opening a dashboard. Historical briefs let the agent show how the same CVE ranked on an earlier date.

Call GET /v1/cve/CVE-2024-3400 and report whether it is in today's ranked set and its KEV status

Agent liveness monitoring

A long-running agent registers a Flight Recorder monitor and sends periodic heartbeats so a controller can tell when it has stalled. A key-owned monitor can store a state capsule on each heartbeat, letting a replacement agent resume from the last recorded state rather than starting over. Free monitors deliver webhook alerts; a Flight Recorder key adds stored capsules and more monitors.

Call POST /v1/recorder/monitors to register a monitor, then POST /v1/recorder/beat/{id}/{secret} with a state capsule on each cycle

Key Endpoints

12 endpoints — the ais api ranks the day's cves by real-world exploitation, combining cisa kev membership, epss probability, and kev-recency into a single priority list that is regenerated daily.

METHOD

PATH

DESCRIPTION

GET

/v1/brief/today

Get today's full ranked CVE priorities

GET

/v1/kev/fresh

List KEV additions from the last seven days with today's ranks

GET

/v1/cve/{cve_id}

Get a single CVE's verdict from today's ranked set

GET

/v1/archive/{date}

Retrieve a historical daily brief by date

POST

/v1/recorder/monitors

GET

/v1/recorder/capsule/{id}

Read the last stored state capsule of a key-owned monitor

GET

/v1/brief/today

Get today's full ranked CVE priorities

GET

/v1/kev/fresh

List KEV additions from the last seven days with today's ranks

GET

/v1/cve/{cve_id}

Get a single CVE's verdict from today's ranked set

GET

/v1/archive/{date}

Retrieve a historical daily brief by date

POST

/v1/recorder/monitors

GET

/v1/recorder/capsule/{id}

Read the last stored state capsule of a key-owned monitor

Why Jentic?

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

Setup

Wiring the AIS API by hand means choosing between its x402 pay-per-call payment header and a Gateway bearer key, scoping keys per building, and passing the right one on every ranked-brief call. Through Jentic you install once, import AIS from the API Directory, store the key once, and your agent calls it.

Permission scoping

The AIS API is read-first: today's brief, fresh KEV, single-CVE verdicts, and the archive are lookups, while the Flight Recorder adds monitor registration and deletion. You choose the operations your agent may call, so you can allow the ranked-brief and single-CVE reads and leave monitor deletion out unless you add it.

Credential isolation

Your AIS Gateway 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 'rank today's CVEs' or 'check if a CVE is exploited', and Jentic returns the matching AIS operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using AIS API: CVE intelligence + Agent Flight Recorder API through Jentic.

What authentication does the AIS API use?

Paid endpoints accept either an x402 payment payload in the X-PAYMENT header (pay-per-call in USDC on Base) or a Gateway bearer key sent as Authorization: Bearer, per the OpenAPI spec. The free teaser, the recorder index, and the heartbeat endpoints need no credential at all. Through Jentic the Gateway key is injected at call time, so the agent only sees the operation it is allowed to run.

Can I check whether a specific CVE is being actively exploited?

Yes. Call GET /v1/cve/{cve_id} with the CVE identifier and AIS returns that CVE's verdict from today's ranked set, including its KEV membership and relative priority. If the CVE is not in the current ranked set the response says so, which is itself a signal that it is not among the actively exploited priorities today.

What are the rate limits for the AIS API?

The OpenAPI spec does not define request-rate ceilings. Access is metered instead by the credential you use: x402 is billed per successful call, while Gateway keys are scoped per building and valid for a fixed window. Check the AIS developer documentation for the quota that applies to your key before scripting bulk historical pulls.

Is there an AIS API MCP server?

You don't need an MCP server to give your agent the AIS API. Jentic connects it directly from the API Directory: import the API, store your Gateway key once, and your agent calls operations such as GET /v1/brief/today on demand. Nothing extra loads into the agent's context until it actually needs an operation.

Can I limit what my agent is allowed to do with the AIS API?

Yes. Write a rule that allows only the ranked-brief read and the single-CVE verdict lookup, so the agent can pull today's priorities and inspect one CVE but cannot register or delete Flight Recorder monitors, and every call it makes is logged. You decide which operations are in the allowed set.

Does the AIS API cover historical CVE data?

Yes. Call GET /v1/archive/{date} with a date in YYYY-MM-DD form to retrieve the daily ranked brief as it stood on that day. This lets an agent show how a CVE's priority has moved over time rather than only its status today.

How do I get today's ranked CVE priorities through Jentic?

Search Jentic for 'get today's ranked CVE priorities', load the GET /v1/brief/today operation, and run it after your Gateway key is stored. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Aislabs AIS API: CVE intelligence + Agent Flight Recorder

AI ReadinessFoundational (D)45/100

See full scorecard

Official vendor OpenAPI document · agent-readySecurityVulnerability ManagementapiKey, bearer12 EndpointsREST

For Agents

Rank today's CVEs by real-world exploitation, look up a single CVE's verdict, and track agent heartbeats through the AIS API's Flight Recorder.

Use for: Get today's top ranked CVE priorities, Check whether a specific CVE is being actively exploited, List the KEV entries added in the last week, Retrieve the archived CVE brief for a past date

Not supported: Does not scan your own network, apply patches, or manage vulnerability tickets. Use for ranked CVE intelligence and agent heartbeat monitoring only.

The AIS API ranks the day's CVEs by real-world exploitation, combining CISA KEV membership, EPSS probability, and KEV-recency into a single priority list that is regenerated daily. It returns today's full ranked brief, the KEV additions from the last seven days, a verdict for any single CVE, and historical daily briefs by date. A companion Agent Flight Recorder registers heartbeat monitors and stores state capsules so a stopped agent can resume from where it left off.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

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: C+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

35%

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

40%

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.

52%

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: CSignals: 1

55%

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: FSignals: 1

36%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the AIS API: CVE intelligence + Agent Flight Recorder to your agent

Capabilities

Start building with AIS API: CVE intelligence + Agent Flight Recorder API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Aislabs AIS API: CVE intelligence + Agent Flight Recorder

Jentic AI Readiness Score

AIS API: CVE intelligence + Agent Flight Recorder

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