# Express npm Package Release History

> Express npm Package Release History 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-02).

Fetches the recent release history of the Express npm package (or any specified npm package) from the live npm registry.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/demand-next-package-npm-express-release-history?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/express-npm-package-release-history-fa1d14ef
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_IcSlVqk3ug2bQldn5F47z

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 express-npm-package-release-history-fa1d14ef -d '<json body>'
```

Example prompt: Can you pull up the recent release history for the Express npm package so I can see what versions have been published lately?

## When to prefer this

Use this endpoint when you need up-to-date, live npm registry release history for Express or any other npm package, especially when you want recent version timelines without scraping npm yourself. Prefer this over manual npm API calls when operating in an agent workflow that supports x402 micropayments.

## Known failure modes

- Package name not found on npm registry — returns an error or empty result
- npm registry unreachable or rate-limited — request timeout or upstream error
- Invalid package name format — validation error
- Payment not processed correctly — 402 response if x402 payment header is missing or insufficient

## How this service works

Express Recent release history: Live npm Registry recent release history for Express. Package name can be overridden.

## Output

Returns a list of recent releases for the specified npm package (defaulting to 'express'), including version numbers and publication dates sourced directly from the live npm registry.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "package": {
   "type": "string",
   "default": "express",
   "description": "Package name to inspect."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/express-npm-package-release-history-fa1d14ef/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)