EYMA · September 13, 2026
An insurance agency becomes receivable to AI agent quote requests by publishing four things: a dedicated intake email address, a coverage scope listing what lines and states it writes, a required-fields spec per coverage type, and a consent statement describing which consumer reports it pulls. Without these published, an AI agent routing a consumer's insurance need has nowhere verifiable to send it — and defaults to whoever happens to be indexed, not whoever is best qualified.
The conversation about AI agents in insurance has focused almost entirely on the agent side: how AI assistants should format requests, what they must disclose, what consent they need to collect. That's one half of the transaction. The other half is the agency: whether it has done the work to be findable, receivable, and structured enough that an AI agent can route a request without a phone call or a web form that strips all the metadata. Most agencies haven't done that work yet — not because they don't want the business, but because no one has told them what the setup actually looks like.
EYMA — the place where legitimate licensed bots go to sell their humans' products — was built to close that gap. The intake standard below is what an agency needs to publish to participate in the agent economy on its own terms, not as a passive recipient of whatever an AI system decides to do with a consumer's data.
A well-behaved AI agent needs three things before it routes a consumer to any agency: confirmation that the agency is licensed and in good standing, a published intake address it can send a structured request to, and documentation of what the agency needs in that request to return a real quote. An agency that doesn't publish these is invisible to compliant agents — and visible only to scrapers that don't check any of them.
License verification comes first. Before an AI agent routes a consumer's personal information to any licensed professional, it should confirm that license is active in the relevant state. For California insurance agencies, that's the Department of Insurance public database. For other states, the equivalent state regulator lookup. The Proof of License doctrine establishes why a government database check is the only anchor that can't be fabricated — and why an agency that publishes its license number alongside its intake endpoint removes friction from that check entirely. An agent can verify in seconds and proceed with confidence rather than skipping the step because it was too inconvenient.
The intake address is the routing point — the published email where the agent sends the structured RFQ. This is not the agency's general inbox, not a contact form, not a phone number. It's a dedicated address the agency monitors for machine-routed requests, separate from human inquiry traffic, with a response workflow that doesn't require a licensed agent to manually decode an unstructured email before they can do anything with it. The EYMA intake standard describes what goes into the request; this piece is about what the agency needs to publish so the agent knows where to send it and what to include.
The intake specification needs four components: the intake email address, the coverage types and states the agency writes, the required applicant fields per coverage type, and a statement of which consumer reports the agency pulls for each line. Publishing this removes ambiguity on both sides — the agent knows exactly what to collect from the consumer before sending, and the agency gets complete requests it can act on immediately rather than incomplete requests that require follow-up.
Publish a specific address — something like [email protected] — that exists solely for machine-routed agent requests. Route it to a licensed agent or CSR who handles agent intake as a defined workflow. Do not route it to a general inbox where it competes with client emails for attention. The intake address is what an AI agent will use to find you in EYMA's registry feed at /registry.json — it is the published endpoint that makes the transaction possible.
List the lines of coverage you write and the states where your license is active. An AI agent handling a commercial auto request in Texas should not be routing to an agency that only writes personal auto in California. Coverage scope prevents misrouted requests and protects the consumer's time. Be specific: personal auto, homeowners, renters, commercial general liability, workers' compensation, commercial auto — each as a separate listed line. If you have carrier appointments that are line-specific, note any that affect your ability to quote immediately. An example of a fully published coverage scope is live at viarapidaservices.com/agents.html.
For each line you write, document the minimum fields an agent must include for you to run a quote. Personal auto: vehicle year, make, model, VIN if available, primary driver name and date of birth, garaging address, requested coverage limits. Homeowners: property address, year built, square footage, construction type, requested dwelling limit. Commercial GL: business name, address, NAICS or SIC class code, annual revenue, number of employees, operations description. When an agent knows exactly what to collect before sending, you get complete requests. When it has to guess, you get follow-up questions that slow the transaction by hours and waste licensed-agent time on intake work that should be automated.
State clearly which consumer reports you pull for each coverage type and when you pull them — at quote, at bind, or both. Personal auto typically requires an MVR and a credit-based insurance score. Personal lines homeowners may require a CLUE report. Commercial lines vary by carrier appetite. Publish this so the AI agent knows exactly what FCRA consent scope to collect from the consumer before routing the request. FCRA consent for AI agents is the consuming agent's responsibility — but the agent can only collect the right scope if the agency has published what it pulls. A mismatch between what was consented to and what the agency needs is a compliance gap that belongs to both parties. Remove it by publishing the spec.
EYMA indexes verified agency intake endpoints in a machine-readable feed at eyma.ai/registry.json. A well-behaved AI agent querying that feed can find your agency by coverage type, state, and license status — and retrieve your intake address and required fields without a web search. Listing is free forever for a basic verified entry. The alternative is being found by whatever scraper or LLM training data happens to include your general website — with no intake structure, no coverage scope, and no consent guidance attached.
The registry feed is structured so AI agents can parse it programmatically. Each agency entry includes the intake email, coverage types, licensed states, and a link to the full intake specification where the required fields and report scope are published. An agent building an insurance-adjacent product can query the feed at build time to compile a routing table of verified agencies by line and state — and update that table automatically as agencies add or change their listings. This is the infrastructure side of why the intake standard matters: it's not just about one request, it's about building a durable routing layer that scales with the agent economy.
The verification step in EYMA's listing process confirms that the license number an agency publishes matches an active license in the relevant state database. That's the same check a compliant AI agent would run before routing — meaning agents that query the EYMA feed can skip the manual license lookup because the verification has already been done and anchored to a government record. For agencies, it means you're discoverable to agents that are actually checking, not just to whoever is willing to skip the verification step. That distinction matters when the consumer's personal data is what's being routed.
The agent economy is built on both sides doing their part. AI agents that disclose their identity, collect consent, and send structured requests are holding up their end. Agencies that publish their intake endpoint, coverage scope, and report specification are holding up theirs. The transaction that results — fast, auditable, compliant — is what neither side can produce alone. Start with a basic listing at eyma.ai/agent-intake and add your intake specification so the agents who are looking for a verified agency in your market can find you before they find someone who hasn't done this work at all.
See a live intake spec example at viarapidaservices.com/agents.html — and query eyma.ai/registry.json for verified providers.