On CarrierBridge, an agent enters one address with Google Places, the API pre-fills dwelling facts via BrightData/Zillow (Realtor.com fallback), the agent confirms gaps and selects carriers, then FastAPI fans out Playwright sessions across the selected portals while Server-Sent Events stream per-carrier progress, premiums, and quote PDFs.
The use case
An agency producer needs HO3 quotes for a Florida dwelling. Without automation, that means logging into each carrier portal, retyping the same address and house facts, waiting, downloading PDFs, and repeating — five to ten times.
CarrierBridge collapses that into one continuous path: address → property prefill → confirm → parallel quotes → live progress.
Step 1 — One address
On the home screen the agent starts with Google Places autocomplete. The address becomes structured input for property lookup instead of a free-text guessing game inside every portal.
Step 2 — Prefill the dwelling
The property-lookup API hits BrightData against a Zillow dataset (with Realtor.com as fallback) and returns attributes the confirm form cares about — square footage, year built, beds, price signals, and related fields.
The point is not “AI guessed the house.” The point is removing duplicate typing before the expensive portal work starts.
Step 3 — Confirm what portals still need
Carriers still care about construction type, foundation, roof, effective date, and customer details. The confirm screen is where the agent owns those gaps, multi-selects carriers, and sets the policy effective date (defaulting to a sensible offset from today).
Nothing submits to a portal until a human has reviewed that packet.
Step 4 — Parallel Playwright, live SSE
The quote stream starts the orchestrator. Playwright Chromium sessions fan out across the selected providers — Universal (Atlas Bridge), Slide, Florida Peninsula (Windward), Southern Oak, Security First, Home Owners of America, American Integrity, Heritage, AAA Carolinas, Orion180 — with a browser pool so concurrency stays bounded.
The quotes UI listens over SSE:
- Per-carrier step and progress
- Premiums as each portal finishes
- Quote PDF links when documents land
- Ability to cancel or reattach if the tab reconnects
One slow portal does not freeze the others. Selective retry re-runs failures without rebuilding the whole property packet.
Why this use case matters
This is the difference between “we scraped a form” and ops automation:
- Enrichment happens before login storms
- Humans confirm carrier-critical fields once
- Parallelism is pool-limited, not “open infinite browsers”
- Progress is observable (SSE), not a spinner
- Production egress sits on EC2 + Cloudflare Tunnel + OpenVPN so portals accept the traffic
For the full product narrative (teams, history, Heritage OTP, deployment), see the CarrierBridge case study.
Related work
Common questions
What is the CarrierBridge address-to-quote use case?
It is the core agent workflow: enter an address, auto-fill property details, confirm the application facts, multi-select carriers, and receive parallel HO3 quotes with live SSE progress.
Where does the property data come from?
Google Places structures the address. BrightData runs a Zillow dataset scrape for dwelling attributes, with Realtor.com as a fallback when Zillow data is thin or unavailable. Agents still confirm construction, foundation, roof, and similar fields portals require.
How many carriers run at once?
Agents multi-select from about ten active scrapers (Universal/Atlas, Slide, Florida Peninsula/Windward, Southern Oak, Security First, Home Owners of America, American Integrity, Heritage, AAA Carolinas, Orion180). A browser pool caps concurrency so shared agency logins stay stable.
What does the agent see while quotes run?
A quotes screen fed by Server-Sent Events: each carrier’s step and percent complete, then premium and PDF link when that portal finishes — without waiting for the slowest carrier to unlock the others.
What happens if one carrier fails?
The run continues for other carriers. Agents can selectively retry failed portals on the same run instead of re-entering the property and restarting everything.
Who built this workflow?
Haris Ullah Khan (https://harisullahkhan.me) built CarrierBridge for Metropolitan Insurance. Full product write-up: https://harisullahkhan.me/blog/metropolitan-insurance-quote-automation-platform.