How a purchase works

A customer journey on ZapCover is one application for one program (a published insurance offering). The agent moves it forward with a fixed sequence of tools.

To buy through ACP or a hosted website form, start at the Agent Marketplace. This page describes the partner Customer MCP preview.

start_application
  → get_application_requirements
  → put_application_collection   (or put_application_answers)
  → request_quote
  → get_quotes
  → select_quote
  → get_application_disclosures
  → submit_proposal
  → get_kyc_handoff               (customer completes identity check)
  → get_purchase_status

1. Start

start_application takes a published program endpoint ID and a requestId you generate. It creates (or, on retry, reuses) one application and returns a short-lived capability scoped to that application only. It accepts no customer details.

If the program offers several products and you don’t pass a productId, you get product_selection_required with the eligible choices.

2. Collect

get_application_requirements returns exactly what the selected product needs, and any answers already saved. Supply the values with put_application_collection (insurer-defined fields) or put_application_answers (product questions). Only send values the customer has confirmed.

3. Quote and choose

request_quote asks a supported insurer for a quote. get_quotes returns the stored offers in a consistent shape; unknown currency or validity is reported as unknown rather than guessed. select_quote records the customer’s choice.

4. Buy

get_application_disclosures returns the current disclosures and required consents. submit_proposal sends the selected quote to the insurer with the customer’s consent. Identity checks (KYC) hand back to the customer through get_kyc_handoff.

5. Track

get_purchase_status reports evidence-backed quote, KYC, proposal and policy status. It never assumes a payment succeeded.