parse-integration

# Parse: document data extraction Parse turns documents into structured JSON. You describe the fields you want, send a PDF, scan, or photo, and get those fields back with their values. It handles the layout variation that breaks template-based parsers: the same schema works across suppliers, form revisions, and scan quality. Two ways to use it, and this skill covers both. - **Run an extraction right now** with the `parse_*` MCP tools bundled in this plugin. - **Build an integration** in the user's own codebase against the HTTP API. ## The one rule that decides whether an integration works `POST /v1/extract` is **asynchronous by default**. It answers `202` with an extraction `id` and `status: "processing"` immediately, and the extracted data is not in that response. You then poll `GET /v1/extractions/{id}` until `status` is `completed` or `failed`. **Branch on `status`, never on timing.** Every response carries `status`, so one code path handles all of them. Integrations that assume "if the call took a while, the data must be in there" break the first time a document is slow or fast in the wrong direction, and they break silently. There are two shortcuts, and both still report `status`, so the same branch handles them: - `wait=N` holds the request open for up to N seconds (max 120) and returns the result inline if it finishes in time. It only applies when the document is uploaded in the same call. If the window expires you get the usual `202` and id, and you poll. - A ...