NuGet Registration Listing & Deprecation Evidence API

Read nuget.org public V3 service index, discover the SemVer2 registration resource, and locate one exact version in its registration index/page. Registration leaf URLs are not guessed and historical catalog blobs are not substituted for current registration metadata. At most one service-index request per run plus one index and, if needed, one selected page per package. Only HTTPS api.nuget.org links scoped to the discovered package registration path are followed. Validate package identity, normalized version, registration counts and unique matching version. The supported input version grammar is a normalized three-component SemVer without build metadata, plus optional valid prerelease identifiers; four-component/unnormalized legacy versions are rejected. Select nullable explicit listed status, deprecation reasons/message/alternate package declaration, license expression, minimum client, published timestamp and up to sixty target framework declarations. Missing listed/deprecation fields are unknown source omissions, not independent proof of support or safety. Do not execute alternate-package recommendations or resolve dependency ranges. No nupkg download, authors/owners, downloads statistics, package installation, dependency solving, exploit data or package safety verdict. Page coverage only concerns locating the requested exact version, not inventorying every version.

Input example

{
  "packageVersions": [
    "newtonsoft.json@13.0.3",
    "dapper@2.1.66"
  ],
  "maxResults": 2
}

Outputs and change comparison

One saved observation is one dataset row with itemKey, sourceUrl, contentHash and observedAt. The SHA256 covers only selected semantic fields; retrieval times, API request URLs, download/popularity counters and people are excluded. Copy SNAPSHOT.previousHashes into the next input to compare the same exact watchlist. Statuses are NO_BASELINE, FIRST_SEEN, UNCHANGED or CHANGED. Unchanged observations are still billable. There is no hidden persistent baseline and no missing-row/deletion inference. OUTPUT records actual requestCount, rowsEmitted, source summaries, errors, status and complete. SNAPSHOT.complete is false after any error or when any requested observation could not be delivered. Reaching the selected result cap is PARTIAL_RESULT_CAP; a monetary budget stop is PARTIAL_BUDGET. Provider restrictions produce PARTIAL_PROVIDER_LIMIT. A saved observation means successful metadata extraction only, not that the declared package state is good or safe.

Pricing and bounded work

$0.005 startup plus $0.001 per saved observation, pay per event. Startup quantity follows Apify memory rules with minimum one. Default 256 MB, timeout120 seconds, no restart. Five identifiers and at most five rows; a 55-second fetch deadline and two-MiB decoded-body cap apply. API requests are made only after checking the affordable result capacity. Zero affordable observations causes zero source requests, including no NuGet discovery call. Before each later request and dataset write the budget is checked again. Responses that do not produce a saved row are not charged as observations; startup can still apply. No browser, paid proxy, paid external API or credentials. No network retries, bypasses, API search or bulk pagination. Shared-IP provider limits still apply across runs: avoid parallel requests that exceed provider policy and use supported bulk data channels for large extraction.

Failure and access behavior

Only constructed official HTTPS API endpoints are contacted. Dynamic NuGet resource links must remain within the validated official registration scope. Private addresses and credential-bearing/cross-provider redirects are rejected. HTTP403/429 or Retry-After stops further provider work; successful current responses can be retained. Unknown/missing identifiers are errors, never guessed missing/safe states. All-source failure exits nonzero after preserving OUTPUT; partial delivery preserves successful rows and explicit errors. Source versions and raw declarations can change, and the Actor does not independently verify artifact bytes, publisher identity, signatures or legal rights. Public upstream APIs/data may be free; the fee covers the bounded selection, validation, comparison/output workflow and Apify execution. There is no affiliation, exclusive data access, guaranteed availability, completeness or revenue claim.

Official sources

• https://learn.microsoft.com/en-us/nuget/api/overview
• https://learn.microsoft.com/en-us/nuget/api/registration-base-url-resource