AIPAgentic Insurance Protocol

Draft 0.1

An open standard to sell insurance through AI agents.

People now ask AI agents to find, compare and buy insurance. The agents visit websites that were made for people, and they often bring back a bare price without the cover or the conditions behind it. AIP gives insurers one open way to give agents the full offer, and to keep each sale compliant.

Read the specSee a sale step by stepGitHub

Personal AI agents

  • Meta Muse
  • OpenAI Dots
  • Claude Duet
  • Instinct
  • GrokBot
  • Other AI agentsAssistants, browsers, bots

Your website

What a regulated sale needs

  • Which agent, acting for whom?PAP
  • Documents before the priceAIP
  • Demands and needs on recordAIP
  • Answers kept as a declarationAIP

Made for people: pages, forms and PDFs

Two steps, one after the other

  1. 1. IdentificationWho is this agent, and who does it act for?PAP
  2. 2. CommunicationHow do you give it the full offer?AIPonMCP
  1. 1Personal agents come to your website.
  2. 2They can't use its forms. A regulated sale needs more than a form can give.
  3. 3PAP solves identity: who the agent is, and who it acts for.
  4. 4MCP with AIP solves the rest: the documents, the needs, the declaration and the full offer.

Agents have started to buy

Personal agents now search, compare and buy for people. Their traffic grows faster than human traffic, and each company decides alone how to answer it.

7,851%

Growth in traffic from AI agents and agentic browsers in 2025, year on year.

Traffic benchmark report, March 2026

17.7 billion

AI agent requests in the second quarter of 2026, 45% more than in the first.

Bot protection report, July 2026

42%

Better conversion for visits from AI than for other visits on US retail sites in March 2026. A year earlier, they converted 38% worse.

Retail analytics data, April 2026
More context and news

Two steps for every insurer that sells to agents

An insurer wants agents to find and price its offer correctly. It must keep control of that offer, and a sale through an agent must meet the same rules as a sale on its own site. An agent goes through two steps, one after the other. First the insurer identifies it, then it gives the agent the full offer.

1. Identification

Who is this agent, and what does it want?

On your site, a customer signs in and you know who they are. An agent needs the same: proof of who it is, who it acts for and what it may do. PAP defines this on top of OAuth, and AIP uses PAP as it is.

PAP

2. Communication

How do you give the agent the full offer?

An agent calls tools, the way a program calls an API. MCP carries those calls, but it does not say which tools an insurer needs. Each insurer picks its own, and the nine quote tools we studied have nine names and nine sets of inputs. AIP defines the tools and what each one returns.

AIPonMCP

The tools AIP defines

AIP tells an insurer which tools to put in its MCP server, and what each one returns. Draft 0.1 covers acquisition, from the first question to the signed contract. Changes, renewals, cancellations and claims come in a later draft.

  1. Who sellsget_distributorThe legal name, and each licence with its regulator and public register.
  2. What is for salelist_productsThe products by line and country, what they cover, and how the customer can subscribe.
  3. What to read firstget_documentsThe IPID and the conditions, each with a version and the hash of the file.
  4. What to askget_question_setThe questions as JSON Schema, with a common core per product line. Sensitive fields stay on your own page.
  5. The pricequoteOffers with the premium, the cover, the limits and the excess. When there is no offer, a reason.
  6. The contractsubmit_applicationconcludeA PAP operation that the customer approves. Its terms hold the parties, the declaration, the demands and needs and the documents delivered, and you keep the evidence record.

The full offer

Each offer carries its cover, limits, excess and documents. An agent compares all of it, and the customer sees what the price buys.

Control stays with you

You choose your level: inform, quote or subscribe. Sensitive data and the last step can stay on your own page, and nothing commits until the customer approves.

Compliance in every step

Each step leaves the evidence that a sale on your own site leaves: the licence, the documents delivered, the demands and needs and the declaration.

Draft 0.1 comes from the quote tools of nine insurance MCP servers in production, a commercial lines broker (US) that exposes only a conversation, and the actions that a listed insurer opened to personal agents in October 2026.

How it works

One pet insurance sale, from discovery to the evidence record. The AIP data on screen comes from the worked example in the spec.

Transcript
  1. Camille asks an AI agent to insure Miso, a cat. Example Pets sells pet insurance.
  2. The agent reads Example Pets' poppy.json. It lists the MCP server, the PAP operations endpoint and the AIP level.
  3. The agent starts a PAP Session, signed out. Every call after this one carries its Session Token.
  4. Each AIP step is an MCP tool. get_distributor says who sells, and under which licence.
  5. The documents that the law requires come with a version and a hash. The agent gives them to Camille before any commitment.
  6. The questions come as a JSON Schema. The microchip number is for Example Pets' own page, so it never passes through the agent.
  7. The agent quotes with the five answers it has. The server lists the four that are missing.
  8. One more call with all ten answers. The offers come back priced, with the hash of the answers.
  9. Applying commits nothing. The tool returns a PAP operation, and AIP defines its terms: parties, declaration, needs and documents.
  10. The agent shows Camille the summary and the key terms in its own interface. The approval covers this exact revision.
  11. The agent confirms revision 1 at the PAP operations endpoint, never through an AIP tool.
  12. Example Pets keeps an evidence record: the documents delivered, the declaration, the needs, the consent, and the hash of the approved terms.
  13. Camille finishes on Example Pets' site. Miso's microchip number never passes through the agent.
  14. MCP carries the calls. PAP carries the Session and the approval. AIP defines the insurance terms on top of both.
  15. Draft 0.1 covers the sale. Changes, renewals, cancellations and claims come in a later draft.

Three levels of conformance

A distributor declares a level and implements every tool up to it. Level 1 is enough to be found, and level 3 takes the customer to a signed contract.

Level 1

Inform

  • get_distributor
  • list_products
  • get_documents

Session: None

Level 2

Quote

  • get_question_set
  • quote
  • validate_answers

Session: None; None, or signed out

Level 3

Subscribe

  • submit_application
  • conclude

Session: None, or signed out

Level 3 needs only one of submit_application and conclude. Every tool that commits returns a PAP operation, and the customer approves it there.

What a server declares

A server declares its level, its product lines and its countries in MCP server/discover, and under the same key in PAP poppy.json. This declaration comes from the worked example.

{
  "capabilities": {
    "extensions": {
      "org.agenticinsuranceprotocol/aip": {
        "version": "0.1",
        "conformance_level": 3,
        "interfaces": ["tools"],
        "lines": ["pet"],
        "countries": ["FR"],
        "can_conclude": false
      }
    }
  }
}

Shape the draft

The draft changes with what implementers learn. Each link opens a GitHub issue form.

To report a weakness that could harm a live implementation, use private vulnerability reporting.