canonical: https://jentic.com/apis/aislabs.ai/aislabs

# Aislabs AIS API: CVE intelligence + Agent Flight Recorder

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.

## For AI 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.

## Scope

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

## Capabilities

- 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
- Register agent heartbeat monitors and store state capsules so a stopped agent can resume

## Use cases

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

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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

| 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` | Register an agent heartbeat monitor |
| GET | `/v1/recorder/capsule/{id}` | Read the last stored state capsule of a key-owned monitor |

## Key resources

- **CVE Briefs** — Today's full ranked brief, fresh KEV additions, single-CVE verdicts, and historical daily briefs by date
- **Agent Flight Recorder** — Register monitors, send heartbeats, store and read state capsules, and list monitors owned by a key

## AI readiness

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.

- **Score:** 45 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 59 / 100
  - AI-Readiness & Agent Experience: 23 / 100
  - Agent Usability: 94 / 100
  - Security: 55 / 100
  - AI Discoverability: 36 / 100
- **View full report:** https://jentic.com/apis/aislabs.ai/aislabs/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Snyk API** — Scans your own code and dependencies for known vulnerabilities rather than ranking the global CVE feed by exploitation
- **Shodan** — Finds internet-exposed hosts and services that a high-priority CVE might affect
- **AbuseIPDB** — Checks IP addresses against a crowd-sourced abuse and threat database

## FAQ

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