Insurance workflows are asynchronous
A real document workflow often involves uploads, batches, long files, callbacks, retries, and downstream systems. Synchronous request-response extraction is convenient for demos but brittle for production.
PolDex is designed around jobs. Developers can submit documents, receive status, handle webhooks, and download artifacts after processing completes.
Artifacts make output usable
JSON is the core contract, but teams often need CSV, XLSX, ZIP bundles, signed links, and manifests. Those artifacts help data move into spreadsheets, review queues, procurement systems, compliance products, and internal tools.
PolDex derives those outputs from the same FastScript truth source. The export is not a separate interpretation. It is a packaged form of the same schema-controlled result.
Webhooks need signatures
A webhook is only useful if the receiver can trust it. Signed delivery, retry behavior, idempotency, and clear job states reduce integration risk.
That operational layer is part of the product. Insurance extraction is not finished when the model reads the document. It is finished when reliable data reaches the system that needs it.