Choose Your Integration

There are two ways to integrate. They differ on one question: do you want to show the plans yourself?

Everything else you may have heard about (co-branded checkout, pre-filled checkout, agent-operated checkout, cached search) is configuration or optimization layered on top of these two. It is not a third or fourth path. See what is not a choice below.

Who does what

flowchart TB
    classDef you fill:#8250df,color:#ffffff,stroke:#8250df
    classDef chaiz fill:#0969da,color:#ffffff,stroke:#0969da

    subgraph handoff["2. Search and Hand Off"]
        direction TB
        HA["Find customer"] ==> HB["Quote"] ==> HC["Show plans"] ==> HD["Take payment"] ==> HE["Issue contract"]
    end

    subgraph lead["1. Send a Lead"]
        direction TB
        LA["Find customer"] ==> LB["Quote"] ==> LC["Show plans"] ==> LD["Take payment"] ==> LE["Issue contract"]
    end

    class LA,HA,HC you
    class LB,LC,LD,LE,HB,HD,HE chaiz

Purple is yours. Blue is ours. Chaiz always does the quoting, takes the payment, and issues the contract. Card data never reaches you on either path, so neither puts you in PCI scope.

Pick one

flowchart TD
    Q1{"Show the plans on your own site?"}
    Q1 ==>|"Yes, I render the plan list"| HANDOFF["Search and Hand Off"]
    Q1 ==>|"No, contact the customer for me"| LEAD["Send a Lead"]

Compare

	Send a Lead	Search and Hand Off
You build	One POST	A search call and a results page that meets the UI requirements
We handle	Quoting, contacting the customer, presenting plans, checkout, payment, contract	Quoting, checkout, payment, contract
API calls	1	1
Customer data you collect	Name, email, vehicle, state, mileage	Vehicle, state, mileage (contact details optional)
Where the customer ends up	Their inbox, then Chaiz	Chaiz checkout
Time to first sale	Hours	Days
Best when	You have traffic but no quoting UI, or you sell by phone follow-up	You want the offer on your surface
Guide	Send a Lead	Search and Hand Off

Not sure? Start with Search and Hand Off. It is what most partners run, and it needs one endpoint.

You can combine them

These are not exclusive at the account level, only per transaction. A common pairing is Search and Hand Off on your site for customers ready to buy, plus Send a Lead for customers who abandon, so we follow up by email instead of losing them.

What is not a choice

Several things that look like separate integrations are actually settings on your account. You do not build differently for them, and you cannot switch them on yourself. Ask your account manager or dev-support@chaiz.com.

Capability	What it does	How you get it
Co-branded checkout	Your logo and brand color on the Chaiz checkout	Account configuration
Skip the plan detail page	Handoff URLs land the customer straight on checkout	Account configuration
Pre-filled checkout	Customer's details already filled in, so they only enter payment	Send `userDetails` with your search. See Search and Hand Off
Agent-operated checkout	Extra confirmations for a human agent buying on a customer's behalf	Account configuration
Restricted catalog	Only certain providers, durations, or payment terms are offered	Account configuration
Cached and async search	Instant results for vehicles you know about in advance	Account configuration, opt-in. See Plan Search Reference

Because these are server-side, your code does not branch on them. You call the same endpoints and read the same fields; the URLs we return and the pages they open already reflect your setup.

Not writing code at all?

If you want to search and compare plans from ChatGPT, Claude, Cursor, or another AI assistant rather than building an integration, use the Chaiz MCP Server. No API key required, and no code.

Next steps

Get a key and run a search: Quickstart.
Open the guide for the path you picked from the table above.
Skim Plan Search Reference; both paths use the same vehicle and quoting rules.
When it works on UAT, follow Going Live.

Authentication

Going Live