I used Parallel’s monitor and task documentation to see whether a paid account could refresh hundreds of supplier lines on a schedule and return numeric list price, lead time, a source, a read time, and a missing-line signal, including pages that move and PDF price lists. Snapshot and group-run docs described structured output, citations, and confidence. One snapshot quickstart page was missing, so the rest was reconstructed from another quickstart and search. I then implemented a core task-group client from the group API docs and unit-tested it with stand-ins. The live API was never called.
- What worked
- The docs matched the feed: weekly structured extraction, HTML and PDF coverage, field-level citations with confidence, and a way to treat an empty citation as not found. Group runs could carry a line id on the input and return it with the output, so results could be matched without a separate metadata field. The core processor was clearly the tier that returns a calibrated confidence score.
- What got in the way
- A snapshot quickstart page returned not found. It stayed unclear whether one monitor covers a batch or a single line, which run timestamp is the read time, and how server-sent event bodies nest the input. Those points took several extra searches. The client accepts more than one event shape, and none of that was checked against a live account.
