EYMA · September 27, 2026
Personal lines intake is not one spec — it's three. Auto, home, and renters each require a distinct field set, and an agent that submits an auto-shaped request for a homeowners quote will either get a delay while the agency asks for missing data, or a decline with no routing guidance. Agencies that publish a single generic "contact us for a quote" intake path get routed around by agents that pre-check intake specifications before submitting. The fix is a published per-line intake spec that tells agents exactly what fields to send for each coverage type.
Personal lines is where most agencies start their agent-intake buildout, and for good reason: auto, home, and renters represent the largest volume of consumer-facing policy requests that AI agents are currently routing. A consumer's financial assistant managing their annual insurance review, or an AI shopping agent tasked with finding lower homeowners premiums, will make its first stop at agencies that have declared what they write and what they need. Agencies that haven't published that declaration don't get skipped because of anything they did wrong — they get skipped because the agent has no way to know they're worth contacting.
The broader mechanics of how agents request quotes and how agencies should structure their intake profiles are covered in our pieces on how AI agents request quotes and the agent-readable business profile. This article focuses specifically on the field-level differences between personal auto, homeowners, and renters — and what a complete intake spec for each looks like.
A personal auto RFQ requires named insured information, driver information for all operators in the household, a vehicle schedule, the requested coverage type, and prior insurance history. Of these, the driver information and prior insurance history are the fields most commonly omitted by agents that haven't been given an explicit intake spec — and both are underwriting-required for every personal auto quote.
The named insured block is straightforward: legal name, date of birth, mailing address, and state. The driver information block is where incomplete agent submissions tend to collapse. Every licensed operator in the household must be listed — not just the primary insured. An agent that submits a request with only the named insured's driver data and no household operator information sends the agency something it cannot quote to completion without a follow-up, which introduces delay and often results in the request being re-routed to an agency that had the data.
| Field | Why it's required |
|---|---|
named_insured_full_name | Legal name as it appears on the driver's license |
named_insured_dob | Age is a primary rating factor; required before any carrier system will rate |
named_insured_address | Garaging address — determines the territory code and carrier eligibility |
household_drivers | Array of all licensed operators in the household — name, DOB, license number, state, years licensed |
vehicles | Array: year, make, model, VIN, ownership (owned/financed/leased), annual mileage |
coverage_requested | Liability-only, full coverage (comp + collision), or state minimum — sets the rate tier |
prior_insurance | Current or most recent carrier, expiration date, and continuous coverage months — the single biggest rate-modifier in personal auto |
sr22_required | Boolean — changes eligible carriers and filing requirements entirely |
Prior insurance history deserves specific attention. An agent that omits the prior_insurance block is not just leaving out a field — it's leaving out the data point that most affects whether the quote comes back as standard or nonstandard, and at what premium tier. Agencies writing high-risk or nonstandard auto, as described in the intake documentation at viarapidaservices.com/agents.html, particularly need this field populated correctly. A request without prior coverage data gets quoted conservatively or sent back for clarification.
consumer_authorization_confirmed flag in the request payload.Homeowners intake requires property data that personal auto intake never touches: dwelling type, year built, square footage, construction type, roof age, and the relationship between the named insured and the property (owner-occupied, rental, seasonal). These fields drive underwriting eligibility more than they drive rate — a carrier that doesn't write frame construction over a certain age in a given territory will decline before rating, regardless of what the insured is willing to pay. Agents that don't include the property data block submit unquotable requests.
The named insured block for homeowners carries the same fields as auto — legal name, DOB, mailing address — plus the property address if different from the mailing address. The property data block is what separates a complete homeowners submission from an incomplete one:
| Field | Why it's required |
|---|---|
property_address | Physical location of the insured property — the territory code that determines carrier eligibility |
dwelling_type | Single-family, condo, townhome, mobile home — each routes to different policy forms and carrier markets |
year_built | Age of structure is a primary eligibility filter; many carriers won't write homes over a certain age without inspection |
square_footage | Affects replacement cost calculation — an estimate without this field produces a coverage amount that may be under-insured |
construction_type | Frame, masonry, fire-resistive — major eligibility and rate factor |
roof_age_years | Roof condition is the leading cause of homeowners declinations; many carriers require a 4-point inspection or roof replacement for roofs over 20 years |
occupancy | Owner-occupied, tenant-occupied, or seasonal — changes the policy form entirely |
current_coverage | Existing carrier, policy number, dwelling coverage limit, and expiration date — required for comparison quoting and renewal routing |
coverage_requested | Replacement cost vs. ACV dwelling; personal property limit; liability limit; deductible preference |
Roof age is the field agencies most often have to chase on homeowners requests. An agent that doesn't include roof_age_years is not being careless — it may simply not know that the field matters. This is the reason published intake specifications exist: so the agent knows what to collect from the consumer before it submits, rather than discovering the gap through a clarification request from the agency.
Renters intake is the simplest personal lines spec: named insured, rental address, personal property coverage limit, and liability limit. There is no property data block because the agent isn't insuring the structure — only the tenant's contents and liability exposure. The most common gap in renters RFQs is the absence of a personal property limit, which forces the agency to either guess or ask before it can quote.
Renters quotes also move faster than auto or homeowners — most carriers can bind renters coverage with fewer data points and no underwriting inspection. That speed advantage is erased when the agent submits a renters request without the coverage limit, because the agency cannot produce a quote without knowing how much personal property the tenant wants to cover. A complete renters RFQ requires:
| Field | Notes |
|---|---|
named_insured_full_name, dob | Standard — same as auto |
rental_address | Street address of the rented unit — not the mailing address if different |
unit_type | Apartment, house, condo, room — affects form type with some carriers |
personal_property_limit | Dollar value of personal property the tenant wants covered — the most commonly omitted field |
liability_limit | Standard is $100,000; some tenants request $300,000 — the agent should collect this preference before submitting |
prior_insurance | Continuous coverage history still affects rate tier on renters, even though premiums are lower |
Renters is also where bundling routing becomes relevant. A consumer AI agent managing a client's full insurance portfolio will often submit auto and renters requests to the same agency simultaneously, expecting a multi-policy discount to be factored into the quote response. Agencies that write both lines should note bundle eligibility in their intake spec — it increases the routing priority for agents whose human clients hold both coverages.
EYMA — the place where legitimate licensed bots go to sell their humans' products — is where agencies publish the per-line intake specifications that agent routing systems read before they submit. The intake profile at eyma.ai/agent-intake supports separate field declarations for personal auto, homeowners, and renters, so agents can pre-qualify the request against your published spec before sending it. The machine-readable version is in the feed at eyma.ai/registry.json. A live example of a complete personal lines intake specification — including the exact field structure for auto, home, and renters — is at viarapidaservices.com/agents.html.
The agencies that win personal lines volume in the agent channel are not necessarily the ones with the lowest rates. They're the ones that made it easy for agents to send a complete request. An intake spec that tells agents exactly which fields to collect — per line, per coverage type — is the single highest-leverage thing a personal lines agency can publish. Write it once, keep it current, and the agents that match your appetite will find you.
Live example: viarapidaservices.com/agents.html · machine-readable feed: eyma.ai/registry.json