Company profile · 3 min read
Hedge is a specialty wholesale brokerage for hard commercial risks
Hedge helps retail insurance agents submit, place and bind difficult commercial risks with named broker support and API access.
Cofounder of Lazyweb (a16z Speedrun). Previously grew subscriptions and built native ads at Duolingo. Writes First1000 (90,000+ subscribers).
Published · Updated
Hedge is a specialty wholesale insurance brokerage for hard-to-place commercial risks. The current product is more concrete than the older “AI-native insurance company” label: named brokers, a shared file, specialty-market access and an API for retail brokers.
What it does
Hedge’s current homepage says retail agents can submit a difficult risk by email, ACORD form, screenshot or one sentence. The team handles intake, market selection, carrier responses, quotes, subjectivities and binding in one file, with the same named people on the account. Hedge homepage
The public developer docs expose a second path. Retail brokers can submit risks, check appetite, run quotes and read policies and payments through an API, CLI or a read-only AI connector. Access is authenticated with short-lived OAuth tokens and scoped to the brokerage. Hedge Broker API docs
Why I’d look closer
The product’s wedge is speed on the files standard markets do not handle cleanly. The site names cat-exposed property, thin-file professional risks and distressed cyber as examples. That is a better fit definition than “insurance AI.”
The founder context supports the operating model. The about page describes Luke Button’s previous brokerage and growth work and Luke Rosa’s systems background. The company emphasizes the same four people staying with the file through intake, quote, bind and renewal.
What could make it the wrong choice
Hedge is a broker and wholesale placement layer, not a self-serve policy marketplace. A retail agent needs to understand appointment, carrier access, admitted versus non-admitted markets, state constraints, compensation and who is responsible for the final placement.
The public docs show API and connector capabilities, but a writer did not authenticate or test them. A brokerage should verify scopes, data handling, quote timing, policy documents, audit history and the exact point where a human broker takes responsibility.
My editorial take
I would shortlist Hedge for a retail broker handling hard commercial accounts where the bottleneck is specialty-market access and follow-up. I would not choose it because it has an AI label. The useful product is the named human team plus the shared file; the API is valuable when the brokerage already has a system that should feed that process.
Quick facts
| Field | Sourced detail |
|---|---|
| Product | Specialty wholesale brokerage and broker API |
| Buyer | Retail insurance agents and brokers |
| Workflow | Intake, appetite, placement, quotes, bind and policy delivery |
| Integration | REST API, CLI and read-only AI connector are documented |
| Main fit question | Is the file hard because of market access and placement, not simple quoting? |
Sources checked
Hedge homepage, Broker API docs, about page and YC profile were checked on 2026-09-19.
Cohort context
Hedge is listed in Spring 2026. In our 2026-09-18 directory snapshot, 21 of 193 listed companies in that cohort have YC’s primary industry label Fintech (10.9%). This is a current-directory comparison, not an original intake count or a performance ranking. Nine-cohort dataset.
Public website snapshot
Observed 2026-09-19T16:16:15.959Z in raw homepage HTML. This records visible metadata and advertised links, not agent execution or product quality.
| Signal | Homepage observation |
|---|---|
| Product description metadata | Observed |
| Canonical link | Observed |
| H1 or H2 heading | Observed |
| Typed structured data | Observed |
| Docs/developer link | Observed |
| Pricing link | Not observed in this response |
| llms.txt link | Observed |
| Markdown alternate | Not observed in this response |
Public observations · Collection method. Missing links here do not establish that a capability or file is absent elsewhere.
About the author
Cofounder of Lazyweb (a16z Speedrun). Previously grew subscriptions and built native ads at Duolingo. Writes First1000 (90,000+ subscribers).
I cofound Lazyweb and publish Mudpie. This is an owner-written publication, not an independent testing organization. Research notes distinguish observations, sourced reporting and editorial judgment.
First1000 ↗ · X ↗