Adult Data APIs and Porn Metadata Databases
An adult data API can mean several very different things. One service may return a platform's video catalog and embed URLs; another may supply scene, performer and studio metadata; another may tag videos you already own; and a self-hosted database may give you the infrastructure without any data at all. This guide separates those use cases instead of forcing them into one ranking.
The most important boundary is legal as well as technical: API access is not automatically a license to download, store or republish the underlying photos and videos. Metadata, thumbnails, embed URLs and media files can all have different usage rights. If you need licensed files rather than data about them, see our guide to licensed adult content providers.
We reviewed the current public documentation and terms on September 20, 2026. The main options covered here are Eporner API v2, AdultDataLink, AdultLM, ThePornDB, StashDB, FansDB, prdb, javinfo and Stash-box. Undocumented scrapers are intentionally not treated as equivalent to a supported data source.
Quick picks by use case
The public webmaster API supports search, per-video lookup and removed-video checks, and returns an embed URL alongside metadata and thumbnails. It is the clearest fit when your site publishes pages around Eporner-hosted videos rather than storing the video files itself.
AdultDataLink combines adult data, categories and filtering behind its own API and RapidAPI. A free account is available for testing, but its Copyright Policy says commercial use of datasets and APIs requires a written agreement, so a paid key should not be treated as a blanket republication license.
AdultLM is different from a third-party scene database. It analyzes a platform's own catalog and creates structured metadata, automatic tags, semantic search and content-safety signals. Access is positioned as a managed B2B engagement rather than a self-service public API plan.
Its API documentation exposes scenes, JAV, movies, performers, sites, tags, hashes, collections and bulk/change resources. It is useful for catalog normalization and media tooling, but public API access should not be read as a universal commercial right to mirror every field or image.
Both are useful when you already have media and need to identify or organize it. StashDB works closely with the Stash ecosystem and GraphQL; prdb offers REST/JSON access and phash/oshash lookup with low-cost paid plans.
Contents
Adult data APIs and metadata databases compared
| Option | Type | What it provides | Access / pricing | Main caveat |
|---|---|---|---|---|
| Eporner API v2 Details ↓ | Official platform API | Video search, metadata, thumbnails, embed URLs, removed IDs | Public GET endpoints; JSON/XML | Embed/API access does not imply a right to download and rehost the video file |
| AdultDataLink Details ↓ | Commercial multi-source data API | Adult-source data, categories, filtering, image/video references | Free account; current limited offer adds 1,000 extra requests/day; paid tiers and RapidAPI | Current Copyright Policy requires a written agreement for commercial use of datasets/APIs |
| AdultLM Details ↓ | Managed B2B catalog analysis | Automatic tagging, structured metadata, semantic search, content-safety analysis | Evaluation and contract; pricing depends on catalog scale | Analyzes your catalog rather than supplying a ready-made external scene database |
| ThePornDB Details ↓ | Metadata database + API | Scenes, performers, sites, tags, movies, JAV, hashes, collections, bulk/change resources | API docs; account/token for Stash-Box access | Commercial mirroring/republication rights should be confirmed separately |
| StashDB Details ↓ | Community metadata database | Scenes, performers, studios and fingerprints | Invite-code registration + API key; GraphQL | Primarily a Stash/cataloging ecosystem rather than a turnkey commercial feed |
| FansDB Details ↓ | Creator-platform metadata database | Performers, aliases, scenes and tags for approved creator platforms | Invite-only application; API key + GraphQL | Narrow creator focus; commercial republication rights are not implied by access |
| prdb Details ↓ | Adult media database | Scene/performer metadata, previews, spritesheets, phash/oshash lookup | Plus $12/year; Premium $20/year; Ultra $40/year; Bitcoin | Public plan language is aimed at personal collections and tool developers, not broad website republication |
| javinfo Details ↓ | JAV metadata aggregator | Codes, titles, cast, maker/label, series, dates and asset references from multiple sources | Trial; pay-as-you-go crypto billing; RapidAPI | Metadata and third-party asset references are not a media license |
| Stash-box Details ↓ | Self-hosted metadata server | GraphQL, performers, studios, scenes, tags and fingerprints | Open source, MIT; requires PostgreSQL | The database starts empty; you are responsible for data sources, rights and maintenance |
First decide what kind of adult API you actually need
"Adult API" is too broad to be a useful product category on its own. In practice, these tools fall into five different models.
1. An official platform API
The platform exposes its own catalog and usually a supported way to embed its media. Eporner is the clearest example in this guide. This model is useful when your site builds discovery, search or editorial pages around one source while the source keeps hosting the videos.
2. A third-party metadata database
ThePornDB, StashDB, FansDB and prdb help identify scenes, performers, studios, tags and other catalog entities. Fingerprints or hashes can also match a local file to a database record. This is a normalization layer, not a license to the underlying video.
3. A multi-source data aggregator
AdultDataLink and javinfo normalize information from multiple sources behind one interface. That can reduce engineering work, but it creates another due-diligence question: what rights does the aggregator actually grant for the returned data, images and external asset references?
4. Automated analysis of your own catalog
AdultLM starts with media you already control. Its value is automatic tagging, structured metadata, semantic retrieval and content-safety analysis rather than matching against a public scene database.
5. Your own metadata backend
Stash-box is infrastructure rather than a populated data source. It gives you the server, schema and GraphQL layer; you still have to supply lawful data, moderation and update processes.
Eporner API v2: official catalog and video embeds
Eporner publishes an "API for webmasters" whose documentation explicitly describes getting data and integrating Eporner videos into websites or applications.
The documented v2 methods cover:
- search — catalog search and pagination;
- id — data for a specific video and a way to verify that it is still available;
- removed — IDs for videos that have been removed.
Responses can include title, keywords, views, rating, duration, thumbnails, the public page URL and an embed URL, with JSON or XML output. The removed endpoint is particularly useful for automated catalogs because it gives you a supported signal for unpublishing pages whose source video has disappeared.
Rights boundary: the API documents Eporner-hosted integration and embeds. That should not be turned into a claim that you may download the source file, move it to your own CDN and republish it as your media. A self-hosted library needs separate rights.
This is most useful for adult video discovery sites, category pages and editorial/SEO pages where Eporner continues to host the media.
AdultDataLink: a commercial multi-source adult data API
AdultDataLink is the most conventionally commercial data provider in this comparison. Its Adult Content API advertises adult-source data, metadata, categories and filtering through both its own API and RapidAPI.
The current pricing page offers a Free account and advertises a limited offer of 1,000 extra requests per day for Free accounts, followed by Startup, Professional and Enterprise levels. It also lists API overage at $0.0003 per request. The site's current FAQ/homepage materials list cards, PayPal and cryptocurrencies among the available payment options.
The legal detail matters more than the price. AdultDataLink's current Copyright Policy says commercial use of AGIS datasets, APIs, codebases and analytics systems requires a written agreement. A technical API key or paid subscription therefore should not be treated as automatic permission to mirror every returned field, image or linked asset on a monetized website.
For a production project, define the intended use before integration: internal search, enrichment of your own records, a public catalog, image display, caching and long-term storage may require different answers.
This suits commercial teams that want one provider for multiple adult data sources and are prepared to document the permitted use case.
AdultLM: automatic tagging and semantic search for your catalog
AdultLM solves a different problem from the scene databases below. It analyzes media from your own catalog and generates structured adult-content metadata, including actions, participants, setting, mood, intensity and other semantic attributes.
For content platforms, the company also advertises automatic tagging, natural-language semantic search and content-safety checks during upload. Its public site says the same layer is already used across more than 75,000 videos in its search product.
This is a managed B2B model rather than a public self-service tariff. AdultLM offers content platforms a limited evaluation on sample videos or a search benchmark before a contracted engagement, with pricing tied to catalog scale.
This makes most sense for a platform with its own licensed video library that needs better metadata and search. If you need existing records about third-party scenes and performers, ThePornDB, StashDB or AdultDataLink are closer to that job.
ThePornDB: broad structured adult metadata
ThePornDB is useful when you need a normalized adult-media data model rather than the catalog of one video platform. Its current OpenAPI documentation exposes resources for scenes, JAV, movies, bulk operations, changes, directors, hashes, performers, performer sites, sites, tags, collections and more.
The database is also available through the Stash-Box workflow: create an account, generate an API token and configure the GraphQL endpoint in compatible tooling such as Stash.
The attraction is breadth and integration with hash-based workflows. The limitation is licensing clarity: the public pages we reviewed do not provide a broad enough grant to assume that any monetized site may mirror the full database and all associated imagery without further confirmation.
Use it for catalog enrichment, media management and entity matching when you can verify your intended public or commercial use separately.
StashDB and FansDB: community metadata through Stash-Box
StashDB — scenes, performers, studios and fingerprints
StashDB is a community database for professional digital adult-content metadata. It does not host the video files or point users to unofficial downloads; its value is identifying and organizing media you already have access to.
Registration currently requires an active invite code; after creating an account, you copy your API key and configure the GraphQL endpoint in Stash. Stash can then pull scene, performer and studio records and match local files by fingerprint/hash even when filenames are unreliable.
That makes StashDB useful for private media libraries, catalog normalization and internal tooling. It should not be presented as a turnkey commercial content feed unless the intended public use of the data has been cleared separately.
FansDB — metadata for independent creators and creator platforms
FansDB uses the same Stash-Box model but focuses on independent adult creators. Its database covers performers and aliases, scene titles and descriptions, release dates, participating performers and tags across approved creator platforms.
Access is invite-only: users apply, receive an invitation if approved, create an account and then obtain an API key and GraphQL endpoint.
FansDB is most useful for internal databases or tools where creator-platform metadata is specifically valuable. A public commercial catalog should still verify how much data and imagery it may republish.
prdb: fingerprint lookup for local adult media libraries
prdb is positioned around an adult media database for collectors and tool developers. Its API exposes scene and actor metadata, preview images, spritesheets and lookup by phash or oshash. That is useful when you already have a local file and need to identify the corresponding scene.
A free account provides the web interface without API access. The current Plus plan is $12 per year and is described for personal use and small collections; Premium is $20 per year with higher limits for power users and tool developers; Ultra is $40 per year and advertises five times the API rate limits of Premium for large libraries and heavier automation. Paid plans use Bitcoin through the site's BTCPay setup.
Because the published plan language is collection/tool oriented, prdb is easier to recommend for local workflows and specialized applications than as a mass commercial data backend. A broader public-site use case should be confirmed first.
javinfo: a specialized JAV metadata API
JAV here means Japanese Adult Video. javinfo accepts a DVD code or search query and returns normalized metadata regardless of which connected source produced the result. Its schema includes titles, cast, maker/label, series, release date, runtime and links to cover/gallery assets.
Direct access uses a REST API key, with RapidAPI available as another route. The provider's current homepage and FAQ now agree on paid usage pricing: $0.50 per 1,000 /movie results and $0.20 per 1,000 /query calls. The advertised free signup allowance is less consistent — the homepage says 100+ free lookups while the FAQ says 1,000+ — so verify the live allowance in the app. Direct top-ups are crypto-based.
The provider is explicit that it aggregates metadata and returns references to third-party assets rather than hosting a licensed video library. Keep the source/provenance information and do not treat a cover URL, stream manifest or other pointer as permission to create your own permanent copy.
It fits JAV catalogs, DVD-code lookup and internal enrichment workflows that need one normalized JSON interface instead of several custom scrapers.
Stash-box: run your own metadata server
Stash-box is an open-source video-indexing and metadata API server from the Stash project. The code is published under the MIT License, the backend uses GraphQL, and the schema covers performers, studios, tags, scenes, sites and fingerprint operations.
It is not a shortcut to somebody else's populated catalog. The README makes clear that a new installation starts with an empty database. You get the infrastructure and must decide where lawful data comes from, who moderates it and how it is updated.
A real deployment also needs PostgreSQL, image storage, API keys, backups and operational maintenance. Stash-box makes sense when metadata is part of your own product and control matters more than the convenience of a hosted service.
API access, metadata rights and media rights are separate
An adult API can technically return several layers of material with different legal implications:
- factual metadata — title, date, duration, IDs and studio names;
- editorial data — descriptions, curated tags, rankings or other fields created by somebody else;
- visual assets — thumbnails, covers and performer images;
- the media itself — photo and video files.
Permission to use one layer does not automatically cover the others. For a commercial project, verify at least whether data may be displayed publicly, cached long term, combined with images, stored after source deletion and used without or with attribution.
PornhwaDB is a useful exclusion example
PornhwaDB is technically a well-structured metadata API for adult manhwa, but its current Terms allow only non-commercial, personal and educational use and explicitly prohibit monetized apps, paid services and ad-supported platforms. That makes it a poor core recommendation for the commercial webmaster use case of this guide.
Why we do not treat scraping as equivalent to an API
A scraper may be technically convenient, but it does not create permission to use the extracted data. Page structure, anti-bot controls and source terms can also change independently of your code. For a production service, start with an official API, documented feed or explicitly permitted integration when one exists.
A practical integration pattern for WordPress or a custom stack
Most sites do not need an elaborate data platform just to consume one of these APIs. WordPress can call a service from a server-side scheduled task or plugin, store selected fields and update records on a schedule. If you are still choosing the site platform itself, compare our porn CMS and adult website scripts.
- Keep the source ID and source name. Do not store only a copied title; preserve a reliable link back to the source record.
- Call APIs server-side. API keys should not be exposed in public browser JavaScript.
- Cache only what the provider allows. Define retention separately for metadata, thumbnails and availability/status data.
- Handle removals. Use a removed/status endpoint when available; otherwise recheck records periodically.
- Separate embeds from self-hosting. An embed keeps the media with the platform; your own player/CDN requires the rights to store and serve the file.
- Preserve provenance. With aggregators, keep the underlying source and update timestamp when the API provides them.
If you host the video files yourself, the data layer is only one part of the architecture. Storage, transcoding, CDN and backups are separate concerns; see our guide to adult web hosting.
Pricing and commercial-use checks matter more than headline API access
The products in this guide use very different access models. Eporner's documented API is public; AdultDataLink has self-service tiers but separately requires written agreement for commercial use of its datasets/APIs; AdultLM is contract-led B2B; FansDB is invite-only; prdb has inexpensive paid API tiers; javinfo combines direct usage billing with RapidAPI; and Stash-box is open-source infrastructure.
Before building around any one provider, verify:
- whether your intended public or internal use is permitted;
- request quotas and overage behavior;
- storage and caching rules;
- rights to thumbnails, covers and performer images;
- attribution or source-link requirements;
- what happens to stored data when a source item is removed;
- whether the access model can support your expected catalog size and update frequency.
For commercial adult projects, a technically good API with unclear republication rights can be a worse dependency than a narrower service with a documented contract.
Which adult data API fits your project?
| Goal | Start with | Why |
|---|---|---|
| Publish pages around one adult video platform using embeds | Eporner API v2 | Official webmaster API with search, metadata and embed URLs |
| Pull normalized data from multiple adult sources | AdultDataLink | Commercial API, filters, pricing tiers and a B2B rights process |
| Automatically tag and search your own video catalog | AdultLM | Structured metadata, automatic tags and semantic search |
| Normalize scenes, performers, studios and tags | ThePornDB | Broad entity model plus Stash-Box compatibility |
| Identify local files by fingerprint/hash | StashDB or prdb | Both support hash/fingerprint-oriented matching workflows |
| Build tooling around independent creator-platform metadata | FansDB | Dedicated focus on independent creators |
| Look up JAV metadata by code or search | javinfo | Specialized multi-source API with a normalized schema |
| Own the metadata backend yourself | Stash-box | Open-source GraphQL server instead of a third-party hosted database |
FAQ
Can an adult API give me porn videos that I am allowed to republish?
Only when the source terms or a separate license grant that right. A video URL, thumbnail, stream or downloadable file is technical access, not proof of copyright permission. If your project needs locally hosted media, use a provider whose license explicitly covers that distribution model.
What is the simplest API for an adult video site?
If your model is external embeds, an official platform API such as Eporner is the simplest starting point in this set. If you host licensed files yourself, a metadata API becomes an enrichment layer rather than the source of the media rights.
Can I use ThePornDB or StashDB on a commercial website?
Technical access is available, but the public materials we reviewed do not provide a broad enough grant to assume unrestricted commercial mirroring of the database and associated imagery. Confirm the exact monetized/public republication use case before designing around it.
What should I use for JAV metadata?
javinfo is the most narrowly focused hosted option in this comparison, with normalized metadata from multiple sources. ThePornDB also exposes JAV resources as part of a broader adult metadata database.
Do I need a custom CMS to use these APIs?
No. WordPress or an existing adult CMS is enough for many projects if you add a small server-side integration layer. A custom backend becomes more useful when you have a very large catalog, complex entity relationships, your own search index or frequent updates.
How is an adult metadata API different from an NSFW AI API?
A metadata API describes, identifies or organizes existing content. An NSFW AI API generates new text, images, video or voice. They solve different product problems and should not be evaluated with the same criteria.
How we selected these APIs and databases
This review was checked on September 20, 2026. We looked for products that are currently accessible to developers and have public documentation or a clearly documented integration process.
- We checked: API documentation, data model, authentication, pricing/rate limits, integration model, data provenance and public usage restrictions.
- We did not treat as a benefit: the mere existence of a scraper, downloader or undocumented endpoint.
- We excluded from the core list: services with explicit commercial-use prohibitions for the target use case, unverified/closed products and tools without a distinct webmaster/developer job.
- We kept separate: data APIs, licensed media providers and generative NSFW AI APIs.
Provider terms can change faster than your architecture. Recheck terms, quotas, caching/storage rules and your permitted use case before launching a production integration.
Bottom line
For a supported video catalog with embeds, Eporner API v2 is the most straightforward starting point here. For normalized data across multiple adult sources, AdultDataLink is a more commercial B2B option, but its rights need to be documented explicitly. If the challenge is tagging and search across media you already control, AdultLM addresses a different but important part of the stack.
For catalog normalization and file identification, ThePornDB and StashDB are the broadest community/database-oriented options in this set; FansDB adds creator-platform specialization, prdb focuses on collection/tool workflows and fingerprints, and javinfo covers JAV metadata. Stash-box is the fallback when you want to own the metadata infrastructure instead of depending on a hosted database.
