Built for independent agencies · First tenant: 360 Insurance Services
Agents that keep your book in force.
Daemond Cover runs ambient agents across carrier, lender and payment portals. They wake on an email, a deadline or a portal change, do the legwork, and stop for a licensed broker before anything consequential happens.
Notice received
NOIC from notices@daemond.co
Lender account checked
Policy, borrower, amount and cure date match
Carrier billing checked
Financed by Ironbridge, loan number matches
Broker sign-off
Pay $1,560.00 to Ironbridge by Nov 16
Payment, lender and carrier readback
Runs after sign-off
Amount to approve
$1,560.00
Installment $1,535.00 + late fee $25.00
Illustration of the console. Sandbox data.
From an unknown portal to a safe action
Most carrier and lender portals have no public API. The agents learn them the way a careful person would, then write down what they learned.
01
Explore
A browser agent signs in to a carrier or lender portal with credentials you authorize, walks every page in scope, and records the first response to each call. It never submits a form while exploring.
02
Learn
Each record is read twice. Fields that differ between two reads of the same record are noise; fields tied to the URL are identity; status, amounts and dates are change.
03
Codify
Every portal gets a generated API doc and open TypeScript types, versioned. Adapters expose six actions: start quote, apply answers, read state, take action, fetch documents, cancel.
04
Mirror
Partner records land in a raw mirror with full history and first seen, last changed and last seen times. Reconcilers flag where your records and the partner's disagree.
05
Act
Agents check the live page before each write, read every write back, and pause with the fix spelled out when something is missing. A person resumes it in one step.
Premium rescue, start to finish
When a financed premium goes unpaid, the lender sends a Notice of Intent to Cancel and the clock starts. The rescue agent works across the lender portal, the carrier portal and the payment tool, and hands back the moment anything disagrees.
- 1Lender emails a Notice of Intent to Cancel to notices@
- 2Agent reads the lender account and the carrier's billing
- 3Any mismatch: stop and hand back to a person
- 4Licensed broker signs off on the exact amount
- 5Payment sent once, with an idempotency key
- 6Lender reinstatement and carrier status read back
Agents propose. Code and people decide.
Sign-off before money moves
Payments, binds and submissions wait for a licensed broker. The approval covers an exact payload hash, so a changed amount needs a new sign-off.
Readback, not receipts
A write counts only when the partner's own page shows it. A timeout is treated as unknown and resolved by reading, never by resubmitting.
Pause with the fix
Missing credentials, an expired session or an unreadable notice pause the work with what is missing, why, and the exact value needed to resume.
Traced end to end
Every model call, tool call, policy decision and portal request is a span you can open. Personal data is scrubbed before it is stored.
Integrations, stated plainly
Live means connected to a real service today. Sandbox means our own test portals, which exercise the same code paths without touching real money or real policies.
| Area | Service | Status |
|---|---|---|
| Inbound email | Cloudflare Email Routing to notices@ and intake@ | Live |
| Documents | PDF, text and XLSX parsing (census, prospect, rent roll); R2 storage | Live |
| Inference | Konoha; Cloudflare Workers AI as a labelled fallback | Live (fallback) |
| Database and runtime | Neon Postgres; Cloudflare Workers with a minute-by-minute event loop | Live |
| Carrier portals | Northwind Mutual sandbox (SPA with JSON and GraphQL) | Sandbox |
| Premium finance | Ironbridge sandbox (server-rendered forms) | Sandbox |
| Payments | PayBridge sandbox (JSON API with idempotency keys) | Sandbox |
| SMS and Slack | Queued in the console until a provider is connected | Not connected |