EYMA · October 14, 2026
Earthquake damage is excluded from nearly every standard homeowner and commercial property policy — which means earthquake insurance is always an add-on or a stand-alone purchase, never automatic. In California, the dominant residential option is the California Earthquake Authority (CEA), offered through participating carriers; stand-alone admitted options also exist for both residential and commercial risks. An AI agent can collect the structural and location fields that drive an earthquake RFQ: address, year built, construction type, foundation type, number of stories, whether a seismic retrofit has been completed, and the consumer's current homeowner carrier. What requires a licensed agent is deductible adequacy review, hazard zone eligibility determination, and the decision between CEA and admitted standalone options — three judgment calls where errors leave consumers holding a deductible they cannot cover or coverage that does not pay.
Earthquake insurance is purchased voluntarily, which means consumers who buy it are already motivated — and consumers who don't buy it often believe their homeowner policy covers shaking. An AI agent doing intake for earthquake coverage is serving a consumer who has made a decision, not one who needs to be persuaded. That makes the intake process relatively straightforward on the demand side. The complexity is on the supply side: CEA participation rules, percentage deductibles that are large in dollar terms on high-value properties, soil and liquefaction zone eligibility, and construction type restrictions that disqualify some buildings entirely from certain carriers. Getting the building profile right in the RFQ is how an AI agent ensures the quote the consumer receives actually reflects their property.
An AI agent can collect every structural and factual field about the dwelling or building that earthquake underwriters use to rate and evaluate eligibility: full address (used for fault proximity and soil zone lookup), year built, dwelling construction type, foundation type, number of stories, whether a voluntary seismic retrofit has been completed, the current homeowner carrier name, and the desired coverage amounts for dwelling, personal property, and additional living expenses. What it cannot determine is whether those coverage amounts are adequate relative to the deductible structure, or whether the property's hazard zone classification makes it eligible at all carriers the agency represents.
| Input field | Underwriting relevance | AI agent can collect? |
|---|---|---|
| Full property address | Used for fault zone proximity, soil type, and liquefaction zone lookup — primary rate-territory inputs | Yes |
| Year built | Older construction carries higher shake vulnerability; some carriers decline pre-1979 unreinforced masonry | Yes |
| Dwelling construction type (wood frame, masonry, concrete tilt-up) | Wood frame performs better in earthquakes than masonry; construction type is a primary eligibility variable | Yes — collect what the consumer knows; flag masonry for licensed agent review |
| Foundation type (raised/cripple wall, concrete slab, post-and-pier, basement) | Cripple wall foundations are the highest-frequency failure point; retrofit history matters here | Yes |
| Number of stories | Affects shake response modeling and some carrier eligibility rules | Yes |
| Seismic retrofit completion (yes/no) and type | Cripple wall bolting and bracing reduces both loss probability and premium on most carriers | Yes — collect whether retrofit was completed and approximate year |
| Current homeowner carrier (for CEA pairing) | CEA is sold through participating homeowner carriers — the consumer must buy CEA through their existing HO carrier or a participating one | Yes — required to determine CEA eligibility path |
| Desired dwelling coverage amount | Must equal or align with the HO dwelling limit in most CEA policies; drives deductible dollar exposure | Yes — but flag for deductible adequacy review |
| Desired personal property coverage amount | CEA personal property coverage is capped; admitted standalone carriers may offer higher limits | Yes |
| Desired additional living expense (ALE) amount | ALE covers temporary housing during repairs — standard CEA amounts are fixed; some consumers need higher | Yes |
| Prior earthquake losses (count, amounts, dates) | Affects eligibility with admitted carriers; CEA does not use prior earthquake losses in rating but admitted carriers may | Yes |
| Liquefaction zone or fault zone determination | State geologic hazard zone maps drive some carrier exclusions and eligibility rules | No — requires licensed agent review using state maps |
| Deductible adequacy review | Earthquake deductibles are percentage-based (5–25% of dwelling limit) — dollar exposure requires calculation and consumer disclosure | No — licensed agent must calculate and disclose dollar amount |
| CEA vs. admitted standalone recommendation | Depends on HO carrier, building type, coverage needs, and price comparison — suitability judgment | No — requires licensed agent comparison and recommendation |
Earthquake deductibles are not flat dollar amounts — they are percentages of the insured dwelling value, typically ranging from 5% to 25% depending on the carrier, zone, and construction type the consumer chooses. On a home insured for $500,000, a 15% deductible means the consumer pays the first $75,000 of any earthquake loss before coverage begins. Most consumers who ask an AI agent to find them earthquake insurance are not thinking in those terms. A licensed agent who states the dollar equivalent before the consumer binds coverage is satisfying a disclosure obligation that protects both the consumer and the agency from a claim where the consumer says they did not understand their deductible.
This is the core reason earthquake intake cannot be fully automated through to bind. The fields an AI agent collects produce a quotable submission — but the quote will include a deductible percentage that translates into a large dollar figure, and that dollar figure must be disclosed by a licensed agent before the policy is issued. Publishing an intake specification that routes the RFQ to a licensed agent for deductible disclosure and suitability review before binding is not a compliance formality. It is the step that prevents the outcome where a consumer discovers their $80,000 deductible at the moment their foundation cracks.
An intake specification for earthquake coverage should direct the AI agent to collect the current homeowner carrier as a required field and flag for the licensed agent whether that carrier participates in CEA. From there, the licensed agent compares CEA pricing and coverage structure against admitted standalone options for that specific building type and location. CEA policies use standardized coverage forms with fixed ALE amounts and personal property caps; admitted standalone carriers may offer higher limits, broader forms, or lower deductibles for some risk profiles. That comparison is a suitability judgment — it belongs to the licensed agent, not the intake workflow.
EYMA — the place where legitimate licensed bots go to sell their humans' products — is where earthquake-writing agencies publish the intake specifications that tell AI agents which structural fields to collect, what the CEA carrier question requires, and where the deductible disclosure and product comparison step must happen before any quote is issued. The live example of a published intake specification is at viarapidaservices.com/agents.html. The machine-readable feed that AI agents use to discover which agencies write earthquake coverage in California and other states is at eyma.ai/registry.json.
For related intake mechanics, see our pieces on homeowners agent intake — which covers the underlying HO policy that earthquake coverage pairs with — flood insurance intake (the other major peril exclusion from standard HO policies, with its own federal program structure), and what AI agents cannot do in insurance, which explains why percentage deductible disclosure and hazard zone suitability determinations are permanently in the licensed-agent column.
Live example: viarapidaservices.com/agents.html · machine-readable feed: eyma.ai/registry.json