Skip to content
All APIs

Web & Search · 1 endpoint

npm Package

One npm package's registry record — description, license, links, dependency counts, and the tarball's checksum, at any version or `latest`.

Status
Operational
Price
1 credit / request
Rate limit
120 / 60s
Cache
5m
Requests
0

Endpoint

How to call it

GET/v1/packages/npm

Code

Request — cURL

v1

curl https://api.diraz.co.id/v1/packages/npm \
  -H "Authorization: Bearer drz_live_…"

For AI agents

Callable through the MCP server with the same key:

call_api {"endpoint":"npm-package","params":{"package":"next","version":"latest","max_age":"60"}}

Parameters

packagestring · required
A package name — scoped names work too.
versionstring · optional
A version string.Default: latest
max_ageinteger (seconds) · optional
Ask for data no older than this. Clamped to the product's own floor, so it can narrow the window but never force a refresh on every call.Default: 300

Example response

200 OK

JSON

{
  "data": {
    "name": "next",
    "version": "16.3.1",
    "description": "The React Framework.",
    "license": "MIT",
    "homepage": "https://nextjs.org",
    "repository": "git+https://github.com/vercel/next.js.git",
    "keywords": ["react", "framework"],
    "dependencies": 6,
    "dev_dependencies": 0,
    "peer_dependencies": 4,
    "unpacked_size_bytes": 31457280,
    "file_count": 512,
    "shasum": "dfa0034dd721991bfc2399f1185ad8cda012504a",
    "tarball": "https://registry.npmjs.org/next/-/next-16.3.1.tgz",
    "maintainers": ["vercel-release-bot"],
    "url": "https://www.npmjs.com/package/next"
  },
  "meta": {
    "request_id": "req_7Q2fK4mZ",
    "as_of": "2026-08-20T16:30:00.000Z",
    "age_seconds": 60,
    "next_update_at": "2026-08-20T16:35:00.000Z"
  }
}
name / version / description / license
The package's identity and terms.
dependencies / dev_dependencies / peer_dependencies
How many of each kind it declares.
unpacked_size_bytes / file_count / shasum / tarball
The tarball's weight, contents, checksum, and download URL.
keywords / homepage / repository / maintainers
The package's own links, labels, and keepers.

Errors

When something goes wrong

Every failure carries a stable machine-readable code and the same meta.request_id a success carries — quote it and we can find your request. Errors are never billed.

401 Unauthorized

JSON

{
  "error": {
    "code": "UNAUTHORIZED",
    "message": "The API key is invalid, expired, or revoked."
  },
  "meta": {
    "request_id": "req_7Q2fK4mZ"
  }
}
UNAUTHORIZEDHTTP 401
Missing, malformed, expired, or revoked API key.
FORBIDDENHTTP 403
The key is valid but lacks the scope this product needs.
VALIDATION_ERRORHTTP 422
A query parameter is the wrong type or out of range.
RATE_LIMITEDHTTP 429
Rate limit exhausted. `Retry-After` says how long to wait.
SERVICE_UNAVAILABLEHTTP 503
No data recent enough to serve. Carries `Retry-After`, and is never billed.

Data freshness

Every response is timestamped

as_of is when the data was published, age_seconds how old it is now, and next_update_at when newer data is expected.

  • Up to date

    200

    Inside its published window. Almost every request.

  • Delayed

    delayed: true

    Newer data is late; you get the latest there is, flagged.

  • Unavailable

    503

    Nothing recent enough. Carries Retry-After, never billed.

Health

Is it up?

  • npm Package

1/1 passing