# npm Package Lookup

> npm Package Lookup is a paid API for AI agents from the-stall.intuitek.ai, paid per call via x402, $0.007/call, status unknown (last checked 2026-09-14, last successful call 2026-07-09).

Retrieves metadata and version details for a given npm package, optionally for a specific version.

## Facts

- Endpoint: GET https://the-stall.intuitek.ai/cap/npm-lookup
- Price: $0.007/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Last successful call: 2026-07-09
- Success rate: 100% of calls made through Zero
- Activations on Zero: 1
- Tags: x402
- Canonical page: https://www.zero.xyz/c/npm-package-lookup-0b009f60
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_zPFA1wChsnSHcBOofT5JB

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 npm-package-lookup-0b009f60
```

Example prompt: What's the latest stable version of the 'express' npm package, and can you give me its description, license, and main dependencies?

## When to prefer this

Use this endpoint when an agent needs to resolve npm package metadata, check latest or specific versions, retrieve dependency lists, or validate package existence — particularly in keyless, accountless x402 pay-per-call contexts where no npm API token is available.

## Known failure modes

- Package not found — returns error if the package name doesn't exist on npm registry
- Version not found — returns error if the specified version doesn't exist for the package
- Invalid package name format — malformed names may return a validation error
- Payment failure — USDC payment on Base mainnet not confirmed, request rejected with 402

## How this service works

Node.js / JavaScript package metadata from the npm registry. Returns latest version, description, license, keywords, direct dependencies, weekly download count, publish date, GitHub repository, and all recent versions. Also supports looking up a specific version. Use before adding an npm package as a dependency: verify it's maintained, check its license, assess how many dependencies it pulls in. Free upstream: npm registry API (no key, public).

## Output

Returns npm package metadata including version number, description, author, license, homepage, dependencies, and release date. For a specific version query, returns details scoped to that version. Supports scoped packages like @scope/name.

## Example request

```json
{
 "input": {
  "type": "http",
  "method": "GET",
  "queryParams": {
   "package": "express"
  }
 }
}
```

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "required": {
   "type": "string"
  },
  "properties": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/npm-package-lookup-0b009f60/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from the-stall.intuitek.ai](https://www.zero.xyz/host/the-stall.intuitek.ai/llms.txt)