Back to Browse
Suverse NPM Package Metadata Lookup
x402
Suverse NPM Package Metadata Lookup is a paid API for AI agents from proxy.suverse.io, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-14).
Fetches the latest npm package metadata including version, license, homepage, repository, dependencies, and dist integrity hash for a given package name.
Price / call$0.05
Success—
StatusUnknown
How this service works
Latest npm package metadata from the npm registry: version, license, homepage, repository, dependencies and dist integrity hash. Pass a package name. Keyless.
Output
Returns a JSON object containing the latest npm package metadata: version string, SPDX license identifier, homepage URL, repository URL, a map of runtime and dev dependencies with their version ranges, and the dist integrity hash (e.g. sha512 checksum) for the published tarball.
Example use cases
Auditing open source licenses
“Can you pull the npm metadata for 'axios' and tell me what license it uses and who maintains its repository?”
Checking dependency tree before install
“Before I install 'express' in my project, can you fetch its latest npm metadata so I can see its current dependencies and version?”
Verifying package integrity hash
“Can you get the dist integrity hash for the latest version of 'react' from the npm registry so I can verify it against what I have locally?”
Technical details
Endpoint
POSThttps://proxy.suverse.io/v1/data/suverse-npm-packageWhen to prefer
Choose this endpoint when you need quick, keyless access to npm registry metadata for a single package without setting up npm registry API credentials. It is ideal for agent workflows that need to audit licenses, verify integrity hashes, inspect dependencies, or validate package versions on-the-fly. Prefer it over direct npm registry calls when operating in an x402 payment-gated environment or when API key management is not desired.
Side effects
- Package name not found in the npm registry — returns an error or empty response
- Malformed or missing package name input causes a 400-level error
- npm registry upstream timeout or unavailability causes a 5xx error
- Package exists but has no published versions — metadata fields may be null or absent
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| inputrequired | object | |
| output | object |
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"