Extract insurance quotes to structured JSON
Insurance quotes outline coverage offered, at what price, and under what terms. Formats vary by carrier, line of business, and distribution channel. Sensible turns quote documents into structured JSON for comparative rating, quote-to-bind workflows, and proposal management.
Why insurance quotes challenge extraction tools
No standard format exists. Quotes mix narrative text with coverage tables, requiring hybrid parsing.
Every carrier and broker formats quotes their own way: table-heavy system outputs, narrative proposals, or PDF exports from rating engines. LLM parsing handles the variation; SenseML rules guarantee your output schema stays consistent.
Commercial package quotes list coverages across multiple lines, each with sub-limits, SIRs, deductibles, and endorsements. The extraction config captures the full hierarchical structure with line-level premiums.
Broker proposals bury premium data in narrative paragraphs. Carrier system outputs present it in tables. Sensible processes both formats and normalizes them into the same JSON structure for downstream comparison.
Fields we extract
Default fields cover common quoting workflows. Adjust the schema to match your comparative rating system.
Named insured, effective/expiration dates, quoting carrier, producer, quote number, total premium, payment plan options
Coverage type, limit, deductible, premium, included endorsements, optional coverages, exclusions
Binding requirements, subjectivities, loss control recommendations, minimum premium, cancellation provisions, audit provisions
Workers compensation quote with class code pricing and experience mod factors.
E&O or professional liability quote with claims-made coverage terms.
Cyber liability quote with coverage for data breach, ransomware, and business interruption.
Multi-line commercial insurance quote combining property, liability, and auto coverage.
Supported quote types
Pre-built configurations cover common quote formats. New carrier or broker layouts map to your schema quickly. SenseML extraction logic is explicit and version-controlled.
Commercial package, general liability, workers compensation, commercial auto, cyber, professional liability, property, umbrella
Carrier system output, broker proposals, indication letters, binder quotes, renewal quotes



Common Questions
Answers about quote format support and comparative rating integration.
Sensible captures total premium, per-coverage premium, payment plans, installment amounts, taxes and fees, and any discounts or surcharges listed on the quote.
Yes. Sensible outputs quotes in a consistent JSON schema regardless of carrier. You can programmatically compare coverages, limits, deductibles, and premiums across multiple quotes.
Yes. Insurance quotes vary by carrier and line of business. Sensible extracts quote details regardless of format, including premium breakdowns, coverage terms, and conditions.
Yes. Sensible sends extraction results to your webhook endpoint when processing completes. You can also poll the API for status.
Yes. Sensible flags extractions with low confidence for human review. You can configure review thresholds and workflows.
Sensible is SOC 2 Type II certified and HIPAA compliant. Data is encrypted in transit and at rest.
Document data is stored indefinitely by default. Custom retention policies are available and can be configured for same-day deletion if needed.
Yes. Sensible offers a 14-day free trial on the Growth plan. No credit card required to start.
Sensible uses per-document pricing for predictable costs. No token-based billing or usage surprises. Volume discounts are available for higher throughput.
Sensible provides REST APIs and SDKs for Python and Node.js. Most integrations take a few hours. Webhooks, Zapier, and direct API calls are all supported.
Sensible processes PDFs (native or scanned), Microsoft Word (DOC, DOCX), spreadsheets (XLSX, XLS, CSV), single-page images (JPEG, PNG), multi-page images (TIFF), and email bodies with attachments.
Accuracy depends on document quality and configuration. Most production deployments achieve 95%+ accuracy with proper validation rules and confidence signals.
Processing speed depends on document size, page count, OCR requirements, and which extraction methods are used. Simple single-page documents process in seconds. Larger or more complex documents that use LLM-based extraction take longer.
