Acquisition And Routing
Indexer
Section titled “Indexer”An indexer entry is a configured provider instance that Scryer can test and reference. The settings page stores the connection fields, enablement, limits, and category/routing metadata the installed provider plugin requires.
For example, Settings > Indexers stores a provider type, display name, URL, credentials if required, and Scryer-specific enablement settings.
Download client
Section titled “Download client”A download client entry is a configured provider instance Scryer can coordinate with and later inspect for completed local items.
Download client settings store the fields the selected plugin requires, and the behavior is affected by routing, import paths, and library layout.
For example, Settings > Download Clients stores a configured client, then per-facet routing can decide when that client is eligible.
Delay profile
Section titled “Delay profile”A delay profile controls timing policy before Scryer acts on candidate metadata. It can apply by facet, tag, protocol preference, minimum age, and priority.
Don’t confuse delay profiles with quality profiles: delay profiles answer “when is this eligible”; quality profiles answer “does this satisfy the media policy.”
For example, a delay profile can make matching candidates wait before Scryer continues evaluation.
Quality profile
Section titled “Quality profile”A quality profile describes the allowed and preferred media characteristics for a title or facet. Scryer uses it to evaluate candidate metadata and upgrade state.
You select quality profiles in title add flows, media settings, and quality settings.
For example, a profile can allow selected quality tiers while rejecting candidates with disallowed attributes.
Rules are additional policy logic Scryer applies during evaluation. They can be global or facet-oriented depending on configuration.
Rules complement quality profiles and routing settings — use them for site-specific preferences that standard profile controls don’t cover.
For example, a custom rule can change a candidate score or block a candidate based on metadata Scryer exposes to the rule.
Routing
Section titled “Routing”Routing controls which configured provider instances are eligible for a facet or workflow. You configure it in per-facet settings and global provider settings.
Routing decides how Scryer references the provider instances you’ve already configured in Settings.
For example, anime routing can enable a configured provider instance for anime while leaving it disabled for movies.
Search now vs background acquisition
Section titled “Search now vs background acquisition”Search now is an evaluation you trigger explicitly for a title, episode, wanted item, or queue item. Background acquisition is Scryer’s scheduled or event-driven evaluation for monitored items.
Both paths use the same policy model. The difference is whether you asked Scryer to evaluate now or it evaluated as part of its background work.
You can press Search Now for a wanted item, for example, without changing the title’s long-term monitoring policy.