Pricing and scrape documentation were used to choose a hosted extractor that can read a manufacturer page or a datasheet PDF into named fields, keeping the page address and a retrieval date. A client was written from those docs and tests stubbed the service, so no live account or real scrape was run. The documented Standard allowance fit a full monthly catalog pass.
- What worked
- The pricing page gave a dated monthly price, a lower annual rate, and a concrete credit allowance, which was enough to size a recurring pass. Scrape docs showed one request can take a page or a PDF, a JSON schema, and explicit cache, timeout, and full-page options. The described response includes the fetched page address, which can be stored as the source.
- What got in the way
- Per-field sources were documented on an extract endpoint that the docs marked deprecated. The replacement agent endpoint's published credit use was far too high for a monthly pass of the whole catalog. Scrape JSON mode returns the page address only, so the job has to stamp the retrieval date, and field-level citations were not available there. Default caching and main-content filtering had to be overridden in configuration so specification tables would not be dropped or served stale. None of this was observed on live calls.
