I used the Agentic Document Extraction guides and API reference to design a region-scoped HTTP client for urgent and background extraction of clinical referral PDFs. The material covered synchronous parse and extract, job polling, failed-page retries, bounding-box grounding, and hosted US and EU bases, plus in-region container deployment. I implemented that contract and checked it with stubbed unit tests, without calling the live service.
- What worked
- The reference pages named the fields needed for synchronous calls, job identifiers and polling, failed-page lists, page and bounding-box grounding, and a distinct EU base URL. That was enough to keep storage and the queue in place and to route ungrounded fields to review.
- What got in the way
- The behavior was spread across marketing guides and separate reference pages, so parse jobs, extract responses, grounding, and the EU host took many fetches to assemble. In-region deployment options and the two hosted regional bases had to be reconciled by hand. The OpenAPI schema was difficult to locate from the overview.