How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Anaconda

Anaconda Cves API

The cves API from Anaconda — 20 operation(s) for cves.

Documentation Provider Profile APIs.io OpenAPI GitHub

Anaconda Cves API is one of 24 APIs that Anaconda publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include CVEs. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 23 operations across 20 paths, and defines 12 schemas. It is described by OpenAPI 3.2.0, at version 6.5.

Requests are made against a single base URL, https://api.anaconda.cloud/api.

23 operations 20 paths 12 schemas 20 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
6.5
Base URL
https://api.anaconda.cloud/api
Authentication
HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 2

Anaconda Cves API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (jwt). An API key is passed in the header as X-Auth (user_token).

Paths & Operations 23

Across 20 paths, the API surfaces 23 operations — 20 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

cves 23
GET
/channels/{channel_name}/cves_history
Get the cve history logs of the channel
repo.endpoints.channels.channels_cve_history.get_cve_channel_history 11 params → 200401403404500
POST
/channels/{channel_name}/cves_history
generate min-download-count-parametertory for a specific timestamp for example for existing cves history
repo.endpoints.channels.channels_cve_history.generate_cve_notifications 1 param body → 202200401403404500
GET
/channels/{channel_name}/cves
Get all the CVE's associated with this channel
repo.endpoints.channels.channel_artifacts.list_channel_cves 14 params → 200400401403500
GET
/channels/{channel_name}/cves/ws
repo.endpoints.channels.channel_artifacts.cve_report_batched 9 params → 101400
GET
/channels/{channel_name}/cves/{cve_id}
Get channel CVE details
repo.endpoints.channels.channel_artifacts.get_channel_cve_details 2 params → 200400401403500
GET
/channels/{channel_name}/cves/{cve_id}/files
Get all package files, associated with specific CVE in the channel
repo.endpoints.channels.channel_artifacts.list_channel_cve_files 6 params → 200400401403404500
GET
/channels/{channel_name}/artifacts/{artifact_family}/{artifact_name}/cves
Get all the CVE's associated with this channel and artifact
repo.endpoints.channels.channel_artifacts.list_artifact_cves 9 params → 200400401403500
GET
/channels/{channel_name}/artifacts/{artifact_family}/{artifact_name}/cves/{cve_id}
Get artifact CVE details
repo.endpoints.channels.channel_artifacts.get_artifact_cve_details 4 params → 200400401403500
GET
/channels/{channel_name}/artifacts/{artifact_family}/{artifact_name}/cves/{cve_id}/files
successfully returns routes, related to this CVE in the artifact
repo.endpoints.channels.channel_artifacts.list_artifact_cve_files 8 params → 200400401403404500
GET
/channels/{channel_name}/subchannels/{subchannel_name}/cves_history
Get the cve history logs of the subchannel
repo.endpoints.channels.subchannels_cve_history.get_cve_subchannel_history 12 params → 200401403404500
POST
/channels/{channel_name}/subchannels/{subchannel_name}/cves_history
generate cveshistory for a specific timestamp for example for existing cves history
repo.endpoints.channels.subchannels_cve_history.generate_cve_notifications 3 params → 202200401403404500
GET
/channels/{channel_name}/subchannels/{subchannel_name}/cves
Get all the CVE's associated with this subchannel
repo.endpoints.channels.subchannel_artifacts.list_subchannel_cves 15 params → 200400401403500
GET
/channels/{channel_name}/subchannels/{subchannel_name}/cves/ws
repo.endpoints.channels.subchannel_artifacts.cve_report_batched 10 params → 101400
GET
/channels/{channel_name}/subchannels/{subchannel_name}/cves/{cve_id}
Get subchannel CVE details
repo.endpoints.channels.subchannel_artifacts.get_subchannel_cve_details 3 params → 200400401403500
GET
/channels/{channel_name}/subchannels/{subchannel_name}/cves/{cve_id}/files
Get all package files, associated with specific CVE in the channel
repo.endpoints.channels.subchannel_artifacts.list_subchannel_cve_files 7 params → 200400401403404500
GET
/channels/{channel_name}/subchannels/{subchannel_name}/artifacts/{artifact_family}/{artifact_name}/cves
Get all the CVE's associated with this subchannel and artifact
repo.endpoints.channels.subchannel_artifacts.list_artifact_cves 10 params → 200400401403500
GET
/channels/{channel_name}/subchannels/{subchannel_name}/artifacts/{artifact_family}/{artifact_name}/cves/{cve_id}
Get subchannel artifact CVE details
repo.endpoints.channels.subchannel_artifacts.get_artifact_cve_details 5 params → 200400401403500
GET
/channels/{channel_name}/subchannels/{subchannel_name}/artifacts/{artifact_family}/{artifact_name}/cves/{cve_id}/files
successfully returns routes, related to this CVE in the artifact
repo.endpoints.channels.subchannel_artifacts.list_artifact_cve_files 9 params → 200400401403404500
GET
/cves
Get list of the latest CVEs
repo.endpoints.cves.list_cves 7 params → 200401403500
GET
/cves/{cve_id}
Get the CVE by its ID
repo.endpoints.cves.get_cve 1 param → 200401403404500
GET
/cves/{cve_id}/files
Get the CVE by its ID
repo.endpoints.cves.list_cve_files 5 params → 200401403404500
GET
/cves-report
Get list of the CVEs with status for provided list of packages
repo.endpoints.cves.list_cves_for_packages 2 params → 200401403500
POST
/cves-report
Get list of the CVEs with status for provided list of packages. Using Post as Get
repo.endpoints.cves.list_cves_for_packages_post_query 1 param body → 200401403500

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are CVE (16 properties), CVENotificationsHistory (9 properties), CVEPackage (9 properties), CVEsBySeverity (5 properties). Each schema is shown below with its type and property counts.

CVEPackage
object
CVE Package information
9 properties
CVENotificationsHistory
object
The object representing cve notification
9 properties
CVEsNotificationEventTypes
string
CVEsReport
object
CVE Package information
2 properties
CVENotificationChanges
array
5 properties 3 required
CVENotificationsTimestamp
object
Timestamp for Generation of CVE Notifications
1 property 1 required
ErrorResponse
object
The metadata contained in an error response
3 properties
CVE_status
string
ArtifactFamily
string
CVE
object
CVE information
16 properties
CVEsBySeverity
object
CVE counts grouped by severity based on NVD classification
5 properties
ChannelCveHistory
array
List of cve histories

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

anaconda-cves-api-openapi.yml Raw ↑

Other APIs Anaconda publishes across the network.

Anaconda.org Repository API
AE Profile APIs.io
Anaconda MCP
AE Profile APIs.io
Anaconda Account API
AE Profile APIs.io
Anaconda AI Navigator API API
AE Profile APIs.io
Anaconda Artifacts API
AE Profile APIs.io
Anaconda Audit Logs API
AE Profile APIs.io
Anaconda Auth API
AE Profile APIs.io
Anaconda Channels API
AE Profile APIs.io
Anaconda Diagnosis API
AE Profile APIs.io
Anaconda Docs API
AE Profile APIs.io
Anaconda Files API
AE Profile APIs.io
Anaconda Groups API
AE Profile APIs.io
#CVEs
← Back to A APIs
API Details
ID
anaconda:anaconda-cves-api
Base URL
https://api.anaconda.cloud/api
Docs
https://anaconda.com/docs/anaconda-platform/main
Provider
Anaconda
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=anaconda-cves-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/anaconda-cves-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Anaconda Cves API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.