[ rails for curators and capital ]
Open rails for coverage capital.
Run your category vault on our rails, or fund the pool and earn from real premiums.
[ features ]
Vault, pool, claims desk.
Your vault, your book
One vault, one category, one curator. You set pricing within the constitution. Claims stay with your claims agent.
Judgment stays with the underwriter
Shared capital
LPs fund the pool. You do not put surplus behind every bind. Capacity is withdrawable down to the solvency floor.
You do not lock your own surplus
Checkout you already have
The distribution API is REST: quote, offer, bind, documents, claim intake, payouts. An XCover-compatible wrapper sits on stacks that already speak that pattern. Partners never see wallets or chain objects.
Existing checkout, same book
Claims in the open
Feed-settled covers pay on the trigger. Curator covers settle in the claims console: decision and payout in one interaction.
The decision is on the record
[ use cases ]
Curators and capital.
Curators
Your book. Our rails.
Insurers and MGAs run a category vault: your underwriting, your claims agent, your distribution. LP capital instead of surplus. Bind through the distribution API, including the XCover wrapper, so the checkout you already run stays put.
Liquidity providers
Fund real coverage. Earn real yield.
Supply USDC to a vault pool and earn a share of premium yield plus lending yield on idle liquidity. Uncorrelated with RWA and lending risk.
[ earn ]
Real yield from real premiums.
Provide USDC to a vault pool and earn a share of the premium pool yield plus lending yield on idle liquidity, pro-rata to your share. Withdrawable down to the solvency floor.
Stake
Staked INSUR earns 100% of the revenue pool (the 2.5% protocol fee on every premium), paid in USDC, pro-rata to stake.
[ protocol ]
Coverage in your checkout. One API.
You already have the judgment and the distribution. Capacity sits with someone else. Insur gives you a vault, a pricing engine, a claims console, and an LP pool, listed by governance. Bind through the distribution API so a carrier checkout talks REST, including an XCover-compatible wrapper. Partners never see wallets or chain objects. Origination only. The vault stays yours.
[ faq ]
Fees, claims, capital.
Yes. Curators are governance-listed insurers and MGAs. You get a category vault, pricing parameters within the constitution, a claims console, and LP capital instead of your own surplus. Distribution stays yours.
The distribution API is REST: quote, offer, bind, policy documents, claim intake, payout webhooks. An XCover-compatible wrapper translates that for checkouts that already speak XCover. Partners never see wallets or chain objects. Origination only; vault configuration stays on the curator contracts.
LPs supply USDC to a vault and earn a share of the premium pool yield plus lending yield on idle liquidity, pro-rata. Yield comes from real premiums, not token emissions. Withdrawals respect the vault solvency floor.
The curator's claims agent, after document verification. The path is fixed at vault creation. Parametric covers on the Insur-run vault pay when an allowlisted feed reports the trigger. There is no review step.
A bind that would push active exposure above LP liquidity times the vault utilization ratio is rejected. Payouts drain the premium pool first, then LP principal, never the staker revenue pool. Withdrawals stop at the same utilization floor.
2.5% of every premium, on every vault, to the revenue pool for INSUR stakers. Non-zeroable. On curator vaults the reference split sends 5% of gross to the LP pool; the curator keeps the rest, within protocol caps.
[ ready to start? ]
Open rails for coverage capital.
Curators run the book. LPs fund it.