A customer who has connected your app asks ChatGPT or Claude what cover would cost. Your product answers in that same conversation: a real quote with the agreed disclosures, and a way to buy the policy. Airclerk builds and launches those apps for direct-to-consumer insurers and MGAs in New Zealand and Australia.
Illustrative example A mocked-up quote conversation, showing the shape of the response rather than a live product.
Both use the same plumbing, which is why they get confused. They serve opposite directions.
Your underwriters' Claude or Copilot reading the policy system, the claims platform, SharePoint and the shared mailbox. Connectors and MCP servers scoped to a workflow, inside your tenancy. That is part of every workflow build, described under connectors and integrations.
A member of the public, in their own ChatGPT or Claude account, asks about cover. Your app is what answers. It is a distribution channel with the same disclosure and audit obligations as your website, and it is what the rest of this page is about.
An MCP (Model Context Protocol) app exposes an insurer or MGA's products, quoting and claim service, as a callable app inside ChatGPT, Claude and other AI assistants. OpenAI ships these as ChatGPT Apps (October 2025); Anthropic ships the equivalent as MCP Apps in Claude.ai (January 2026). Both build on the Model Context Protocol, an open specification; the MCP Apps extension is what lets an app show its interface inside the assistant. The same surface can also serve insurer-to-broker workflows: replacing email as the channel through which a broker submits a quote request and an underwriter responds, without connecting to a rating engine.
Primary: direct-to-consumer in the chat, with real quotes and real claim service. Secondary: a broker submission channel that replaces email between brokers and underwriters.
Customers describe what they need in ChatGPT or Claude. Your product responds in the same conversation, bound by the same disclosure and audit obligations as your direct web channel.
Customer describes their need in ChatGPT or Claude. Your app returns a real quote with the disclosures and product summary your regulator requires, and shows the customer how to buy the policy.
Identity-verified policyholder asks for a claim update. Your app returns sanitised status, next steps and expected timeframes.
A different shape, and a different audience. Brokers raise submission requests through the same conversational surface to your underwriting team: structured fact-find capture, clarification back and forth, and the resulting indication or quote, all in one thread instead of a forty-message email chain.
Not connected to your rating engine. Pricing stays with your underwriters. The chat replaces email as the channel for the request, the back and forth and the outcome, captured, structured and audit-ready.
Which product, which systems sit behind it, who signs off disclosures. Enough to quote. The engagement then opens with the detailed design: use case, MCP surface, disclosure model and target architecture, agreed before anything is built.
The app itself, the integrations (to your quoting and policy systems for direct-to-consumer; to your submission and underwriting case management for broker use, with no rating engine required), and the conversation patterns customers or brokers actually use. Tested against your real products before launch.
Disclosure blocks, evidence capture for every quote, FSLAA / CoFI-aligned complaints routing, regulator-readable logs. Built into the app, not retrofitted.
Submission to the ChatGPT apps directory, the Claude apps surface and any other MCP-compatible assistant your customers use. Each platform reviews and approves apps on its own timetable; the written scope sets out those dependencies. Handover and post-launch support as written in the scope; ongoing operation by separate agreement.
Our strongest practice is brokers, and we have done significant work with insurers and MGAs. We know what a quote and a claim conversation actually has to do.
ChatGPT Apps (October 2025) and Claude MCP Apps (January 2026) both run on the same MCP protocol. We build MCP servers and connectors as a regular part of our practice; customer-facing apps use the same surface.
Disclosure, audit trail, identity and complaints belong in the app itself. Done at launch, not retrofitted.
FSLAA, FAP, CoFI and the FMA's conduct expectations in New Zealand, and ASIC's conduct and complaints-handling expectations in Australia, shape how an insurance app should behave inside an AI chat. We agree the disclosure and complaints requirements with your compliance team for each market before building.
A free introductory conversation about the product, the systems behind it and who signs off disclosures. If it is a fit, a written scope with a fixed fee follows.