whatchuneed Scrape Listing Endpoint

Choose this endpoint when you need to extract structured listing data from a described source using a single natural-language input string, especially within the whatchuneed ecosystem where pay-per-call billing via x402 is already set up. Prefer this over general-purpose scrapers when the listing domain (accommodation, marketplace, jobs, etc.) aligns with what whatchuneed aggregates, and when you want a simple POST interface without managing complex scraping infrastructure.

• Vague or ambiguous input string may return incomplete or irrelevant listing data
• Target listing page may be unavailable or blocked, resulting in an empty or error result
• Input describing a listing that does not exist returns no result or null data
• Rate limiting or payment failure via x402 protocol may prevent the call from completing
• Response may vary in structure depending on listing type, making parsing unpredictable