Patterns

Common integration patterns

Most integrations fall into five shapes: a quote widget, an embedded application, a comparison listing, an AI assistant and a back-office sync. Each maps cleanly to the public or partner ring.

2 min read

5 patternsCover most builds

PublicWidgets + agents

PartnerApplications + sync

Public-ring patterns

A quote widget renders a live figure from the quote endpoint; a comparison listing reads products and pricing; an AI assistant chains the MCP tools. None needs a token — they read published figures and hand qualified users to apply.

Partner-ring patterns

An embedded application takes the application in your own UI and submits it to POST /applications, reads the decision and provisions a payment; a back-office sync mirrors application and payment state into your systems via webhooks. Both need OAuth and a project.

Picking your pattern

Start from the outcome: showing figures is public; taking an application or moving money is partner. Many products combine a public quote front-end with a partner application back-end — the public-vs-partner guide maps the boundary.

Frequently asked questions

Which pattern is cheapest to build?

A quote widget or comparison listing — both are unauthenticated public reads with no account required. The embedded application and back-office sync need partner access and more integration work.

Can one integration span both rings?

Yes, and most do. A public quote widget qualifies and prices a prospect; a partner application flow then takes them through submission, decision and payment. The rings are designed to compose.