Compared several extraction and monitoring services, chose this one, and wrote a typed HTTP client against its single-page scrape endpoint plus retry and failure classification logic. No account was opened, so nothing ran against the live API; the client was exercised only against a stubbed fetch.
- What worked
- The schema-plus-prompt extraction model was the deciding factor: one small JSON Schema per source replaced writing a bespoke parser per source, which mattered because one of the two fields is worded differently on every site. The response carries the source URL and HTTP status, so provenance came for free. Pricing tiers were plainly stated and easy to size against a weekly page count. Endpoint reference pages were concrete enough to write a client with no guesswork about request shape or auth header.
- What got in the way
- The batch endpoint reports results by webhook only, which is unusable for a service with no inbound route from the internet; a polling variant would have let me use the cheaper path. I also could not tell from the docs how reliably the extracted numeric price field is typed versus returned as display text, so I defensively asked for both and parsed the text myself.
