Back to Browse
npm Registry Package Lookup
x402
npm Registry Package Lookup is a paid API for AI agents from api.companyrecords-api.workers.dev, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-24).
Fetches public metadata for a single npm package by exact name: latest version, license, description, homepage, repository, and tarball URL.
Price / call$0.002
Success—
StatusUnknown
How this service works
Pay-per-call company registry, government, legal and B2B data tools for AI agents, from official registers and public sources. Payment: x402, USDC on Base, Solana, Arc, Polygon, Arbitrum, Monad, World Chain, Optimism, Avalanche, Celo or Stellar, or RLUSD/XRP on the XRP Ledger. No signup, no API key; a failed call is not charged.
Output
A JSON object containing the package's name, latest version number, SPDX license identifier, short description, homepage URL, git repository URL, tarball download URL for the latest release, and the timestamp when the record was checked.
Example use cases
Check open source license compliance
“What license does the 'lodash' npm package use? I need to verify it's MIT-compatible before adding it to our project.”
Find latest published package version
“What's the latest version of '@babel/core' on npm right now? I want to make sure our CI is pinning to the current release.”
Retrieve package repository for auditing
“Can you pull the npm registry record for 'express' and give me its GitHub repository URL and homepage so I can review the source?”
Technical details
Endpoint
GEThttps://api.companyrecords-api.workers.dev/api/gov/npm-registry?utm_source=zero.xyzWhen to prefer
Use this endpoint when you need lightweight, read-only npm package metadata (version, license, homepage, repo) without downloading the tarball or pulling download statistics. Prefer it over scraping npmjs.com directly or calling the raw npm registry API when you want a structured, pay-per-call response with no auth setup. Not suitable if you need download counts, historical versions, all package versions, or package vulnerability data.
Side effects
- Package not found — returns an error if the exact package name does not exist on npm
- Scoped package name must be URL-encoded or passed correctly (e.g. @scope/name)
- Package name exceeds 214 characters — schema rejects overly long names
- Network or upstream npm registry outage — may return a 5xx or timeout
- Stale data — checkedAt timestamp may lag real-time npm registry state slightly
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| inputrequired | object | |
| output | object |
Output
Schema · Response
{
"type": "json",
"example": {
"name": "lodash",
"source": "https://registry.npmjs.org/lodash/latest",
"license": "MIT",
"tarball": "https://registry.npmjs.org/lodash/-/lodash-4.18.1.tgz",
"homepage": "https://lodash.com/",
"checkedAt": "2026-10-23T09:37:21.512Z",
"repository": "git+https://github.com/lodash/lodash.git",
"description": "Lodash modular utilities.",
"latestVersion": "4.18.1"
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"