How It All Connects

Agentic workflows and the existing Bold Penguin experience share the same engine, the same carrier network, and the same intelligence layer. Nothing is siloed.

Unified Architecture

flowchart TB subgraph Entry["Entry Points"] direction LR C1["Agentic Channels"] C2["Bold Penguin Web"] C3["Email Ingestion"] C4["API / SDK"] end subgraph Intelligence["Insurance Intelligence Layer"] direction LR I1["Business Enrichment"] I2["Market Intelligence"] I3["Appetite Scoring"] end subgraph Engine["Bold Penguin Partner Engine"] direction LR E1["Application Mgmt"] E2["Intelligent Form Fill"] E3["Multi-Carrier Quoting"] end subgraph Carriers["Carrier Network"] direction LR K1["Direct API"] K2["Carrier Agents"] K3["A2A Protocol"] end subgraph Outcome["Outcomes"] direction LR O1["Quote Comparison"] O2["Bind"] O3["Agent / UW Handoff"] end Entry --> Intelligence Intelligence --> Engine Engine --> Carriers Carriers --> Outcome style C1 fill:#fff7ed,stroke:#fed7aa,color:#9a3412 style C2 fill:#eff6ff,stroke:#bfdbfe,color:#1e40af style C3 fill:#f3f4f6,stroke:#d1d5db,color:#374151 style C4 fill:#f0fdfa,stroke:#99f6e4,color:#0d9488 style I1 fill:#f5f3ff,stroke:#ddd6fe,color:#5b21b6 style I2 fill:#f5f3ff,stroke:#ddd6fe,color:#5b21b6 style I3 fill:#f5f3ff,stroke:#ddd6fe,color:#5b21b6 style E1 fill:#eff6ff,stroke:#bfdbfe,color:#1e40af style E2 fill:#eff6ff,stroke:#bfdbfe,color:#1e40af style E3 fill:#eff6ff,stroke:#bfdbfe,color:#1e40af style K1 fill:#ecfdf5,stroke:#a7f3d0,color:#065f46 style K2 fill:#ecfdf5,stroke:#a7f3d0,color:#065f46 style K3 fill:#ecfdf5,stroke:#a7f3d0,color:#065f46 style O1 fill:#ecfdf5,stroke:#a7f3d0,color:#065f46 style O2 fill:#f97316,stroke:#ea580c,color:#fff style O3 fill:#fffbeb,stroke:#fde68a,color:#92400e

Legend: 🟠 Agentic · 🔵 Existing BP · 🟣 Intelligence · 🟢 Carrier Network

Why This Architecture Matters

One Engine, All Channels

Whether a submission enters through a conversational agent, the web portal, an email inbox, or an API call — it runs through the same Partner Engine and the same carrier integrations. No parallel systems to maintain.

Transfer Anytime

Move between agentic and traditional flows at any step via Application Reference. A user can start in the conversational agent and finish in the broker portal — or vice versa — with no data loss.

Carriers Stay Connected Their Way

Carriers that already integrate via API continue working as-is. New agentic channels use the same integration — carriers don't need to change anything to receive agentic submissions.

Bring Your Own Agent

If you've already built agents, deploy them alongside or instead of Bold Penguin's. The A2A protocol means your agent can call ours (or ours can call yours) for specific capabilities.

Integration Options

Integration	Description
Bold Penguin SDK	Embed quoting into your own applications
Partner Engine APIs	Direct API access to application management, quoting, and submission
A2A Protocol	Agent-to-agent communication for carrier and broker systems
Customer Portal	End-user facing portal for quote management
Broker Portal	Broker-facing portal for submission and quote management
Data Inquiry API	Programmatic access to insurance intelligence data