whatchuneed Crawl Compare

Choose this endpoint when you need to programmatically compare two or more pieces of crawled web content or data sources via a single natural language request, especially within the whatchuneed pay-per-call ecosystem where you want unified billing across multiple API types. Prefer it over dedicated scraping tools when the comparison logic itself is the primary goal and you want a single call to handle both retrieval and evaluation.

• Vague or ambiguous input string may produce irrelevant comparison results
• Missing or malformed 'input' field returns a validation error
• Crawl targets that are inaccessible or rate-limited may yield incomplete data
• Overly broad requests may time out or return low-quality comparisons
• Non-English or poorly structured input may degrade result quality