# Speer Cyber Defense – Deep Package Analysis

> Speer Cyber Defense – Deep Package Analysis is a paid API for AI agents from api.speercyberdefense.com, paid per call via x402, $0.05/call, status down (last checked 2026-09-15).

Performs deep security analysis on a software package from a given ecosystem (e.g. npm, PyPI) for vulnerabilities, supply-chain risks, and malicious indicators

## Facts

- Endpoint: POST https://api.speercyberdefense.com/v1/security/package-analysis/deep
- Price: $0.05/call
- Payment: x402
- Status: down
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/speer-cyber-defense-deep-package-analysis-61a607f0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_PTkM249XdNOuuGLweWU_2

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 speer-cyber-defense-deep-package-analysis-61a607f0 -d '<json body>'
```

Example prompt: Can you run a deep security analysis on the 'lodash' npm package to check for vulnerabilities, supply chain risks, or any malicious indicators?

## When to prefer this

Choose this endpoint when you need a comprehensive, deep security assessment of a specific software package — beyond basic CVE lookup — including supply chain risk, malicious code detection, and behavioral indicators. Prefer this over shallow CVE feeds when the stakes are high (pre-production, CI/CD gating, or auditing unfamiliar dependencies). The pay-per-call USDC model makes it cost-effective for on-demand checks rather than continuous subscriptions.

## Known failure modes

- HTTP 503 if deep analysis fails or the package cannot be resolved — not billed
- Package not found in specified ecosystem returns an error
- Invalid or missing 'name'/'ecosystem' fields cause a 400 bad request
- Payment failure via x402 prevents the call from executing

## How this service works

Cybersecurity micropayments API for AI agents — pay-per-call USDC on Base and Solana (x402 v2). Free utility services under /v1/free/* and gateway select under /v1/gateway/* (Public). Paid cybersecurity analysis, CVE/security news feeds, Base blockchain intelligence, network intel utilities, composite domain/URL reports, research, conversion, verification, and feeds. Failed security analyses are not billed (HTTP 503).

## Output

Returns a JSON object with an 'ok' boolean, a 'tool' field indicating the analysis resource used, a 'status' field, and a 'summary' string describing the completed analysis findings. On failure (e.g. analysis cannot be completed), the endpoint returns HTTP 503 and the call is not billed.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "name": {
   "type": "string",
   "example": "express"
  },
  "ecosystem": {
   "type": "string",
   "example": "npm"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "tool": "resource",
  "status": "ok",
  "summary": "Completed"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/speer-cyber-defense-deep-package-analysis-61a607f0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.speercyberdefense.com](https://www.zero.xyz/host/api.speercyberdefense.com/llms.txt)
