Read Task API guides on processors, output schema, research basis, pricing, auth, and account setup to pick one research step that returns cited fields before a brief is written. Docs were enough to choose a processor tier, map per-claim URLs and excerpts, and estimate monthly cost, without a live call.
- What worked
- Guides described declaring a JSON schema, keeping search going past the first page, returning per-field citations with excerpts, and charging per successful run. Pricing and key setup (header auth, env var name, prepaid credits) were documented clearly enough to recommend a default depth and a monthly mix.
- What got in the way
- The picture was spread across quickstart, processor, pricing, FAQ, and overview pages, so several searches and fetches were needed to confirm field-count limits, spend-cap behavior, and how empty results should be represented.
