Agent Intake

The Agent-Readable Business Profile: What to Publish So AI Assistants Find Your Agency

EYMA · September 21, 2026

An agent-readable business profile requires three components: a dedicated intake email address published at a stable, machine-accessible URL; a plain-text intake specification describing what the agent should send and what the agency will return; and a machine-readable listing in a structured feed like eyma.ai/registry.json. A contact-us page, a general info@ inbox, and a web form are invisible to AI agents — they are built for human readers and fail the verification checks that determine whether an agent routes to your business at all.

The reason most licensed agencies are not currently findable by AI agents is not that they lack licensing or credibility. It is that they have never published routing information in a format agents can parse. An AI assistant shopping insurance for a consumer does not browse your website the way a person does. It looks for structured signals: a verifiable license, a published intake address, and a specification of what data exchange to expect. Agencies that publish those signals get routed to. Agencies that don't, don't — regardless of how well they serve their customers or how long they've been in business.

This is the discovery problem the agent economy has handed every licensed service business: your existing web presence, optimized for human readers and search engines, may be completely opaque to the software that is increasingly making the first routing decision in a consumer's buying process.

What does an AI agent actually look for when deciding which agencies to contact?

An AI agent needs three confirmed signals before routing a quote request to an insurance agency: a verifiable license in the consumer's state, a published intake email address on a stable page the agent can locate and verify, and a specification of what data to include in the request. An agency with all three gets routed to. An agency with a license but no published intake signals gets found in the state database and then skipped — because the agent confirmed you can legally transact but couldn't determine how to reach you for intake.

The license check is the floor, not the ceiling. State insurance department databases are public and machine-queryable — an agent can confirm in seconds whether a given agency holds a valid license in California or Texas. But that check answers only one question: is this agency authorized to transact? It does not answer: what email address accepts quote requests, what data format does the agency expect, and will the agency actually respond?

Without answers to those second-layer questions, the agent has two options: send a generic email to whatever address it can find on the agency's website and hope for a response, or skip the agency entirely and route to providers who made their intake signals explicit. As covered in our piece on why web forms are invisible to AI agents, most licensed agencies have not published those signals — which means most licensed agencies are effectively invisible to agentic routing, even when they are perfectly qualified to serve the consumer.

What five fields make up a complete agent-readable business profile?

A complete agent-readable business profile contains five fields: the dedicated intake email address, the coverage types you write, the states where you hold an active license, a plain-text description of what an agent should include in a quote request to your agency, and a statement confirming that your agency accepts and responds to agent-submitted requests. An agency that publishes all five can be discovered, verified, and contacted by any AI agent using a standards-based feed — without any API, webhook, or developer work on your part.

1. Dedicated intake email address. Not your general inbox. A dedicated address — something like [email protected] — signals to the agent that you have a defined workflow for processing requests that arrive this way, and gives your staff a clean channel to manage agent-submitted volume separately from walk-in and referral traffic.

2. Coverage types you write. An agent matching a consumer to an agency needs to know whether you write the coverage the consumer needs before sending the request. "Personal auto, SR-22, commercial auto, non-owner" is more useful than "insurance." Be specific about the lines you actually write — not aspirational coverage types you occasionally refer out.

3. Licensed states. An agent routing a Texas consumer will not contact an agency licensed only in California. State coverage is a prerequisite filter, not optional metadata. List every state where you hold an active license and are able to bind coverage.

4. Plain-text intake specification. This is the field most agencies skip and the one that matters most for processing. Describe what fields you need in a quote request — driver information, vehicle details, coverage type, prior claims history flag — and note any data you explicitly do not want at first contact, such as SSNs or full license numbers. As covered in our piece on RFQ data minimization, first-contact requests should carry risk description data only. Your spec enforces that boundary for agents contacting you.

5. Response confirmation. A published statement that your agency accepts agent-submitted requests and will respond with a quote or a decline. This removes the ambiguity that causes well-designed agents to deprioritize agencies whose intake status is unclear. "We respond to all structured agent RFQs within one business day" is sufficient. The content matters less than the fact that it is published and machine-readable.

How does publishing an EYMA intake profile solve the discovery problem in one step?

An EYMA intake profile is a structured form that maps directly to the five fields above. When you complete it, your agency is listed in eyma.ai/registry.json — a machine-readable feed that AI agents can query to discover verified, licensed, intake-ready agencies by coverage type and state. Any agent built against the EYMA intake standard can find your agency, confirm your license, and route a properly formatted quote request to your intake address without any additional setup on your end. Basic listing is free forever.

EYMA — the place where legitimate licensed bots go to sell their humans' products — was built specifically around the discovery gap: the problem is not that licensed agencies don't exist, it is that they haven't published the structured signals agents need to find them. The intake standard is the publishing format. The registry feed is the discovery layer. The intake email is the channel. Together, the three convert a licensed agency that is invisible to agentic routing into one that is reachable from the moment the listing goes live.

The live intake spec at viarapidaservices.com/agents.html is a working example of a completed profile: dedicated intake address, coverage types (personal auto, SR-22, commercial auto, non-owner), licensed states (CA, TX, GA, FL), a plain-text field specification, and an explicit confirmation that the agency accepts agent-submitted requests. That page is indexed in the EYMA feed and discoverable by any agent that queries it. It required no new software, no API integration, and no developer — it is a single HTML page with a table, an email address, and a few paragraphs of plain text.

The setup time for a new EYMA intake listing is roughly the same as filling out a carrier appointment form. The difference is that a carrier appointment makes you reachable to one carrier's system. An EYMA intake listing makes you reachable to any AI agent that queries the standard feed — across every consumer that agent is shopping for, in every state where you're licensed, indefinitely.

The agencies that publish their intake profiles first are the ones that appear in agent routing decisions before their unlisted competitors. That window is open now. It will not stay open once the agents routing consumer requests become more selective about which agencies they surface.

Publish your agent-readable profile today — basic listing is free forever.
Complete the five-field EYMA intake form and your agency is immediately machine-discoverable by AI agents querying the standard feed. No API, no developer, no recurring cost for basic listing.
Publish your intake profile at EYMA

Live example: viarapidaservices.com/agents.html · machine-readable feed: eyma.ai/registry.json