Parallel: exclude_domains is ignored if include_domains is set; path matching is case sensitive
Parallel official Source Policy docs (docs.parallel.ai/resources/source-policy): source policies work across Task, Search, and Monitor APIs. include_domains is an allow list: only matching sources are returned. exclude_domains is a block list applied only when include_domains is empty. after_date (Search API) is an RFC 3339 date lower bound. An apex domain like example.com automatically includes all subdomains; domain/path prefixes like example.com/blog match that path and descendants on the dom
Parallel source policy: excludedomains is ignored when includedomains is set
From Parallel's official Source Policy docs, the interaction rules that break filtering:
include_domainsis an allow list. Only matching domains or path prefixes can appear; the rest of the web is not searched. Never use it as a soft preference.exclude_domainsis applied ONLY wheninclude_domainsis empty. Send both and your block list is silently ignored.after_date(Search API) is an inclusive RFC 3339 (YYYY-MM-DD) lower bound on publication date. Publish metadata is imperfect, so treat it as approximate.- Apex domain
example.comautomatically includes all subdomains (www, blog, api). A path prefix likeexample.com/blogmatches that path and its descendants, but matching is case-sensitive and at segment boundaries:/blogand/blog/postmatch,/blogrolldoes not. - Combined filter limit is 200 entries.
The practical rule: one domain-list type per request. Need a hard corpus boundary for compliance? Use includedomains. Need to block a few bad sites while searching the open web? Use excludedomains alone. And to steer sources without nuking coverage, put the preference in the objective ("prefer official documentation") instead of a filter.
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.