01 · PolicyQuotes
AI proposals from carrier quotes
Send the carrier quote PDFs. Get back one clean, branded proposal with options side by side, ready for the insured.
POST /v1/proposalsDoor 3 · Build it into our system · API only
For agency software, MGA platforms and raters. Your agents quote, sign, collect and finance without leaving your system. No PolicyOS screens, no second login. Your UI, our rails.
FREE TO INTEGRATE · SANDBOX KEYS FOR EARLY PARTNERS · WORKS NEXT TO WHAT YOU ALREADY RUN
Agency software vendors
Put a proposal, a signature and a checkout one click from the policy screen your agents already live in.
MGA platforms
Your retail agents sign and pay in your portal. Premium finance sits behind the same button.
Raters
The quote you just rated becomes a proposal the insured can read, sign and pay. Same session.
Layer 1 · The tool · Free to integrate
These are the PolicyPay rails, packaged as part of PolicyOS. Call them from your product and your agents get the whole path from carrier quote to money in the bank. If you never read past this section, this is still the whole win.
01 · PolicyQuotes
Send the carrier quote PDFs. Get back one clean, branded proposal with options side by side, ready for the insured.
POST /v1/proposals02 · PolicySign
Apps, disclosures and finance agreements, signed in a hosted flow or embedded in your page. Signed copies come back to you.
POST /v1/signatures03 · PolicyPay
Checkout sessions by link, email or SMS. Card and ACH, pay in full, with reminders. Money moves after merchant approval.
POST /v1/checkout/sessions04 · PolicyPay
Offer a finance option in the same checkout. Down payment, installments and the agreement, handled on the rails.
POST /v1/finance/quotes# Example request — illustrative, final API in docs POST /v1/checkout/sessions Authorization: Bearer sk_sandbox_example Content-Type: application/json { "agency_ref": "example-insurance-group", "producer": { "name": "Alex Rivera", "npn": "0000000" }, "insured": { "name": "Example Marine LLC", "email": "ops@example.com" }, "policy": { "carrier": "Example Mutual", "line": "commercial_package", "premium_usd": 18450.00, "effective": "2026-10-01" }, "options": { "pay_in_full": true, "premium_finance": { "down_payment_pct": 25, "installments": 9 } }, "require_signature": true, "return_url": "https://your-app.example/policies/88213" } # 201 Created { "id": "cs_demo_7Qm2", "url": "https://pay.example/cs_demo_7Qm2", "status": "open" }
# Example request — illustrative, final API in docs POST /v1/proposals Authorization: Bearer sk_sandbox_example Content-Type: multipart/form-data agency_ref = example-insurance-group insured_name = Example Marine LLC quotes[] = @carrier-a-quote.pdf quotes[] = @carrier-b-quote.pdf branding = agency_default # 202 Accepted — AI reads the quotes, then calls you back { "id": "prop_demo_4Lk9", "status": "reading_quotes", "options_found": 2, "webhook": "proposal.ready" }
# Example event — illustrative, final API in docs POST https://your-app.example/hooks/policyos PolicyOS-Signature: t=1790000000,v1=demo { "type": "checkout.financed", "created": "2026-10-01T15:04:22Z", "data": { "session": "cs_demo_7Qm2", "agency_ref": "example-insurance-group", "down_payment_usd": 4612.50, "financed_usd": 13837.50, "installments": 9, "agreement_signed": true } }
Layer 2 · What your agents' data became
You didn't write a line of extra code for this. It came along with the quotes, signatures and payments.
Alex Rivera · Example Insurance Group
Earned this month, shown in USD
GET /v1/agents/{id}/earnings · illustrative · earn rates are being set
Layer 3 · Add Jefferson later
Those proposals didn't build themselves. Jefferson read every carrier quote. Once you're live, plug him into your product through the JCI MCP and he can do more for your agents: revive dead files, work renewals, read the inbox. He does not require a declaration of independence from your codebase. He just needs a key.
Set up in JCI
The JCI MCP is its own setup, with its own keys and permissions. Your PolicyOS integration doesn't change.
Your screens
A button on the policy screen, a task in your queue, a chat panel. You decide what he can see and do.
Metered
Every call is counted by model. Light models cost little. Heavier models cost a multiple. You see it per call.
"I would rather be exposed to the inconveniences attending too much liberty than those attending too small a degree of it. The same goes for API scopes. Give me the narrow ones."JEFFERSON, MOSTLY
Layer 4 · The bigger room
Every endpoint you called is an element in one periodic system. Your agents' agencies get a virtual Cabinet from day one, and a physical one on their own hardware if they ever want it. The network, the marketplace and discounted E&O + Cyber come with the room. Your platform is the door they walked through.
The network
Your platform is listed as a way in. Agencies on the network can find you.
The marketplace
Partner tools sit next to ours, on the same rails and the same wallet.
E&O + Cyber
For agencies on the network, including the ones you brought.
How it works
Questions from tech teams
No. It's API only. Your agents stay in your product and never see a PolicyOS screen. Insureds see a hosted checkout or signing page, or an embedded one inside yours.
The agency owns its book and the insured owns their InsureBio profile. You keep everything in your own system as you do today. On our side: you own it and control who sees it. We hold the keys for you, and every access shows up in your log.
Free to integrate. Pricing is on volume through the rails, payments and premium finance, and is being set. Join the waitlist and we'll walk through it for your platform.
Yes. It works next to what you already run. Start with one agency, one checkout, and grow when you're ready.
Build it in
Your product, your agents, your screens. Our rails underneath. Join the waitlist for API access and tell us a little about your platform.