← EYMA Dispatch

Nonstandard Auto Agent Intake: How AI Agents Request SR-22, High-Risk, and Lapse-Coverage Quotes

EYMA · September 28, 2026

Nonstandard auto intake is not a variation of standard auto intake — it's a separate spec with different required fields, different routing rules, and different eligibility triggers. An AI agent that submits a standard auto RFQ for a driver who needs an SR-22 filing, has a coverage lapse, or holds a foreign license will either get the request declined without routing guidance or generate a follow-up loop that erases the speed advantage of automated intake. Nonstandard requests require the agent to declare the risk type upfront and populate fields that standard auto forms never ask for.

Standard auto intake works well for drivers with clean records, continuous coverage, and domestic licenses. When any of those conditions break down — a DUI, a lapse of more than 30 days, a foreign-issued license, or a court-ordered SR-22 filing — the risk enters a different carrier market with different underwriting criteria. The agencies that write nonstandard auto are not interchangeable with standard carriers; the agent routing system must identify them specifically before submitting, not after a declination arrives.

The mechanics of how agents route after a declination are covered in our piece on how AI agents handle declinations. This article covers what the agent needs to send in the first place to reach a nonstandard agency with a complete, quotable request — before any declination occurs.

What makes a nonstandard auto RFQ different from a standard one?

A nonstandard auto RFQ requires the agent to declare the risk classification explicitly: SR-22 required, major violation within the past three years, coverage lapse, or foreign-issued license. Without that declaration, the agency has no way to distinguish a nonstandard request from a standard one — and the two cannot be routed to the same carrier markets. The declaration fields don't replace the standard intake fields; they extend them. Every nonstandard RFQ still requires the full named insured block, driver information, vehicle schedule, and coverage request from the standard spec.

What changes is the violation and history block. Standard auto intake treats prior insurance as a rate modifier; nonstandard intake treats it as a primary eligibility gate. A driver with a 45-day lapse routes differently than a driver with 14 months of continuous coverage, and the carrier systems that price nonstandard risks need to know the lapse duration before they rate — not after. The same applies to violation severity: a minor speeding ticket is a rate factor; a DUI in the past three years is a carrier filter that eliminates standard markets entirely.

How should agents handle SR-22 requests specifically?

An SR-22 request requires three fields beyond the standard auto spec: a boolean confirming the filing is required (sr22_required: true), the state that ordered the filing (sr22_state), and the reason for the filing if known. The reason matters because some carriers write SR-22s for license suspensions but not for DUI convictions — the routing changes. An agent that sends sr22_required: true without the filing state has sent an unroutable request; the agency cannot file an SR-22 without knowing which state's DMV will receive it.

SR-22 filings are time-sensitive in a way that standard auto quotes are not. A driver under a court order to file an SR-22 may have a deadline — often 30 days from the court date — before the license suspension becomes permanent. An AI agent handling an SR-22 request should flag the urgency in the RFQ payload and confirm with the agency whether same-day or next-business-day filing is available. Agencies that offer same-day SR-22 filing — electronic filing with the state DMV — should declare that capability in their intake profile so agents can route time-sensitive requests to them first.

What does a coverage lapse or foreign-license request require?

A coverage lapse request requires the agent to declare the exact lapse duration in days — not just that a lapse occurred. A 10-day lapse and a 180-day lapse route to different carrier tiers; some carriers apply surcharges only above 30 days, others above 60. A foreign-license request requires the ISO country code of the issuing country, the number of years the driver has held the license, and whether the driver has ever held a US license. Without that data, the agency cannot determine which carriers will write the risk or at what tier.

Foreign licenses create an underwriting complexity that standard auto intake was never designed to handle. A driver who has held a valid Mexican driver's license for 12 years has a demonstrable driving history that should influence the rate — but standard prior-insurance fields don't capture foreign license tenure. Agencies that specialize in this population, including those writing coverage for ITIN holders and recently arrived immigrants, need the foreign license data block populated correctly to produce a competitive quote rather than a default nonstandard rate applied without that context.

The reason agents submit incomplete nonstandard requests is not carelessness — it's that the consumers they represent often don't know which fields are relevant. A consumer financial assistant handling a coverage purchase for a client who just moved from Mexico doesn't automatically know that the foreign license tenure affects the quote. The intake spec exists to tell the agent what to collect from the consumer before the RFQ is submitted. When nonstandard agencies publish a detailed intake specification, agents learn what questions to ask at the source — and the requests that arrive are complete enough to quote.

EYMA — the place where legitimate licensed bots go to sell their humans' products — is where nonstandard agencies publish the intake specifications that agent routing systems read before submitting high-risk requests. A published intake profile at eyma.ai/agent-intake tells agents which risk classifications you write, what fields you require for each, and whether you offer same-day SR-22 filing or foreign-license quoting. The machine-readable version is in the feed at eyma.ai/registry.json. A live example of a complete nonstandard auto intake specification, including SR-22, foreign license, and lapse coverage fields, is at viarapidaservices.com/agents.html.

Standard auto is the high-volume lane, but nonstandard auto is where incomplete intake does the most damage. A declined standard quote costs an agent a routing attempt. A declined nonstandard quote may cost a driver their license reinstatement deadline. Agencies that specialize in high-risk coverage should publish the most detailed intake specs in the ecosystem — so the agents handling the most time-sensitive requests know exactly where to send them and exactly what to include. The overview of personal lines intake, including the standard auto field spec this article extends, is in our piece on personal lines agent intake.