I read the official pages for search, scrape, JSON extraction, PDF parsing, browser actions, monitoring, proxies, billing, and terms, then wrote an HTTP client for the v2 search and scrape endpoints. Tests stub that client. No account was opened and the live API was never called. The request shape was clear enough to design listing discovery, numeric price and lead-time fields, and a retry when a saved link is dead. Putting that together took many separate pages.
- What worked
- Search plus scrape, a JSON schema for price and lead time, PDF parsing, and browser actions matched the job: find a moved listing, including a price-list PDF, then read structured fields. Pricing and terms pages made a paid hobby plan and responsibility for target-site rules explicit enough to flag before a full weekly run.
- What got in the way
- The live service was never called, so render quality, credit use, proxies, and block behavior were not observed. Monitoring, interact, JSON mode, proxies, and billing were split across pages and took repeated searches to connect. No SDK was installed. Account setup, an API key, and the paid plan were left unfinished.