Collections are org-scoped saved source sets. Bundle the datasets, domains, and URLs you reach for repeatedly, then reference them by name with the collection:<name> prefix in included_sources. Create once, reuse across every search in your organization.
Collections vs presets: presets (academic, finance, …) are Valyu-curated and available to everyone. Collections are bundles you define and save for your org.
If a collection doesn’t exist or isn’t accessible, the API returns a warning and continues with any other valid sources:
{ "success": true, "warnings": ["Collection 'unknown-collection' not found"], "results": [...]}
If only an invalid collection was specified, you’ll get empty results with the warning.
Keep collections small and focused (medical-research, finance-sec-filings, tech-docs) rather than one catch-all, and use clear names so teammates know what each is for.