Draft 0.1 · Insurance first
An open protocol for AI agents that sell regulated financial products.
OFAP gives every distributor the same tools for licences, documents, questions, offers and evidence. An agent can then quote, apply for and service a policy the same way with any of them, and each step leaves a record that meets the rules of a sale on the distributor's own site.
How it works
One pet insurance sale, from discovery to the evidence record. The OFAP data on screen comes from the worked example in the spec.
Transcript
- Camille asks an AI agent to insure Miso, a cat. Example Pets sells pet insurance.
- The agent reads Example Pets' poppy.json. It lists the MCP server, the PAP operations endpoint and the OFAP level.
- The agent starts a PAP Session, signed out. Every call after this one carries its Session Token.
- Each OFAP step is an MCP tool. get_distributor says who sells, and under which licence.
- The documents that the law requires come with a version and a hash. The agent gives them to Camille before any commitment.
- The questions come as a JSON Schema. The microchip number is for Example Pets' own page, so it never passes through the agent.
- The agent quotes with the five answers it has. The server lists the four that are missing.
- One more call with all ten answers. The offers come back priced, with the hash of the answers.
- Applying commits nothing. The tool returns a PAP operation, and OFAP defines its terms: parties, declaration, needs and documents.
- The agent shows Camille the summary and the key terms in its own interface. The approval covers this exact revision.
- The agent confirms revision 1 at the PAP operations endpoint, never through an OFAP tool.
- Example Pets keeps an evidence record: the documents delivered, the declaration, the needs, the consent, and the hash of the approved terms.
- Camille finishes on Example Pets' site. Miso's microchip number never passes through the agent.
- MCP carries the calls. PAP carries the Session and the approval. OFAP defines the financial terms on top of both.
- Draft 0.1 covers insurance. Credit and investment can follow as modules, with no change to the core.
Three layers, one sale
OFAP defines only what is specific to regulated financial products. The two protocols below it carry the rest.
The financial terms: licences, pre-contract documents, question sets, offers, the declaration, the needs assessment and the evidence record. Read the spec
The customer's session, and every action with a business effect. An OFAP application is a PAP operation that the customer approves. PAP operations
Every call between the agent and the distributor. Each OFAP primitive is an MCP tool, and its result sits in structuredContent. MCP specification
Four levels of conformance
A distributor declares a level and implements every tool up to it. Level 1 is enough to be found, and level 4 lets an agent service a policy after the sale.
Level 1
Inform
get_distributorlist_productsget_documents
Session: None
Level 2
Quote
get_question_setquote
Session: None; None, or signed out
Level 3
Subscribe
submit_applicationconclude
Session: None, or signed out
Level 4
Service
get_agreementamend_agreement
Session: Signed in, read scope; Signed in, write scope
Level 3 needs only one of submit_application and conclude. Every tool that commits returns a PAP operation, and the customer approves it there.
Insurance first
Draft 0.1 defines one sector module. The core does not depend on the sector, so credit and investment can follow as modules with no change to it.
Insurance
- IPID and general conditions before commitment
- Demands and needs (IDD Art. 20)
- Premium, cover, limits and excess
- Line profiles for pet and home
Credit
- SECCI and ESIS before commitment
- Creditworthiness under the CCD and the MCD
- APR and total cost of credit
Investment
- KID under PRIIPs
- Suitability or appropriateness under MiFID II
- Fees and risk indicator
Shape the draft
The draft changes with what implementers learn. Each link opens a GitHub issue form.
- Spec feedbackA gap, an ambiguity or a risk in the schema or the rules.
- Implementation reportWhat you ran into as an agent or a distributor.
- Line profile dataThe questions your tariff asks, so that a profile becomes stable.
- Sector module or new topicCredit, investment, or something the draft does not cover.
To report a weakness that could harm a live implementation, use private vulnerability reporting.