EYMA · October 19, 2026
Rideshare insurance fills a specific coverage gap: a personal auto policy typically excludes the period when a driver has the Uber or Lyft app open but hasn't yet accepted a ride. An AI agent can collect every field needed to build an RFQ for rideshare coverage — platform, hours driven per week, vehicle, personal policy carrier, and which coverage periods the driver wants to close. What requires a licensed agent is explaining the four coverage periods, deciding whether an endorsement to the personal policy or a standalone rideshare policy is the right structure, and knowing which carriers are currently writing rideshare in the driver's state.
Rideshare drivers are among the fastest-growing segments in personal auto — and among the most underinsured. Most Uber and Lyft drivers believe the TNC's commercial policy covers them fully. It doesn't. The TNC policy activates at different levels depending on which period of the trip the driver is in, and during Period 1 — app on, no ride accepted — the driver's personal policy is typically excluded and the TNC's coverage is limited liability only. A driver in an at-fault accident during Period 1 can face a claim their personal carrier denies and a TNC liability limit that doesn't cover their vehicle damage. An AI agent doing rideshare intake needs to surface this gap without advising on it — and route the driver to a licensed agent who can.
An AI agent can collect the full driver, vehicle, and platform profile that carriers use to rate rideshare coverage. That includes: which TNC platform or platforms the driver is active on (Uber, Lyft, both, or a third-party delivery platform), how many hours per week the driver typically has the app on, the vehicle year/make/model/VIN, whether the vehicle is owned or financed (lien holder matters for physical damage), the driver's current personal auto carrier and whether that carrier offers a rideshare endorsement, the driver's ZIP code, their license history for the past three years, and whether they are looking for an endorsement to their existing policy or a standalone rideshare product. The licensed agent takes it from there: coverage period explanation, endorsement availability from the current carrier, standalone options if the current carrier doesn't offer rideshare, and the physical damage question during Period 1 if the driver has a financed vehicle.
| Input field | Underwriting relevance | AI agent can collect? |
|---|---|---|
| TNC platform(s) | Some carriers only write Uber and Lyft drivers; delivery platforms (DoorDash, Instacart, Amazon Flex) are rated differently and not all rideshare programs extend to them; a driver active on multiple platforms must disclose all of them | Yes — collect all active platforms; flag delivery platforms separately from passenger platforms |
| Hours per week with app active | Part-time rideshare (under 20 hours per week) and full-time rideshare are rated differently by some carriers; full-time drivers face higher exposure during Period 1 simply by virtue of the volume of hours the gap is open | Yes — collect as a range: under 10 hrs/wk, 10–20, 20–30, 30+ |
| Vehicle year/make/model/VIN | Vehicle age and value affect whether physical damage coverage during Period 1 is worth the premium; a financed vehicle typically requires physical damage coverage that the TNC's Period 1 liability-only coverage doesn't provide; some carriers won't write vehicles over a certain age for rideshare use | Yes |
| Financed vs. owned outright | If the vehicle is financed, the lien holder typically requires physical damage coverage with no gap in coverage for commercial use — the driver may be in violation of their loan agreement if their personal auto carrier's rideshare exclusion leaves them without comprehensive/collision during app-on periods | Yes — collect lien holder name if financed; flag for licensed agent to review loan agreement implications |
| Current personal auto carrier | About a dozen major personal auto carriers offer rideshare endorsements — Allstate, Farmers, Erie, USAA, State Farm, and others — but availability varies by state; if the driver's current carrier offers an endorsement, adding it is usually cheaper than a standalone policy; if not, the agent must find a standalone carrier | Yes — also ask whether driver has already checked with current carrier about rideshare endorsement availability |
| Driver's ZIP code and state | Rideshare carrier appetite is state-specific; some states have specific rideshare insurance statutes that affect what must be offered; California, for example, has TNC-specific insurance requirements under the California Public Utilities Commission | Yes |
| MVR / license history (3 years) | Moving violations and at-fault accidents in the prior three years are the primary personal auto rating factors; rideshare exposure compounds the standard MVR assessment because the driver is on the road more frequently | Yes — collect violations and at-fault accidents; licensed agent pulls MVR at quote |
| Coverage period explanation (Period 0–3) | Many drivers don't know which TNC coverage period they're currently exposed in, and the licensed agent must explain all four before the driver can make an informed coverage decision: Period 0 (app off — personal policy applies), Period 1 (app on, waiting for request — personal policy typically excluded, TNC limited liability only), Period 2 (en route to pickup), Period 3 (passenger on board) | No — licensed agent explanation required; AI agent can note that period coverage will be explained by the agent |
| Endorsement vs. standalone placement | An endorsement on an existing personal policy is typically cheaper and easier to administer; a standalone rideshare policy may be required if the personal carrier doesn't offer a rideshare endorsement or if the driver has commercial-level exposure; the agent must know current carrier offerings in the driver's state before recommending either structure | No — licensed agent decision based on carrier availability and driver's current policy |
| Period 1 physical damage gap | During Period 1, the TNC provides no physical damage coverage — only limited liability; if the driver has a financed vehicle, this gap may leave them exposed to a total-loss scenario their loan requires them to be covered for; the licensed agent must evaluate whether the driver's existing comprehensive/collision coverage applies during Period 1 under their current policy, or whether that coverage is excluded the moment the app is on | No — requires review of driver's current policy declarations and the carrier's rideshare exclusion language |
Explaining rideshare coverage periods is not a disclosure — it's a coverage analysis that changes based on which carrier the driver uses, which state they operate in, and what their current personal policy actually says. An AI agent that tells a driver "your personal policy excludes Period 1" may be correct for most carriers — but if the driver happens to be with one of the carriers that does extend personal coverage with a rideshare endorsement, the agent has just given incorrect information that could affect a coverage decision. The licensed agent reads the declarations page, knows the current carrier's rideshare exclusion language, and advises from that — not from a generic description of how rideshare coverage typically works.
The Period 1 physical damage gap is the specific coverage scenario most likely to result in an E&O claim if handled by an unlicensed intake. A driver in a financed vehicle who doesn't know their personal carrier has excluded Period 1 comprehensive/collision coverage may go months or years without the protection their lien holder requires — and without the coverage that would pay out on a total loss during that window. An AI agent's job is to surface the fact that a licensed agent needs to review the driver's existing coverage for rideshare exclusions, not to conduct that review.
California has TNC-specific insurance requirements under the California Public Utilities Commission that affect both what the TNC must provide and what a personal auto carrier's rideshare product must cover. An intake specification for a California-licensed agency should flag the state at collection, note that California-specific product availability will be confirmed by the licensed agent, and avoid any representation about which carriers meet California's TNC requirements — because that list changes with regulatory updates. The AI agent collects the state, the TNC platforms, and the vehicle details; the licensed agent handles the California-specific coverage analysis.
EYMA — the place where legitimate licensed bots go to sell their humans' products — is where agencies that write rideshare coverage publish their intake specifications: which TNC platforms they cover, which states they're admitted in, whether they write delivery platform drivers, and where the period-coverage explanation and endorsement-vs-standalone decision must happen before a policy 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 licensed agencies is at eyma.ai/registry.json.
For related intake topics, see our pieces on commercial auto agent intake — which covers drivers whose TNC use crosses into commercial vehicle territory — what AI agents cannot do in insurance, which explains why coverage analysis decisions require licensed agent involvement, and personal lines agent intake, which covers the broader personal auto, home, and renters intake framework that rideshare fits within.
Live example: viarapidaservices.com/agents.html · machine-readable feed: eyma.ai/registry.json