Providers, scrapers, and downloaders
Cove separates “bring in new media” from “identify existing media” and from “apply metadata to media you already have.” The canonical contracts are documented under metadata providers; this page helps you choose and introduce them safely.
The three main roles
Section titled “The three main roles”Downloaders
Section titled “Downloaders”Use a downloader for acquisition and intake from a supported source.
Use downloaders when you want Cove to:
- fetch new media directly
- match a source URL to a supported tool
- place new items into the library workflow without leaving the app
Scrapers
Section titled “Scrapers”Use a scraper to search for or extract metadata for an existing item when you want item-level review.
Use scrapers when you want to:
- check one item carefully before trusting a source broadly
- review suggested fields before applying them
- work source by source instead of running a big batch immediately
Metadata servers
Section titled “Metadata servers”Use a metadata server as a configured structured catalog after you trust its matches and want repeatable identification or enrichment.
Use metadata servers when you want to:
- identify many items at once
- enrich a larger portion of the library
- keep recurring provider workflows centralized in settings
A recommended workflow
Section titled “A recommended workflow”- Start with a scan or downloader intake.
- Test a scraper or metadata source on a small representative set.
- Review provenance and the quality of the result.
- Scale up only after the result looks trustworthy.
- Save the resulting cleanup or review workflows as filters or dynamic groups.
Provenance matters here
Section titled “Provenance matters here”Large libraries often combine manual edits, import data, scrapers, metadata servers, downloaders, and extensions. Review provenance so a successful-looking result does not hide an incorrect source or match.
Common metadata servers
Section titled “Common metadata servers”Cove works with metadata servers — community-run databases you point Cove at to identify and enrich your library. Add one under Settings → Data Sources & Data → Metadata Servers by pasting its endpoint and your API key, then use it from the Identify and Tagger options.
Metadata servers may use their own vocabulary. Several call a video record a scene; Cove matches and stores those records as videos. In the table below, “scene” describes the provider’s catalog rather than a separate Cove media type.
These are the metadata servers most people use:
| Server | Endpoint | What it covers |
|---|---|---|
| StashDB | https://stashdb.org/graphql | Community-driven database of digital scenes across all orientations. |
| ThePornDB | https://theporndb.net/graphql | Scenes and movies, powered by automated scrapers. |
| FansDB | https://fansdb.cc/graphql | Creator-platform content (OnlyFans, Fansly, ManyVids, and similar). |
| JAVStash | https://javstash.org/graphql | Japanese Adult Video, with original Japanese metadata. |
| PMV Stash | https://pmvstash.org/graphql | Remixed works such as Porn Music Videos. |
Each server needs a free account on that server and an API key, which you paste into Cove alongside the endpoint. Pick the servers that match your library — you can add more than one and Cove records which server each saved value came from.
Downloaders and the extension model
Section titled “Downloaders and the extension model”Downloaders participate in Cove’s extension model, so installation, discovery, and future expansion use the same package boundary as other add-ons.
If you are configuring the system, treat downloaders like installable capabilities. If you are building one, use the extension development guides for the implementation side.