# pydantic Advisory Severity Breakdown (PyPI / OSV)

> pydantic Advisory Severity Breakdown (PyPI / OSV) is a paid API for AI agents from market.datapackvibe.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-21).

Returns a breakdown of open-source vulnerability advisory severities for a specific version of the PyPI package pydantic, sourced from the OSV database.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/signal-osv-pypi-pydantic-severity?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pydantic-advisory-severity-breakdown-pypi-osv-5781637b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_UC681B2KFqzTOk2rKGvrc

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability pydantic-advisory-severity-breakdown-pypi-osv-5781637b -d '<json body>'
```

Example prompt: What's the advisory severity breakdown for pydantic version 2.5.3 according to OSV — how many critical, high, medium, and low vulnerabilities are there?

## When to prefer this

Use this endpoint when you specifically need OSV-sourced advisory severity data for the pydantic PyPI package. It is pre-scoped to pydantic, making it faster and simpler than a general OSV lookup. Prefer this over a generic vulnerability API when your workflow only concerns pydantic and you want structured severity counts without building a full OSV query.

## Known failure modes

- Unknown or invalid version string returns no advisories or an error
- 'latest' resolution may lag if the PyPI registry is slow to respond
- Pagination required for packages with many advisories — use page_token
- OSV data may not include very recently published advisories
- Package name field is fixed to 'pydantic'; other packages return irrelevant or no data

## How this service works

pydantic Advisory severity breakdown: Advisory severity breakdown for PyPI package pydantic, from OSV. Accepts an exact version; latest resolves the registry version. Scope is the named package only.

## Output

A severity-classified breakdown of open-source security advisories for the specified pydantic version from the OSV database, including counts or listings by severity level (e.g. CRITICAL, HIGH, MEDIUM, LOW). Covers only the pydantic package itself.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "package": {
   "type": "string",
   "default": "pydantic",
   "maxLength": 150
  },
  "version": {
   "type": "string",
   "default": "latest",
   "maxLength": 100
  },
  "page_token": {
   "type": "string",
   "maxLength": 4000
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/pydantic-advisory-severity-breakdown-pypi-osv-5781637b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from market.datapackvibe.com](https://www.zero.xyz/host/market.datapackvibe.com/llms.txt)