One API · every kind of insurance work · agent-first
Agents can't sell or settle insurance. They can call it.
api.insure is the endpoint any agent hits the moment work turns insurable: the F&I menu in an auto checkout, the flood binder at a closing, the wind claim after the storm. Everything the state leaves open runs agent-native, and the acts it reserves land on licensed authority we hold: our TPA for the claim decision, our appointed agency for the bind. Point your agent at the API, or build it into your product. One key either way.
Claims is the first live surface; bind and quote are roadmap, typed on the same substrate. Flat, posted pricing, fixed at post time. No decision, no charge.
POST /claims { "policy": "HO3-4482-TX", "loss": { "date": "2026-07-14", "peril": "wind_hail", "state": "TX" }, "run": ["intake", "assemble", "evaluate", "decide"] }
{
"claim": "clm_8f3ka92",
"status": "PENDING_ADJUSTER",
"open_work": {
"fnol": "complete",
"file": "assembled",
"coverage": "analyzed",
"estimate": "checked"
},
"reserved_act": {
"verb": "adjust",
"license": "TX all-lines adjuster",
"verified": "at_call_time",
"authority": "delegated_by_carrier",
"fee": { "shape": "flat", "fixed": "at_post" }
},
"webhook": "decision.issued"
}
The regulated surface has never had an interface.
The state reserves the decision, the negotiation, and the bind. It does not reserve the intake, the file assembly, the coverage read, or the estimate math. Yet every path to the reserved acts today runs through one of two dead ends.
The legacy TPA contract
Per-file pricing negotiated annually at procurement. Weeks of latency. A portal instead of an API, an SFTP drop instead of a webhook. Your claim leaves your product and enters a queue nobody can see into.
The unlicensed-adjusting tripwire
Build the decision yourself and your agent is adjusting claims without a license. One blown acknowledgment deadline, one agent that "just denies it", and it's not a bug ticket. It's a Department of Insurance complaint with your product's name in it.
POST the file. Get a typed pending state. Get the decision.
Run the open work
Your agent runs FNOL intake, document assembly, coverage analysis, estimate review. Everything the state leaves open stays in your loop, at API speed.
"open_work": "yours" // intake, assemble, evaluate
Hit the reserved act, and keep going
When a call reaches an act the state reserves, you don't stop. The call returns a typed pending state while a licensed adjuster on the network, working under delegated authority the carrier granted our TPA, reviews the prepared file and decides in their own licensed judgment: approve, deny with reasons, or send back for more.
"status": "PENDING_ADJUSTER" "license": "verified at call time"
Receive the decision
The decision, the adjuster's verifiable Attestation, and the payment record come back on a webhook. Your product moves on. You were never the adjuster, and never needed to be.
{ "event": "decision.issued",
"decision": "approved",
"attestation": "att_71b…",
"payment": "pay_20c…",
"meter": "released" }Two licensed professions. One substrate. The line is typed.
A per-state, platform-counsel-owned catalog of reserved verbs draws the boundary where the state draws it, including utterance-class acts: negotiating a settlement is speech, gated at utterance time, not just at signature time. The API's own type system stops your agent at the line, in every state.
| Profession | Reserved verbs | Open to your agent | Status |
|---|---|---|---|
| Adjuster per state × line of authority, Designated Home State handled |
investigate · adjust · settle | intake · assemble · analyze · estimate · monitor | v1 surface |
| Producer backed by our owned, appointed agency |
sell · solicit · negotiate · bind | quote math · document prep · renewal watch | Roadmap |
We hold the licenses, the appointments, the claims-handling agreements, and the E&O, so you never touch the regulated surface. You integrate an API; you never carry a license or answer to a market-conduct examiner.
Every line of business. One substrate.
api.insure is not a claims product. It is the insurance layer of the agent-first stack: every line of business, both licensed professions, two license grains (the corporate licenses our entities hold, the personal licenses the network holds), one typed API. Agent-first verticals already route their insurance work here.
| Caller | What their agents call | Motion | Status |
|---|---|---|---|
| auto.dev | F&I products at the point of sale · liability / collision / comprehensive · total-loss and glass claims | B2A2D | Claims v1 · Roadmap bind |
| Real-estate stack | home and flood at closing · escrow-tracked renewals · loss draft claims | B2A2D | Claims v1 · Roadmap bind |
| Insurtechs · MGAs · claims-tech | the claims loop end to end: FNOL to decision to payment record | B2A · B2A2D | v1 surface |
| Any agent, directly | coverage reads · license lookups · deadline rules · then the reserved acts, routed | B2A | v1 surface |
Every statutory clock has a named owner.
State unfair-claims-practices law sets hard timers on every claim: acknowledge, decide, pay. On api.insure they are deterministic ladder machinery, closed only by evidence, escalated loudly, never silent dead air.
Receipt of the claim acknowledged to the policyholder, on the record, inside the state's window.
Accept or deny after the file completes, by a licensed adjuster, with reasons on a denial.
Payment issued after acceptance, and the payment record lands on your webhook.
Worked example: the Texas Prompt Payment of Claims Act. Timers vary by state; the full per-state table ships with the catalog.
The agreement, plainly.
No decision, no charge
Demand-side billing releases only on the deterministic fact: the issued decision, the payment record. A denial is a decision; the meter treats it as one.
Flat, posted pricing
Every reserved act is a flat fee fixed at post time. Nothing per-severity, nothing percentage-of-claim, no meters you can't cap. Your spend ceiling is hard and you set it.
The regulated surface is ours to carry
The TPA licensing, the claims-handling agreements, the producer agency, the E&O program: held and maintained by the platform's own licensed entities, so you never hold a license or file for one.
A live license at every reserved act
Verified at call time against the state registry, per state and line of authority. Lapsed or suspended means BLOCKED: typed, never silent, never degraded.
Licensed judgment, structurally protected
The adjuster who decides can send back or refuse; no platform mechanism can commit past their refusal, and their flat fee can't be leaned on by the outcome. A decision your regulator can trust is a decision your product can ship.
You never cross the line
The type system stops your agent at the reserved boundary, for both professions, in every state. Building on api.insure is how you avoid unlicensed adjusting, not how you risk it.
The parties, named honestly.
In claims, who is owed what is the first thing a compliance team checks. The API types the parties distinctly instead of blurring them into a generic "client". Your compliance lead will notice. That's the point.
- Carrier
- The principal. Delegated authority flows from its claims-handling agreement with our TPA.
- Policyholder
- Owed good-faith handling and the statutory clocks, on the record.
- Claimant
- Adverse in third-party claims, and typed that way.
Claims is first. You can be too.
Request a key and you're emailed the moment the surface is callable. Early integrators shape the catalog and set their embed terms; late ones integrate a standard someone else shaped.
The honest fine print. api.insure is in early access: there is no live service yet, and the artifacts on this page are labeled specimens. Delegated authority requires a claims-handling agreement between your carrier or MGA and our TPA; we stand that up with you during onboarding. Bind and quote are producer-reserved acts backed by our owned, appointed agency, and they are roadmap. Carrier-side claims only: api.insure is not a public adjuster and does not represent policyholders.