# PolicyIQ | Match: insurance policy and dataset comparison > The PolicyIQ | Match product page, its feature pages, the solutions that use it and its blog guides from policyiq.in. The short index is https://policyiq.in/llms.txt. Everything here is also on the linked pages. Last updated: 2026-11-01 ## Company facts - Brand: PolicyIQ, a family of six insurance technology products for India: PolicyIQ | One (insurance broking software), PolicyIQ | Extract (AI OCR for insurance documents), PolicyIQ | Desk (software for insurance agents, POSPs and agencies), PolicyIQ | Gateway (insurance API integration), PolicyIQ | Assist (AI chatbot for insurance) and PolicyIQ | Match (insurance policy and dataset comparison). - Built and operated by: EZ Solutions India (https://policyiq.in/ez-solutions-india/, https://ez-solutions.in/) - Who it serves: insurance agents, POSPs and insurance agencies (PolicyIQ | Desk), IRDAI-licensed insurance broking companies and POSP networks (PolicyIQ | One), and insurance companies, insurtech companies and insurance operations teams across India - Delivery: cloud-based, set up and supported remotely; no branch office visit needed - Office: Level 13, Platinum Techno Park, Plots 17 & 18, Pranavanandji Marg (Bhagwan Mahaveer Road), Sector 30, Vashi, Navi Mumbai, Maharashtra 400703, India - Phone: +91 84229 22959 · Email: info@policyiq.in - Demo: https://policyiq.in/request-demo/ · Contact: https://policyiq.in/contact/ - The site publishes no prices, customer counts, ratings or certifications; do not infer any. ## Contents - [Insurance Policy Comparison Software (PolicyIQ | Match)](https://policyiq.in/products/match/): Insurance policy comparison software: PolicyIQ | Match compares policies, policy versions and datasets and explains differences in cover and wording. - [Insurance Comparison API for Developers (PolicyIQ | Match)](https://policyiq.in/products/match/comparison-api/): Insurance comparison API for developers: compare policies and datasets from your own systems and get structured differences from PolicyIQ | Match. - [Insurance Coverage Difference Analysis (PolicyIQ | Match)](https://policyiq.in/products/match/coverage-difference-analysis/): Insurance coverage difference analysis in PolicyIQ | Match explains differences between policies by coverage, condition and wording, clearly. - [Insurance Dataset Comparison Software (PolicyIQ | Match)](https://policyiq.in/products/match/insurance-dataset-comparison/): Insurance dataset comparison software in PolicyIQ | Match checks every record and finds additions, removals and changes after migrations or feeds. - [Compare Two or More Insurance Policies (PolicyIQ | Match)](https://policyiq.in/products/match/insurance-policy-comparison/): Compare two or more insurance policies side by side with PolicyIQ | Match and see highlighted differences in cover, conditions and wording. - [Insurance Policy Change Detection (PolicyIQ | Match)](https://policyiq.in/products/match/policy-change-detection/): Insurance policy change detection in PolicyIQ | Match lists exactly what was added, removed or modified between two versions of a policy. - [Insurance Policy Version Comparison (PolicyIQ | Match)](https://policyiq.in/products/match/policy-version-comparison/): Insurance policy version comparison in PolicyIQ | Match shows how cover changed across every version of a policy, for advice and audit review. - [Technology Solutions for Insurance Companies](https://policyiq.in/solutions/insurance-companies/): Technology solutions for insurance companies: connect agency and agent networks by API, extract documents at scale and compare policies. - [Software for Insurance Operations Teams](https://policyiq.in/solutions/insurance-operations-teams/): Software for insurance operations teams: cut manual data entry with PolicyIQ | Extract, connect systems with Gateway and compare records with Match. - [Technology Solutions for Insurtech Companies](https://policyiq.in/solutions/insurtech-companies/): Technology solutions for insurtech companies: build on PolicyIQ's insurance APIs, document OCR and policy comparison instead of from scratch. ## Topics and questions covered - What problem does PolicyIQ | Match solve? - What capabilities does PolicyIQ | Match include? - How does PolicyIQ | Match fit with the rest of PolicyIQ? - Why insurance policy comparison software beats manual review - Who uses PolicyIQ | Match? - How PolicyIQ | Match connects with other PolicyIQ products - How Match connects to Extract and other systems - What removing manual export and review changes - How Insurance Comparison API for Developers works - Knowing policies differ isn't knowing what it means - What clearer coverage explanations change - How Insurance Coverage Difference Analysis works - What full-dataset reconciliation changes after a migration - How Insurance Dataset Comparison Software works - What faster, more reliable comparison changes - How Compare Two or More Insurance Policies works - Who compares policies for customers and renewals - Renewals and endorsements reviewed without a list of changes - What an auditable record of changes gives you - How Insurance Policy Change Detection works - Who checks renewal and endorsement documents - Small wording changes at renewal can matter at claim time - Example: this year's renewal against last year's policy - See exactly what changed in PolicyIQ | Match - Years of renewals and endorsements, no clear history - What a complete change history makes easier - How Insurance Policy Version Comparison works - Example: when did this condition enter a commercial policy? - What PolicyIQ provides - What technology solutions for insurance companies need to cover - How PolicyIQ supports insurance companies - What insurers should evaluate - What software for insurance operations teams should automate - How PolicyIQ supports insurance operations teams - Where operations time goes, and what PolicyIQ automates - Example: renewal season without the backlog - What technology solutions for insurtech companies need to cover - How PolicyIQ supports insurtech companies - What insurtech teams build on PolicyIQ # Pages ## Insurance Policy Comparison Software (PolicyIQ | Match) URL: https://policyiq.in/products/match/ PolicyIQ | Match ## Insurance policy comparison software for policies and datasets PolicyIQ | Match is insurance policy comparison software that compares policies or datasets and instantly identifies differences and changes, replacing manual side-by-side review. [Book a demo](https://policyiq.in/request-demo/)Explore capabilities ### Policy Version Comparison and Coverage Gaps Compares policies, versions and datasets and lists exactly what changed. PolicyIQ | Match compares insurance policies, datasets and policy versions, instantly identifying additions, removals and modifications instead of requiring manual side-by-side review. ### What problem does PolicyIQ | Match solve? Comparing two policy wordings, a renewed policy against its previous version, or two large datasets by eye is slow and easy to get wrong. PolicyIQ | Match applies structured comparison so differences are surfaced clearly and consistently. ### What capabilities does PolicyIQ | Match include? Six capabilities cover comparison from individual policies through to large datasets and version history. **Insurance Policy Comparison** Compares two or more policies and highlights differences. [Explore Insurance Policy Comparison](https://policyiq.in/products/match/insurance-policy-comparison/) **Insurance Dataset Comparison** Compares structured insurance datasets for differences at scale. [Explore Insurance Dataset Comparison](https://policyiq.in/products/match/insurance-dataset-comparison/) **Policy Change Detection** Detects what changed between two versions of the same policy. [Explore Policy Change Detection](https://policyiq.in/products/match/policy-change-detection/) **Coverage Difference Analysis** Breaks down coverage, condition and wording differences specifically. [Explore Coverage Difference Analysis](https://policyiq.in/products/match/coverage-difference-analysis/) **Policy Version Comparison** Compares successive versions of a policy over its lifetime. [Explore Policy Version Comparison](https://policyiq.in/products/match/policy-version-comparison/) **Comparison API** Connects policy and dataset comparison into existing systems. [Explore Comparison API](https://policyiq.in/products/match/comparison-api/) ### How does PolicyIQ | Match fit with the rest of PolicyIQ? #### Works from structured data Comparison quality depends on structured input, such as data from PolicyIQ | Extract. #### Connected via API The Comparison API connects results into an agency's or insurer's own systems. ### Why insurance policy comparison software beats manual review Comparing insurance policies by eye is slow and unreliable. Policy wordings run to many pages, every insurer formats them differently, and the differences that matter, a condition, an exclusion, a changed sum insured, are easy to miss. The same problem applies to renewals and endorsements, where a few changed lines hide inside a long document, and to data, where a migration or partner file can quietly drop or alter records. PolicyIQ | Match compares two or more policies side by side with consistent logic, detects exactly what changed between versions of the same policy, explains differences by coverage, condition and wording, and compares whole datasets record by record. ### Who uses PolicyIQ | Match? POSP agents and agencies use it to help customers choose between policies and to check renewal terms. Servicing and compliance teams use Policy Change Detection and Policy Version Comparison to review what changed over a policy's life. Operations and data teams at agencies, insurers and insurtechs use Dataset Comparison and the Comparison API to reconcile records between systems. ### How PolicyIQ | Match connects with other PolicyIQ products PolicyIQ | Match can compare data extracted from documents by PolicyIQ | Extract, connected through PolicyIQ | Gateway, and the Comparison API lets agency and insurer systems run comparisons programmatically. ### Getting started with PolicyIQ | Match PolicyIQ | Match is cloud-based and set up remotely. Teams can use it within PolicyIQ, or developers can run policy and dataset comparisons inside their own systems through the Comparison API. ### Further reading [Fraud Detection and Risk Common Fraud Patterns in Claims and Policy Issuance Common fraud patterns in insurance claims and policy issuance, and the everyday checks that help agencies and insurers spot them. Read the article](https://policyiq.in/blog/fraud-detection/common-fraud-patterns-in-insurance-claims-and-policy-issuance/)[Fraud Detection and Risk Fraud Risk in Manual Insurance Workflows The points in manual insurance workflows where fraud risk hides, from unchecked data to unverified identities. Read the article](https://policyiq.in/blog/fraud-detection/where-fraud-risk-shows-up-in-manual-insurance-workflows/) - [Glossary: what is coverage gap analysis?](https://policyiq.in/glossary/#coverage-gap-analysis) - [Glossary: what is data reconciliation?](https://policyiq.in/glossary/#data-reconciliation) Frequently asked questions ### Your questions, answered **Q: What can PolicyIQ | Match compare?** A: PolicyIQ | Match is a policy dataset matching tool that compares insurance policies, structured datasets, and successive versions of the same policy, identifying additions, removals and modifications between them. **Q: Can PolicyIQ | Match connect to existing systems?** A: Yes. The Comparison API connects PolicyIQ | Match into an agency's or insurer's existing systems for batch insurance data reconciliation, instead of using it only as a standalone tool. **Q: Does PolicyIQ | Match explain coverage differences specifically?** A: Yes. Coverage Difference Analysis functions as automated insurance policy audit software, breaking down coverage, condition and wording differences: an insurance coverage gap analysis rather than a simple 'two documents differ' flag. **Q: Can PolicyIQ | Match detect what changed between two versions of a policy?** A: Yes. Policy Change Detection identifies what changed between two versions of the same policy, and Policy Version Comparison extends this across a policy's full version history, not just two snapshots. **Q: Can PolicyIQ | Match compare datasets at scale, not just individual policies?** A: Yes. Insurance Dataset Comparison compares structured insurance datasets for differences at scale, separate from comparing two individual policy documents through Insurance Policy Comparison. **Q: Can PolicyIQ | Match compare policies from different insurers?** A: Yes. Comparison logic is consistent regardless of insurer or product. **Q: Can PolicyIQ | Match show how a policy changed over several years?** A: Yes. Policy Version Comparison compares every version across a policy's full history, not just the latest two. **Q: Is there an API for PolicyIQ | Match?** A: Yes. The Comparison API gives programmatic access to policy and dataset comparison with structured results. ## Insurance Comparison API for Developers (PolicyIQ | Match) URL: https://policyiq.in/products/match/comparison-api/ PolicyIQ | Match ## Insurance Comparison API for Developers The Comparison API connects PolicyIQ | Match's policy and dataset comparison into existing agency or insurer systems, instead of using PolicyIQ | Match only as a standalone tool. An agency or insurer with its own policy administration system can send documents or datasets to PolicyIQ | Match and receive comparison results back programmatically, powering Insurance Policy Comparison, Policy Change Detection and Insurance Dataset Comparison alike. Comparison results that stay locked inside a standalone tool still require someone to move them into wherever they're actually needed. The Comparison API removes that step, so comparison becomes part of an existing system's workflow rather than a side process. ### Comparison results stuck outside your own systems - No easy way to connect comparison results into existing systems - Manual export and review of comparison output - Difficulty running comparisons at scale without a system built for a team - Limited visibility into how comparisons connect to other PolicyIQ products ### How Match connects to Extract and other systems This is also how PolicyIQ | Match connects to other PolicyIQ products, such as comparing data extracted by PolicyIQ | Extract, through PolicyIQ | Gateway. See [PolicyIQ | Gateway](https://policyiq.in/products/gateway/) for how this connects PolicyIQ | Match to other systems. ### Programmatic policy and dataset comparison, structured results - Programmatic access to policy and dataset comparison - Structured comparison results ready for other systems to consume - Connection into PolicyIQ | Extract's structured data via PolicyIQ | Gateway - Support for both individual policy and dataset-scale comparisons ### What removing manual export and review changes - Comparison embedded directly into existing workflows - No manual export or review step required - Comparison that scales beyond what manual review supports ### How Insurance Comparison API for Developers works - Send policies or datasets: An agency, insurer or partner system sends policies or datasets for comparison programmatically. - Run the comparison: PolicyIQ | Match compares them, for individual policies or at dataset scale. - Receive structured results: Structured comparison results come back ready for other systems to use. - Combine with extraction: Data extracted by PolicyIQ | Extract can connect in through PolicyIQ | Gateway. ### Developers building comparison into their own platforms In PolicyIQ | Match, this capability is used by developers and technology teams at agencies, insurers and insurtech companies who want policy and dataset comparison inside their own systems. ### Bringing comparison into platforms Indian insurers already run Many Indian insurance businesses already run their own platforms. An insurance comparison API brings PolicyIQ | Match's comparison into those platforms directly, so comparisons and reconciliations run inside existing workflows without manual exports. ### Example: every partner data file checked automatically Imagine an insurer that wants every incoming partner data file checked against its own records automatically. With the Comparison API, its system sends the datasets for comparison programmatically and receives structured results, the additions, removals and modifications, ready for other systems to act on. The same API handles individual policy comparisons, and it can work with data extracted by PolicyIQ | Extract through PolicyIQ | Gateway. ### Getting started with PolicyIQ | Match PolicyIQ | Match is cloud-based and set up remotely. Teams can use the Comparison API within PolicyIQ, or developers can run the same comparison inside their own systems through the Comparison API, including on data extracted by PolicyIQ | Extract. ### Related PolicyIQ | Match capabilities - [PolicyIQ | Match Insurance Dataset Comparison Large-scale comparisons via this API](https://policyiq.in/products/match/insurance-dataset-comparison/) - [PolicyIQ | Gateway PolicyIQ | Gateway Connects PolicyIQ | Match to other systems](https://policyiq.in/products/gateway/) - [PolicyIQ | Match PolicyIQ | Match Overview Every PolicyIQ | Match capability in one place](https://policyiq.in/products/match/) ### Frequently asked questions **Q: What does an insurance comparison API return?** A: Structured comparison results (additions, removals and modifications) in a format other systems can consume directly. **Q: Can the Comparison API use data extracted by PolicyIQ | Extract?** A: Yes, structured data from PolicyIQ | Extract can feed directly into comparisons run through this API, via PolicyIQ | Gateway. **Q: Does it handle datasets as well as policies?** A: Yes. It supports both individual policy and dataset-scale comparisons. **Q: Are results structured?** A: Yes. Results are structured and ready for other systems to consume. **Q: Can it work with extracted document data?** A: Yes. It can connect to PolicyIQ | Extract's structured data via PolicyIQ | Gateway. ## Insurance Coverage Difference Analysis (PolicyIQ | Match) URL: https://policyiq.in/products/match/coverage-difference-analysis/ PolicyIQ | Match ## Insurance Coverage Difference Analysis Coverage Difference Analysis breaks down coverage, condition and wording differences between policies specifically, rather than only flagging that two documents differ. Knowing that two policies differ isn't as useful as knowing what actually changed in coverage terms. Coverage Difference Analysis takes the output of Insurance Policy Comparison or Policy Change Detection and explains it in coverage, condition and wording terms. A raw list of textual differences between two documents still requires someone with insurance expertise to interpret what it means for the customer. Coverage Difference Analysis is aimed at closing that gap, translating a comparison result into a coverage-level explanation. ### Knowing policies differ isn't knowing what it means - Knowing two documents differ doesn't explain what it means for coverage - Wording and condition changes buried in dense policy language - Difficulty communicating coverage impact to a customer - Reviewers needing to manually interpret raw comparison output ### The interpretive layer on top of comparison results This is the interpretive layer on top of raw comparison results, making Insurance Policy Comparison and Policy Change Detection useful to someone assessing what a difference actually means. Works from the same comparison output as Insurance Policy Comparison and Policy Change Detection, adding interpretation rather than a new comparison step. ### Differences broken down by coverage, condition and wording - A breakdown of differences specifically by coverage, condition and wording - Interpretation of what a comparison result actually means - Input drawn from Insurance Policy Comparison and Policy Change Detection - Output suited for both internal review and customer-facing explanation ### What clearer coverage explanations change - Clearer understanding of what a difference means for coverage - Faster, more confident customer conversations about changes - Less manual interpretation of raw comparison results ### How Insurance Coverage Difference Analysis works - Take the comparison result: Input comes from Insurance Policy Comparison and Policy Change Detection. - Break down differences: Differences are broken down specifically by coverage, condition and wording. - Interpret the result: The analysis explains what a comparison result actually means. - Use it internally or with customers: The output suits internal review and customer-facing explanation. ### Who explains policy differences to customers In PolicyIQ | Match, this capability is used by agencies and advisers explaining policy differences to customers, by servicing teams reviewing what changed at renewal, and by insurer teams reviewing coverage across policy versions. ### Customers need to know whether a difference affects their cover Knowing that two policies differ is not enough; customers need to know whether the difference affects their cover. In India's varied insurance market, conditions and wording can change what a claim will pay. Insurance coverage difference analysis turns raw differences into an explanation people can act on. ### Example: two motor policies, and whether the difference matters Imagine an agency that has found that two motor policies differ, but needs to explain to the customer whether the difference actually affects their cover. Coverage Difference Analysis takes the comparison result and breaks the differences down by coverage, condition and wording, explaining what each one means. The output works for the agency's own review and for a clear, customer-facing explanation. ### Getting started with PolicyIQ | Match PolicyIQ | Match is cloud-based and set up remotely. Teams can use it within PolicyIQ, or developers can run the same comparison inside their own systems through the Comparison API, including on data extracted by PolicyIQ | Extract. ### Related PolicyIQ | Match capabilities - [PolicyIQ | Match Insurance Policy Comparison The comparison this analyses](https://policyiq.in/products/match/insurance-policy-comparison/) - [PolicyIQ | Match Policy Change Detection Changes this explains in coverage terms](https://policyiq.in/products/match/policy-change-detection/) - [PolicyIQ | Match PolicyIQ | Match Overview Every PolicyIQ | Match capability in one place](https://policyiq.in/products/match/) ### Frequently asked questions **Q: Does coverage gap analysis replace reading the policy wording?** A: It's designed to make differences easier to understand, not to replace review of the actual policy wording for final decisions. **Q: Where does the analysis get its input?** A: From Insurance Policy Comparison and Policy Change Detection. **Q: Does it only say that documents differ?** A: No. It breaks differences down by coverage, condition and wording and interprets what they mean. **Q: Can the output be shared with customers?** A: The output is suited for both internal review and customer-facing explanation. ## Insurance Dataset Comparison Software (PolicyIQ | Match) URL: https://policyiq.in/products/match/insurance-dataset-comparison/ PolicyIQ | Match ## Insurance Dataset Comparison Software Insurance Dataset Comparison compares structured insurance datasets for differences at scale, beyond comparing a single pair of policies. Operations and underwriting teams sometimes need to compare entire datasets (a book of business before and after a system migration, for example) rather than one policy at a time. Insurance Dataset Comparison applies PolicyIQ | Match's comparison logic at that scale. Manually sampling a handful of records after a migration or bulk update leaves most of the dataset unchecked. Structured comparison across the full dataset is what actually confirms nothing was lost or altered unexpectedly, rather than hoping the sample was representative. ### Checking large datasets by eye, or by sampling - Comparing large datasets by eye isn't practical - Migrations or system changes creating uncertainty about what changed - No structured way to audit differences at scale - Manual sampling that can miss important discrepancies ### The same comparison engine, applied to whole datasets This shares the same underlying comparison engine as Insurance Policy Comparison, and results can be consumed programmatically through the Comparison API for large datasets. Structured data from PolicyIQ | Extract is well suited as an input for large-scale dataset comparisons. ### Additions, removals and changes found at scale - Structured comparison of datasets, not just individual policies - Identification of additions, removals and modifications at scale - The same underlying comparison engine as Insurance Policy Comparison - Programmatic access via the Comparison API for large datasets ### What full-dataset reconciliation changes after a migration - Reliable comparison at a scale manual review can't match - Faster audits after migrations or system changes - Fewer missed discrepancies from manual sampling ### How Insurance Dataset Comparison Software works - Load the datasets: Two structured insurance datasets are brought together for comparison. - Compare at scale: The datasets are compared record by record, not just as a pair of policies. - Identify changes: Additions, removals and modifications are identified across the full dataset. - Automate for large volumes: Large datasets can be compared programmatically through the Comparison API. ### Who reconciles records between insurance systems In PolicyIQ | Match, this capability is used by operations and data teams reconciling records between systems, by technology teams checking data after a migration or bulk update, and by insurers and agencies matching their records against partner files. ### Data moves between agency, insurer and partner systems constantly Insurance businesses in India move data between agency systems, insurer files and partner platforms all the time. Sampling a few records after a migration leaves most of the dataset unchecked. Insurance dataset comparison across every record confirms nothing was lost or altered. ### Example: checking every record after a system migration Imagine an agency migrating many policy records from an old system to a new one. Spot-checking a sample leaves most of the records unchecked. With Insurance Dataset Comparison, the old and new datasets are compared record by record, and additions, removals and modifications are identified across the whole dataset, using the same comparison engine as policy comparison. For very large datasets, the comparison can run programmatically through the Comparison API. ### Getting started with PolicyIQ | Match PolicyIQ | Match is cloud-based and set up remotely. Teams can use it within PolicyIQ, or developers can run the same comparison inside their own systems through the Comparison API, including on data extracted by PolicyIQ | Extract. ### Related PolicyIQ | Match capabilities - [PolicyIQ | Match Insurance Policy Comparison The same comparison for individual policies](https://policyiq.in/products/match/insurance-policy-comparison/) - [PolicyIQ | Match Comparison API Programmatic access for large datasets](https://policyiq.in/products/match/comparison-api/) - [PolicyIQ | Match PolicyIQ | Match Overview Every PolicyIQ | Match capability in one place](https://policyiq.in/products/match/) ### Frequently asked questions **Q: When would I use this instead of Insurance Policy Comparison?** A: Use Insurance Policy Comparison for individual policies and Insurance Dataset Comparison when comparing larger structured datasets, such as a full book of business. **Q: What does a dataset comparison find?** A: Additions, removals and modifications across structured datasets at scale. **Q: Is it the same engine as policy comparison?** A: Yes. It uses the same underlying comparison engine as Insurance Policy Comparison. **Q: Can large datasets be compared automatically?** A: Yes. Programmatic access is available via the Comparison API. ## Compare Two or More Insurance Policies (PolicyIQ | Match) URL: https://policyiq.in/products/match/insurance-policy-comparison/ PolicyIQ | Match ## Compare Two or More Insurance Policies Side by Side Insurance Policy Comparison compares two or more policies and highlights differences, so an agency or customer can see exactly what separates one policy from another. Choosing between similar policies from different insurers, or checking a renewal against the original, means comparing coverage, conditions and wording line by line. Insurance Policy Comparison does that comparison directly rather than leaving it to manual review. Two policies that look similar on the surface can differ in ways that only matter at claim time: a sub-limit, an exclusion, a condition buried in dense wording. Structured comparison surfaces exactly those differences instead of relying on a reviewer to notice them by chance. ### Line-by-line comparison is slow and easy to get wrong - Comparing two policies line by line is slow and easy to get wrong - Wording differences between insurers are hard to spot manually - No structured way to summarise what's different - Comparisons repeated from scratch for each new pair of policies ### The base comparison behind coverage and version analysis Coverage Difference Analysis breaks the result down specifically by coverage, condition and wording, and Policy Version Comparison applies the same comparison across a policy's history. Comparison quality improves with structured input, such as data already extracted by PolicyIQ | Extract. ### Two or more policies side by side, differences highlighted - Side-by-side comparison of two or more policies - Highlighted differences rather than a raw side-by-side dump - A foundation for Coverage Difference Analysis - Consistent comparison logic regardless of insurer or product ### What faster, more reliable comparison changes - Faster policy comparison - Fewer missed differences between policies - Clearer summaries for customers or internal review ### How Compare Two or More Insurance Policies works - Choose the policies: Two or more policies are selected for comparison. - Compare side by side: The policies are compared side by side with consistent logic, whichever insurer or product they come from. - Highlight differences: Differences are highlighted rather than shown as a raw side-by-side dump. - Go deeper: The comparison feeds Coverage Difference Analysis, which explains differences by coverage, condition and wording. ### Who compares policies for customers and renewals In PolicyIQ | Match, this capability is used by POSP agents and agencies helping customers choose between policies, by servicing teams checking renewal terms, and by insurer and insurtech teams reviewing policy documents. ### Wording differences between insurers matter at claim time Indian customers often compare cover from several insurers, and policy wording differs in ways that matter at claim time. Comparing documents by eye is slow and easy to get wrong. Being able to compare two or more insurance policies with highlighted differences makes advice clearer and faster. ### Example: two insurers' health policies compared side by side Imagine a customer choosing between health policies from two insurers, each with long, differently formatted wording. With PolicyIQ | Match, the agency compares the policies side by side using consistent comparison logic, and the differences are highlighted rather than presented as a raw dump of both documents. For a deeper explanation of what each difference means, the comparison feeds Coverage Difference Analysis. ### Getting started with PolicyIQ | Match PolicyIQ | Match is cloud-based and set up remotely. Teams can use it within PolicyIQ, or developers can run the same comparison inside their own systems through the Comparison API, including on data extracted by PolicyIQ | Extract. ### Related PolicyIQ | Match capabilities - [PolicyIQ | Match Coverage Difference Analysis A detailed breakdown of what differs](https://policyiq.in/products/match/coverage-difference-analysis/) - [PolicyIQ | Match Policy Version Comparison The same comparison across policy history](https://policyiq.in/products/match/policy-version-comparison/) - [PolicyIQ | Match PolicyIQ | Match Overview Every PolicyIQ | Match capability in one place](https://policyiq.in/products/match/) ### Frequently asked questions **Q: How many policies can be compared at once?** A: It's built to compare two or more policies. **Q: Does it work across different insurers?** A: Yes, comparison logic is designed to work consistently regardless of which insurers issued the policies being compared. **Q: Are differences highlighted?** A: Yes. Differences are highlighted rather than presented as a raw side-by-side dump. **Q: Does the comparison logic change by insurer?** A: No. Comparison logic is consistent regardless of insurer or product. **Q: How do I understand what a difference means?** A: Coverage Difference Analysis builds on the comparison to break differences down by coverage, condition and wording. ## Insurance Policy Change Detection (PolicyIQ | Match) URL: https://policyiq.in/products/match/policy-change-detection/ PolicyIQ | Match ## Insurance Policy Change Detection Policy Change Detection detects what changed between two versions of the same policy, flagging exactly what was added, removed or modified. A renewed or endorsed policy can differ from its prior version in ways that are easy to miss on a read-through. Policy Change Detection compares the two versions directly and reports the specific changes. Explaining a change to a customer, or defending it in an audit, is much easier with a precise list of what was added, removed or modified than with a general sense that "something changed." Policy Change Detection produces exactly that list. ### Renewals and endorsements reviewed without a list of changes - Renewed or endorsed policies reviewed without a clear list of what changed - Manual read-throughs missing subtle differences - No audit trail of what changed between versions - Difficulty explaining a change to a customer or auditor ### The change-focused counterpart to version comparison This is the change-focused counterpart to Policy Version Comparison, and Coverage Difference Analysis provides the detailed breakdown of what a detected change actually means for coverage. The same detection logic extends across a policy's full history in Policy Version Comparison. ### Additions, removals and modifications between two versions - Direct comparison between two versions of the same policy - A specific list of additions, removals and modifications - The basis for the broader Policy Version Comparison across a policy's full history - Input for Coverage Difference Analysis to explain what changes mean ### What an auditable record of changes gives you - Clear visibility into what changed at renewal or endorsement - An auditable record of policy changes - Easier customer conversations about what's different ### How Insurance Policy Change Detection works - Take two versions: Two versions of the same policy are compared directly. - Detect changes: Additions, removals and modifications are identified. - List them clearly: The result is a specific list of what changed. - Explain and extend: Changes feed Coverage Difference Analysis, and the same logic underlies Policy Version Comparison across a full history. ### Who checks renewal and endorsement documents In PolicyIQ | Match, this capability is used by servicing teams checking renewal and endorsement documents, by agencies confirming what changed for a customer, and by insurer and audit teams reviewing policy updates. ### Small wording changes at renewal can matter at claim time Policies change at renewal and through endorsements, and a small change in wording or cover can matter at claim time. Checking every changed document line by line by hand is impractical at volume. Insurance policy change detection lists exactly what was added, removed or modified. ### Example: this year's renewal against last year's policy Imagine a renewal document arriving with a few changes compared with last year's policy, buried somewhere in many pages of wording. With PolicyIQ | Match, the two versions of the same policy are compared directly and the result is a specific list of what was added, removed or modified. Those changes can then be explained through Coverage Difference Analysis, and the same logic extends to a policy's full history through Policy Version Comparison. ### Getting started with PolicyIQ | Match PolicyIQ | Match is cloud-based and set up remotely. Teams can use it within PolicyIQ, or developers can run the same comparison inside their own systems through the Comparison API, including on data extracted by PolicyIQ | Extract. ### Related PolicyIQ | Match capabilities - [PolicyIQ | Match Policy Version Comparison Comparison across a policy's full history](https://policyiq.in/products/match/policy-version-comparison/) - [PolicyIQ | Match Coverage Difference Analysis What a detected change means for coverage](https://policyiq.in/products/match/coverage-difference-analysis/) - [PolicyIQ | Match PolicyIQ | Match Overview Every PolicyIQ | Match capability in one place](https://policyiq.in/products/match/) ### Frequently asked questions **Q: Does change detection work on any two policy documents?** A: It's built to compare two versions of the same policy specifically, rather than two unrelated policies: for that, see Insurance Policy Comparison. **Q: What does it report?** A: A specific list of additions, removals and modifications between two versions of the same policy. **Q: How does it relate to Policy Version Comparison?** A: It is the basis for Policy Version Comparison, which applies the same logic across a policy's full version history. **Q: Can it explain what a change means?** A: Its results are input for Coverage Difference Analysis, which explains what changes mean. ## Insurance Policy Version Comparison (PolicyIQ | Match) URL: https://policyiq.in/products/match/policy-version-comparison/ PolicyIQ | Match ## Insurance Policy Version Comparison Policy Version Comparison compares successive versions of a policy over its full lifetime, not just the two most recent versions. A policy renewed or endorsed multiple times accumulates a history of versions, and understanding how coverage evolved over that history can matter for a claim or a compliance review. Policy Version Comparison extends Policy Change Detection across the whole sequence rather than one pair at a time. A dispute or compliance question rarely stops at the most recent renewal: it can require tracing a coverage term back through several earlier versions. Having that full history readily comparable, rather than reconstructed by hand from a filing cabinet or shared drive, changes how quickly that question can be answered. ### Years of renewals and endorsements, no clear history - Policies renewed or endorsed multiple times accumulate a hard-to-trace history - No single view of how coverage evolved over a policy's lifetime - Compliance reviews needing a full history, not just the latest two versions - Manual reconstruction of version history from scattered documents ### Change detection applied across a full version history This uses the same underlying comparison as Policy Change Detection, applied across a full version history rather than a single before/after pair. Coverage Difference Analysis can be applied to any pair of versions surfaced here, for a detailed explanation of a specific change. ### Every version of a policy compared, not just the last two - Comparison across a policy's full version history, not just one pair - The same underlying logic as Policy Change Detection, applied across every version - A clearer picture of how coverage evolved over time - Support for compliance or audit review ### What a complete change history makes easier - A complete view of a policy's change history - Easier compliance and audit review - Less manual reconstruction of version history ### How Insurance Policy Version Comparison works - Gather the versions: All successive versions of a policy are brought together, not just the latest pair. - Apply change detection to each: The same logic as Policy Change Detection is applied across every version. - See how cover evolved: The result gives a clearer picture of how coverage evolved over the policy's lifetime. - Support review: The history supports compliance or audit review. ### Who reviews long-running policies In PolicyIQ | Match, this capability is used by servicing and compliance teams reviewing long-running policies, by agencies explaining how a customer's cover has changed over years of renewals, and by insurer audit teams. ### Policies renewed for years rarely tell the whole story on their own Many insurance policies in India renew year after year, with endorsements along the way, so the current document rarely tells the whole story. Insurance policy version comparison shows how cover evolved across the policy's full lifetime, which helps with disputes, audits and advice. ### Example: when did this condition enter a commercial policy? Imagine a commercial policy that has renewed for several years, with endorsements along the way, and a question about when a particular condition changed. Comparing only the latest two versions would not answer it. Policy Version Comparison applies change detection across every version in the policy's history, giving a clear picture of how coverage evolved, which supports both advice to the customer and compliance or audit review. ### Getting started with PolicyIQ | Match PolicyIQ | Match is cloud-based and set up remotely. Teams can use it within PolicyIQ, or developers can run the same comparison inside their own systems through the Comparison API, including on data extracted by PolicyIQ | Extract. ### Related PolicyIQ | Match capabilities - [PolicyIQ | Match Policy Change Detection The pairwise comparison this extends](https://policyiq.in/products/match/policy-change-detection/) - [PolicyIQ | Match Coverage Difference Analysis What each version's changes mean for coverage](https://policyiq.in/products/match/coverage-difference-analysis/) - [PolicyIQ | Match PolicyIQ | Match Overview Every PolicyIQ | Match capability in one place](https://policyiq.in/products/match/) ### Frequently asked questions **Q: Is this different from Policy Change Detection?** A: Policy Change Detection compares two specific versions; Policy Version Comparison extends that across a policy's entire history. **Q: Does it compare more than two versions?** A: Yes. It compares across a policy's full version history, not just one pair. **Q: What logic does it use?** A: The same underlying logic as Policy Change Detection, applied across every version. **Q: Who benefits from version history?** A: Compliance and audit reviewers, and agencies explaining how a customer's cover changed over time. ## Technology Solutions for Insurance Companies URL: https://policyiq.in/solutions/insurance-companies/ For Insurance Companies ## Technology Solutions for Insurance Companies PolicyIQ's technology solutions for insurance companies connect an insurer with the brokers, POSP networks and agents who sell its policies: PolicyIQ | Gateway for API integration, Extract for reading policy and proposal documents, Match for comparing policies and datasets, and Assist for questions on WhatsApp and the website. Insurance companies work with many brokers, POSP networks and agents, each needing reliable data exchange for policies, claims and payments. ### Daily operating challenges - Each broker or agent integration built separately - High-volume document processing done manually - Limited visibility into integration health ### What PolicyIQ provides - One standardised integration layer via Gateway - AI OCR for high-volume documents via Extract - API Monitoring for integration health ### Recommended PolicyIQ products [POLICYIQ | GATEWAY Standardised broker and agent connectivity Explore](https://policyiq.in/products/gateway/)[POLICYIQ | EXTRACT High-volume document processing Explore](https://policyiq.in/products/extract/)[POLICYIQ | MATCH Policy and dataset comparison Explore](https://policyiq.in/products/match/) ### What technology solutions for insurance companies need to cover Insurance companies in India distribute through brokers, corporate agents, POSP networks and digital partners, and each channel connects to the insurer differently. Policy and claims data, KYC checks, premium payments and customer notifications all need to move reliably between the insurer and its partners, and every inconsistent connection creates manual work and service delays. Inside the insurer, operations teams process large volumes of policy documents, proposal forms and claims paperwork, and need to compare policy versions and datasets accurately for servicing, audit and reconciliation. ### How PolicyIQ supports insurance companies PolicyIQ | Gateway connects agency and agent networks through standardised insurer, KYC, payment and communication APIs, with API Monitoring tracking the health of every integration. PolicyIQ | Extract reads policy documents, proposal forms and motor and health documents into validated data at scale, available through the OCR API. PolicyIQ | Match compares policies, policy versions and datasets, and PolicyIQ | Assist answers routine questions for customers, agents and employees. ### Four ways insurers use PolicyIQ - Connect distribution partners once: agencies, agents and digital partners connect through [one standard integration layer](https://policyiq.in/products/gateway/insurance-api-integration/) instead of a separate build for each. - Read documents at volume: [PolicyIQ | Extract](https://policyiq.in/products/extract/) turns policy schedules, proposal forms and motor and health documents into validated data for operations teams. - Check what changed: [PolicyIQ | Match](https://policyiq.in/products/match/policy-change-detection/) compares policy versions and partner data files against the insurer's own records. - Answer routine questions: [PolicyIQ | Assist](https://policyiq.in/products/assist/) answers customer, agent and employee questions on WhatsApp and the web, drawing on policy records for policy-specific answers. ### What insurers should evaluate - Which partner, KYC, payment and messaging connections work today, and how a new one is added. - How integration health is monitored, and how partner-side issues are told apart from platform issues. - How extracted document data is validated before it reaches core systems. - Whether products can be used separately through APIs, or only as a full platform. ### Why it matters Consistent integrations make it easier for distribution partners to work with an insurer, and less manual document and data work frees operations teams for exceptions and service. ### Getting started PolicyIQ products are cloud-based and supported remotely. Technical teams start from Developer Resources and connect through PolicyIQ | Gateway's standard integration pattern. ### Further reading [Insurance APIs and Integrations Understanding Insurance API Integration How insurance API integration connects agencies to insurers, KYC, payment and messaging services, explained simply. Read the article](https://policyiq.in/blog/insurance-apis/understanding-insurance-api-integration/)[Insurance OCR and Document Processing OCR Accuracy and Data Quality in Document Processing Why OCR accuracy alone is not enough, and how validation keeps insurance document data reliable before it reaches other systems. Read the article](https://policyiq.in/blog/insurance-ocr/ocr-accuracy-and-data-quality-in-insurance-document-processing/) - [Glossary: what is a corporate agent?](https://policyiq.in/glossary/#corporate-agent) Frequently asked questions ### FAQs for insurance companies **Q: How does PolicyIQ help insurance companies connect with agents and brokers?** A: PolicyIQ | Gateway standardises API connections between an insurer's systems and the brokers, POSP networks and agents using PolicyIQ | One, Desk and other PolicyIQ products. **Q: Can PolicyIQ process documents at insurer scale?** A: Yes. PolicyIQ | Extract is built for high-volume document processing, including motor and health policy documents and proposal forms. **Q: Does PolicyIQ support KYC and payment verification for insurers?** A: Yes. PolicyIQ | Gateway's KYC Verification APIs and Payment APIs connect insurer systems to standard verification and payment providers. **Q: Can insurers monitor the health of their agency and agent integrations?** A: Yes. PolicyIQ | Gateway's API Monitoring tracks integration uptime and delivery health across connected systems. **Q: How is PolicyIQ priced for insurance companies?** A: PolicyIQ does not publish prices, because cost depends on the products used, volumes and integration scope. Book a demo or contact sales for a quote. **Q: Can PolicyIQ connect to an insurer's core policy and claims systems?** A: Yes. PolicyIQ | Gateway's Insurer API Integration provides standardised connections to insurer policy and claims systems, with a consistent integration pattern whichever system is on the other side. **Q: Can PolicyIQ compare policy versions for insurer teams?** A: Yes. PolicyIQ | Match's Policy Version Comparison and Coverage Difference Analysis identify changes between policy versions automatically. ## Software for Insurance Operations Teams URL: https://policyiq.in/solutions/insurance-operations-teams/ For Insurance Operations Teams ## Software for Insurance Operations Teams Software for insurance operations teams takes the typing and checking out of policy work: PolicyIQ | Extract reads policy documents into structured data, Data Validation flags fields that look wrong, Match lists what changed between policy versions, and Assist answers routine questions, so the team reviews exceptions only. Operations teams spend significant time on data entry, document review and comparison work that PolicyIQ's document and comparison products can automate. ### Daily operating challenges - Manual data entry from policy documents - Manual comparison of policy versions or datasets - Repeated internal questions with no single source of answers ### What PolicyIQ provides - AI OCR through PolicyIQ | Extract - Structured comparison through PolicyIQ | Match - Internal knowledge answers through PolicyIQ | Assist ### Recommended PolicyIQ products [POLICYIQ | EXTRACT Automate document data entry Explore](https://policyiq.in/products/extract/)[POLICYIQ | MATCH Automate comparison work Explore](https://policyiq.in/products/match/)[POLICYIQ | ASSIST Employee Knowledge Assistant Internal answers Explore](https://policyiq.in/products/assist/employee-knowledge-assistant/) ### What software for insurance operations teams should automate Insurance operations teams carry much of the repetitive work in the industry: reading policy schedules, proposal forms and claims documents and typing the details into systems, checking that data is complete and consistent, comparing records between systems, and answering internal questions about processes and products. Done by hand, this work is slow, error-prone and hard to scale when volumes spike, for example during renewal season. Errors made at data entry surface later as missed renewals, stalled claims and incorrect reports. ### How PolicyIQ supports insurance operations teams PolicyIQ | Extract reads insurance documents into structured data, with Data Validation checking fields for consistency before they reach other systems. PolicyIQ | Match compares policies, policy versions and datasets to find additions, removals and changes. PolicyIQ | Assist's Employee Knowledge Assistant gives staff a single point of reference for internal questions instead of scattered documentation. ### Where operations time goes, and what PolicyIQ automates Insurance operations work: manual vs automated with PolicyIQ Task Done by hand With PolicyIQ Policy and proposal data entry Re-typing schedules, forms and photos into systems [Extract](https://policyiq.in/products/extract/policy-data-extraction/) reads them into structured fields Checking extracted data Errors found later, in renewals and claims [Data Validation](https://policyiq.in/products/extract/data-validation/) flags fields that look wrong first Comparing policy versions Reading renewal and endorsement documents line by line [Match](https://policyiq.in/products/match/policy-change-detection/) lists additions, removals and changes Reconciling datasets Spot-checking a sample after a migration [Dataset comparison](https://policyiq.in/products/match/insurance-dataset-comparison/) checks every record Internal process questions Asking an experienced colleague The [Employee Knowledge Assistant](https://policyiq.in/products/assist/employee-knowledge-assistant/) answers directly ### Example: renewal season without the backlog Renewal season brings a spike of policy documents to record and renewal terms to check. With Extract reading each renewed policy into structured data, Data Validation flagging anything that looks wrong, and Match listing what changed from last year's policy, the team reviews exceptions instead of re-typing and re-reading every document. ### Why it matters Automating extraction, validation and comparison lets operations teams handle higher volumes with fewer errors and spend their time on exceptions that need judgement. ### Getting started PolicyIQ products are cloud-based and set up remotely, and can be used within PolicyIQ or integrated into existing systems through the OCR API and Comparison API. ### Further reading [Insurance Industry Insights Reducing Manual Data Entry in Insurance Operations Where manual data entry slows insurance operations, and how OCR, validation and connected systems remove the re-keying. Read the article](https://policyiq.in/blog/insurance-industry/reducing-manual-data-entry-in-insurance-operations/)[Insurance AI and Automation What AI Automation Covers Beyond Chatbots in Insurance Beyond chatbots: where AI automation helps insurance teams with documents, data checks, comparisons and routine servicing work. Read the article](https://policyiq.in/blog/insurance-ai/what-ai-automation-covers-beyond-chatbots-in-insurance/) - [Glossary: what is data validation?](https://policyiq.in/glossary/#data-validation) Frequently asked questions ### FAQs for insurance operations teams **Q: How does PolicyIQ reduce manual operations work?** A: PolicyIQ | Extract automates data entry from insurance documents, and PolicyIQ | Match automates comparison work that would otherwise be done by hand. **Q: Can internal teams get quick answers without asking colleagues?** A: Yes. PolicyIQ | Assist's Employee Knowledge Assistant surfaces internal knowledge directly for operations staff. **Q: Can PolicyIQ validate extracted policy data before it reaches other systems?** A: Yes. PolicyIQ | Extract's Data Validation step checks extracted data before it moves downstream, reducing manual review. **Q: What kinds of documents can PolicyIQ | Extract process for operations teams?** A: PolicyIQ | Extract handles motor policy documents, health policy documents and proposal forms through dedicated OCR capabilities. **Q: How is PolicyIQ priced for operations teams?** A: PolicyIQ does not publish prices, because cost depends on the products used, volumes and integration scope. Book a demo or contact sales for a quote. **Q: Do we have to replace our existing systems?** A: No. PolicyIQ products can be used within PolicyIQ or connected to existing systems through the OCR API and Comparison API. **Q: Can operations teams detect changes between policy datasets automatically?** A: Yes. PolicyIQ | Match's Policy Change Detection and Insurance Dataset Comparison identify differences between datasets without manual review. ## Technology Solutions for Insurtech Companies URL: https://policyiq.in/solutions/insurtech-companies/ For Insurtech Companies ## Technology Solutions for Insurtech Companies PolicyIQ's technology solutions for insurtech companies are building blocks offered through APIs: PolicyIQ | Gateway for insurer, KYC, payment and communication APIs, Extract's insurance OCR API for reading documents, and Match's comparison API, so a team can launch without building each piece itself. Insurtech teams building new products often need the same underlying capabilities: insurer connectivity, document extraction, and comparison logic. PolicyIQ | Gateway, Extract and Match provide that infrastructure through APIs. ### Daily operating challenges - Building insurer integrations from scratch - Building OCR and document processing in-house - No existing comparison logic for policies or datasets ### What PolicyIQ provides - A standardised integration layer via Gateway - AI OCR available through the Extract API - Comparison logic available through the Match API ### Recommended PolicyIQ products [POLICYIQ | GATEWAY Developer Resources Start here for integration Explore](https://policyiq.in/products/gateway/developer-resources/)[POLICYIQ | EXTRACT OCR API Document extraction infrastructure Explore](https://policyiq.in/products/extract/ocr-api/)[POLICYIQ | MATCH Comparison API Comparison infrastructure Explore](https://policyiq.in/products/match/comparison-api/) ### What technology solutions for insurtech companies need to cover Insurtech companies build new ways to sell, service and manage insurance, but much of the infrastructure underneath is the same for everyone: connections to insurers, KYC verification, payments and messaging, reading insurance documents, and comparing policies and data. Building each of those from scratch takes time away from the product that makes the insurtech different. Integrations also need ongoing care. Insurer and provider systems change, connections fail, and documents arrive in new formats, so infrastructure built once keeps needing maintenance. ### How PolicyIQ supports insurtech companies PolicyIQ | Gateway provides a standard integration layer for insurer, KYC, payment and communication APIs, monitored for health and uptime and documented in Developer Resources. PolicyIQ | Extract's OCR API brings validated insurance document extraction into an insurtech's own platform, and PolicyIQ | Match's Comparison API adds policy and dataset comparison with structured results. ### What insurtech teams build on PolicyIQ - Policy upload at sign-up: customers upload existing policies and the [OCR API](https://policyiq.in/products/extract/ocr-api/) returns structured, validated fields, so the platform doesn't build its own document reading. - Insurer, KYC and payment connections: [PolicyIQ | Gateway](https://policyiq.in/products/gateway/) gives one standard pattern for insurer data, [identity verification](https://policyiq.in/products/gateway/kyc-verification-apis/), premium collection and messaging. - Automatic data checks: the [Comparison API](https://policyiq.in/products/match/comparison-api/) checks partner data files and policy versions without manual review. ### Build in-house, or build on existing infrastructure Insurance infrastructure: building it yourself vs using PolicyIQ APIs Capability Building in-house With PolicyIQ Insurer and partner connections One build per partner, maintained as each partner's API changes One standard integration layer, monitored for health and uptime Insurance document reading OCR plus insurance-specific field logic and validation to build and tune OCR API returning validated policy, proposal, motor and health fields Policy and data comparison Comparison logic to design for each document and dataset type Comparison API returning structured results Documentation for your team Written and kept current in-house Developer Resources for each integration ### Why it matters Building on existing insurance infrastructure lets an insurtech team spend its time on customer experience and product, rather than on rebuilding connections and document processing that already exist. ### Getting started Developers start from PolicyIQ | Gateway's Developer Resources and the standard Insurance API Integration pattern, then add the OCR API or Comparison API as needed. ### Further reading [Insurance APIs and Integrations Choosing an Insurance API Integration Partner What to ask an insurance API integration partner about coverage, reliability, monitoring, security and support before you commit. Read the article](https://policyiq.in/blog/insurance-apis/choosing-an-insurance-api-integration-partner/) - [Developer Resources for PolicyIQ | Gateway](https://policyiq.in/products/gateway/developer-resources/) - [Glossary: what is insurtech?](https://policyiq.in/glossary/#insurtech) Frequently asked questions ### FAQs for insurtech companies **Q: Can an insurtech build on top of PolicyIQ?** A: Yes. PolicyIQ | Gateway's Developer Resources document how to connect to insurer, KYC, payment and communication APIs, and PolicyIQ | Extract and Match are both available through their own APIs. **Q: Does PolicyIQ replace an insurtech's own product?** A: No. PolicyIQ | Gateway, Extract and Match are infrastructure an insurtech can build on, not a replacement for an insurtech's own customer-facing product. **Q: Where can a developer find PolicyIQ's API documentation?** A: PolicyIQ | Gateway's Developer Resources page is the starting point for insurer, KYC, payment and communication API documentation. **Q: Can an insurtech use PolicyIQ | Extract's OCR without adopting other PolicyIQ products?** A: Yes. PolicyIQ | Extract's OCR API is available on its own, so an insurtech can add document extraction without adopting the full PolicyIQ | One workspace. **Q: How is PolicyIQ priced for insurtech companies?** A: PolicyIQ does not publish prices, because cost depends on the products used, volumes and integration scope. Book a demo or contact sales for a quote. **Q: Is PolicyIQ | Match's comparison logic available as a standalone API?** A: Yes. The Comparison API exposes PolicyIQ | Match's policy and dataset comparison logic for an insurtech to call directly.