# node-fetch NPM Package Runtime and Platform Constraints

> node-fetch NPM Package Runtime and Platform Constraints 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-16).

Returns runtime and platform constraints metadata for the npm package node-fetch, useful for integration and upgrade planning.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/signal-npm-node-fetch-runtime-constraints?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/node-fetch-npm-package-runtime-and-platform-constraints-38ac7641
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wAC4Oyd0aR7vZdJxu61f7

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 node-fetch-npm-package-runtime-and-platform-constraints-38ac7641 -d '<json body>'
```

Example prompt: What are the runtime and platform constraints for node-fetch version 3.3.2 on npm — things like supported Node.js versions and OS compatibility?

## When to prefer this

Choose this endpoint when you need structured runtime and platform constraint data specifically for the node-fetch npm package — particularly during dependency audits, CI environment setup, or upgrade planning — and want a fast, programmatic lookup rather than manually parsing npm registry pages.

## Known failure modes

- Invalid or non-existent package version returns an error or empty result
- Package name override to a non-existent npm package returns not found
- Malformed version string may cause lookup failure
- Registry upstream unavailability may cause timeouts or errors

## How this service works

node-fetch Runtime and platform constraints: Runtime and platform constraints for npm package node-fetch. Inspect registry metadata for integration and upgrade planning. Package and version can be overridden.

## Output

Returns registry metadata describing the runtime and platform constraints for the specified node-fetch package version, including supported Node.js engine versions, operating system compatibility, and any other platform-level requirements needed for integration and upgrade planning.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "package": {
   "type": "string",
   "default": "node-fetch",
   "maxLength": 150
  },
  "version": {
   "type": "string",
   "maxLength": 100
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/node-fetch-npm-package-runtime-and-platform-constraints-38ac7641/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)