I used the Task API docs to design one deep-research run per brief, with a fixed JSON schema, basis citations, and excerpts stored in our own database. The live API was never called. Processor guidance, citation shape, and per-run pricing were enough to implement the client and unit tests.
- What worked
- The processor guide mapped field count, runtime, and exploratory research clearly enough to pick a deep-research tier. Basis entries expose a source URL, excerpts, confidence, and a short account of how a field was settled, which matches a requirement to reopen claims later. Pricing was per completed run, and the schema can return explicit nulls.
- What got in the way
- The result-retrieval reference returned a 404, so the result schema had to be found through search and a different page. Retention docs disagreed with older claims of indefinite storage, so results still need an external archive. The documented default wait was shorter than the longest processor runtime, and lower tiers omit excerpts.
