Pay-per-request registry evidence for coding agents

Stable facts.
Not opinions.

Give an agent an npm package name. Get a stable, citation-ready evidence record built from public registry metadata — license, dependencies, distribution integrity, provenance, and factual flags — in a single JSON response.

$0.003per successful request
USDCBase or Solana over x402
No accountno API key or subscription
request.json
01 — Request
POST /v1/npm/evidence
content-type: application/json

{
  "package": "@x402/core",
  "version": "latest"
}
02 — Evidence
{
  "requestId": "…",
  "resolvedVersion": "2.19.0",
  "license": "MIT",
  "repositoryUrl": "git+https://…",
  "distribution": {
    "integrity": "sha512-…",
    "signatureCount": 1,
    "attestationUrl": null
  },
  "flags": ["provenance_attestation_missing"],
  "limitations": ["…"],
  "digests": { "input": "…", "result": "…" }
}
Unpaid requests return discoverable x402 payment requirements. Invalid input and upstream registry failures are not settled.
Resource

One operation.
One clean interface.

1Call

Send the package name and optional version.

2Pay

Your client signs the x402 requirement.

3Cite

Use the stable digest as a decision citation.

DESIGNED FOR MACHINES

Facts an agent can cite, not a verdict.

01

Facts, not scores. Every flag is a deterministic observation about published metadata — never a safety, trust, or quality rating.

02

Pay only on success. x402 settlement happens after a valid response. Invalid input and unavailable upstream records return errors without settlement.

03

Stable citations. Canonical SHA-256 digests let an agent reference this exact evidence later without re-fetching it.

Limitations

What this API does not claim.