# Strale NPM Package Info

> Strale NPM Package Info is a paid API for AI agents from api.strale.io, paid per call via x402, $0.054/call, status unknown (last checked 2026-09-15).

Fetches metadata and details for a given npm package by name

## Facts

- Endpoint: GET https://api.strale.io/x402/v2/npm-package-info
- Price: $0.054/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/strale-npm-package-info-5ae578d1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_nB-0rY9PnbsS25W0KrnHn

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 strale-npm-package-info-5ae578d1
```

Example prompt: Can you look up the npm package info for 'lodash' — I want to know its latest version, license, and who maintains it?

## When to prefer this

Choose this endpoint when you need verified, audit-trailed npm package metadata within an automated agent pipeline — especially in compliance, supply chain security, or due diligence contexts where cryptographic audit records matter. Prefer this over direct npm registry calls when you need structured JSON with provenance guarantees or when operating in regulated environments. Also useful when aggregating package data across many lookups with consistent response schemas.

## Known failure modes

- Package not found: returns error if the package name does not exist on npm
- Invalid package name format: malformed package identifiers may be rejected
- npm registry unavailable: upstream failures may cause timeouts or 5xx responses
- Missing required query parameter: omitting 'package' parameter results in a validation error

## How this service works

The trust layer for AI agents — 250+ independently tested data capabilities across 27 countries. Execute capabilities via REST, MCP, A2A, or x402 micropayments. Every call returns an audit record with cryptographic chain hashing.

## Output

Returns structured metadata for the requested npm package, including package name, description, latest version, all published versions, license type, author, maintainers, repository URL, homepage, dependencies, keywords, and publish timestamps. Each call also includes a Strale audit record with a cryptographic chain hash for provenance tracking.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "package"
     ],
     "properties": {
      "package": {
       "type": "string"
      }
     }
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/strale-npm-package-info-5ae578d1/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.strale.io](https://www.zero.xyz/host/api.strale.io/llms.txt)