prdb.net: visual previews, a metadata API and NZB downloads through NZBporn
How prdb.net combines visual browsing with a metadata API, and where NZBporn fits when accessing matching Usenet releases.
A release list cannot answer every question about a collection. A filename can be technically correct yet reveal little about the catalogue entry it belongs to. prdb.net addresses that problem with a visual interface and structured metadata. For experienced Usenet users, the useful connection is between browsing, processing catalogue data through an API and accessing associated NZBs through NZBporn.
Disclosure: prdb.net and nzbporn.org sponsor nzb.is.
An interface built around visual recognition
According to the prdb.net feature overview, the video library can be filtered to entries with previews. Profiles, favourites and a wanted list support navigation. Image coverage varies; SFW mode blurs imagery.
That helps when recognition comes more easily than remembering a title. Identifying an entry visually makes spelling variations and release names less of an obstacle. A preview still needs to be treated as a reference: it cannot establish the quality of a particular file or the completeness of a Usenet post. Those decisions require information about the actual release.
Connecting the API to a local library
The prdb product page describes a JSON REST API with hash lookups, batch requests and change feeds. Web browsing is free; API access requires a paid plan.
The official SDKs support Python, TypeScript, Go and C#. Authentication uses X-Api-Key. That allows a clear division of responsibilities in a custom integration: the local tool manages files and presentation, while prdb supplies matching catalogue data.
The developer guide specifies supported fingerprints for identification; arbitrary checksums are not interchangeable with them. Lookups can return no match. An import pipeline should account for that: unknown files belong in a review queue instead of acquiring apparently complete metadata through a guessed assignment. Keeping identification separate from renaming also makes results easier to inspect.
NZBporn supplies the NZB downloads
The guide to the two services distinguishes their roles: prdb manages metadata, while NZBporn indexes Usenet and provides NZBs. The prdb API itself is therefore not an NZB download endpoint.
The current NZBporn product page describes preview galleries and Newznab access. Full access requires an active prdb plan with API access; NZBporn has no separate subscription.
An existing setup consequently needs to distinguish two interfaces: the metadata API supports cataloguing, while Newznab handles indexer access. A matching catalogue record does not guarantee a successful download. Availability on your provider and selection of the specific release remain separate parts of the workflow.
For the role of porndb.me alongside these services, see our article on the new PornDB version.
As of October 17, 2026. Based on the linked operator information and SDK documentation; no signed-in account testing.