Search the live web or news index and return ranked URLs, titles, and snippets.

Prefer this before extraction when you do not already know the target URL. The response preserves engine_used and adapter_used so you can report where results came from; cached says whether Scrapyard reused a prior response. This tool does not extract page bodies.

Fetch one public URL and return clean readable markdown plus extraction provenance.

Use for a known article, documentation page, JavaScript-rendered page, or PDF. Check error before relying on content. Preserve and cite method, pipeline_steps, upstream_status, and final_url: they distinguish static parsing, browser rendering, PDF extraction, redirects, and truthful upstream failures. Private-network and unsafe URLs are intentionally rejected.

Discover a site's published URLs from robots.txt and sitemap XML without crawling pages.

Use this to inventory documentation, blog, or product URLs before selecting pages to extract. The response reports the discovery source, total count, filtered_count, and URL/lastmod entries. It intentionally does not follow ordinary page links or perform a full crawl.

Search and extract several domain-deduplicated sources in one bounded request.

Use when the task needs source text rather than only result snippets. The response keeps engine_used; each source keeps method, content_source, and extraction metadata so you can distinguish parsed content from snippet fallback and avoid overstating provenance. For exhaustive work, search first and extract selected URLs individually instead.

Return Scrapyard version, search-engine breaker state, adapter registry, and cache counters.

Use this when search/research fails, results unexpectedly come from a fallback adapter, or you need to verify which engines are configured and healthy. This is operational status, not a web search and not merely a liveness probe.