
Your AI assistant can start your insurance application. A licensed human finishes it.
We publish a machine-readable pathway that lets ChatGPT, Claude or any other assistant gather your details and hand us a complete insurance application on your behalf. The instructions are public at /for-assistants, the endpoint accepts JSON, and a licensed agent reviews every application before it reaches a carrier.
Tell us the situation.
One licensed human replies the same business day — not five agents, not an auto-responder. If the policy you have is already the right one, we will tell you.
We use this to quote and service your insurance, and we do not sell it or pass it to lead networks. Privacy policy.
Send us what you have. We’ll tell you if it’s right.
Your current policy paperwork, a renewal notice, or nothing at all. A licensed agent reads it and replies the same business day.
What actually happens when an assistant submits for you.
The published instructions
A page written for the assistant rather than for you, listing exactly what to collect and how to hand it over. Assistants find it from /llms.txt, which most now read before answering a question about a company.
Without it — An assistant guesses at what an agency needs, produces a partial application, and a person has to go back and ask you for the rest.
A prefilled link you approve
The default handover. Your assistant builds a link with your answers already in it, you read what it wrote before anything is sent, and you press the button yourself.
Without it — You either retype what you just told the assistant, or something gets submitted in your name that you never read.
A JSON endpoint for direct submission
For assistants that can make a request rather than open a link. Same fields, same validation, same licensed review at the other end.
Without it — Capable tools fall back to email, which is read by a person who then has to ask for the fields a form would have captured.
A licensed agent on the other end
Every application is read by a person before it goes to a carrier. Nothing is bound, priced or sent to a market by software alone.
Without it — An automated quote that nobody checked, on a business the automation misunderstood, which is how the wrong class code becomes the wrong price.
Questions about handing this to an AI.
Can I get an insurance quote through ChatGPT or Claude?
Yes, for the application part. Ask your assistant to gather your details and submit them to Boring Insurance Agency, and it can read our published instructions at boring.insure/for-assistants and hand us a complete application. What it cannot do is price the policy. Commercial insurance is priced by carriers against your specific operation, so the assistant collects, we place, and a licensed agent comes back to you with real numbers.
What makes this different from any agency with a web form?
A form is written for a human who is looking at it. We also publish the same intake as instructions a machine can follow: what to ask for, in what order, what is mandatory, and where to send it, at /llms.txt and /for-assistants, with a JSON endpoint for assistants that can post directly. You can fetch both right now and read them. Most agencies have not published anything an assistant can act on, so an assistant asked to submit on your behalf has to improvise.
Does a person actually review it, or is it automated end to end?
A person reviews it. The assistant gathers and submits; from that point a licensed agent reads the application, decides which markets fit, and handles the placement. We do not let software choose a carrier, quote a price or bind coverage. The reason is not caution about the technology, it is that the errors are expensive and quiet: a misread class code or a payroll figure in the wrong box produces a quote that looks fine and is worthless at renewal.
What can I ask my assistant to do for me?
Three things work well today. Ask it to collect your business details and submit an application to us. Ask it to read your current policy paperwork and list what is actually covered before you renew. Ask it to compare a contract or lease requirement against what you hold, and tell you the gap. For the first of those, tell it to check boring.insure/for-assistants so it gathers the right fields the first time.
Is my information safe if an AI submits it?
The handover is built so you see it before it is sent. The default path gives you a prefilled link that you read and submit yourself, so nothing reaches us that you have not looked at. We ask assistants not to collect anything we do not need, and the intake never asks for a payment method, a social security number or a bank account. If your assistant offers to enter any of those anywhere, that is the point to stop.
Are you building your own insurance assistant?
Yes, and it is not live yet, so we will not pretend otherwise. What runs today is the published submission pathway, an after-hours phone agent that takes service requests outside office hours, and document reading that pulls the coverage detail out of policy paperwork. The client assistant we are building is aimed at the part everybody hates, which is filling in the application, with a licensed agent checking the result. When it is running it will be on this page.
Commercial insurance is 96% of what we do — it is not a department here, it is the whole business. Not ready to talk? The guides answer the questions this page raises in more depth. Already insured with us and need a certificate or a policy change? Ask the service team rather than starting a quote — it is faster and it goes to the people whose job it is. We also write home and auto, which is usually cheaper alongside the business policy than apart from it.
Handed a lease, a vendor packet or a client contract with insurance requirements? Paste it into the COI Requirements Decoder to see what each one means for your business, or read what the requirements mean.