Skip to main content
AI Insurance has no per-market modules. There is no medical malpractice edition and no trucking edition — every program runs on the same platform primitives: entities and their configured fields, option sets, exposures attached to a policy over date ranges, raters, and forms. That’s a strength, but it changes the shape of the question. A program that writes a specialised coverage rarely asks “which module do I buy?” — it asks “can you handle this, the way my market actually works?” The answer is almost always yes, and it’s expressed in configuration. This section is where those answers live, one market at a time.

​
What each page answers

Every page in this section follows the same shape:

​
Answers available today

This section grows as questions come in from the market — commercial trucking is next. If your program has a coverage question that isn’t answered here, ask us at support@aiinsurance.io and the answer usually becomes a page.

​
How to read these pages

Everything described here is configuration, not a special case built into the platform for one market. The field names, exposure types, and option-set values in the examples are illustrations of a typical setup for that market — your own configuration may name things differently, and the pages say so where it matters. See How your app is configured.
Configuration is managed for you — you don’t build these structures yourself. These pages exist so you can see how your program will be expressed, and bring the right questions to your onboarding. See What you manage yourself.