Extraction should be predictable
Insurance packets vary in size and complexity. A single upload might be a short COI or a long policy package. Customers need an estimate before work starts, especially when agents or batch jobs are involved.
PolDex uses credit estimates and explicit confirmation paths so spend is visible. The workflow is designed around predictability rather than surprise invoices.
Credits fit API usage
Seat pricing is awkward for infrastructure. The value is not how many people log in. The value is how many documents are processed and how reliable the output is.
Prepaid credits align the customer with the API. Developers can estimate, run, and export without negotiating a subscription before the first useful extraction.
Agents need confirmation
Agent environments require stronger spend controls. CLI extraction requires an explicit flag, and MCP extraction should require confirmation before paid work starts.
That guardrail is not friction. It is part of safe automation. Agents should be powerful, but they should not silently spend customer credits.