Embroker
Embroker is a San Francisco-based digital business insurance broker and insurtech platform founded in 2015 by Matt Miller, on a mission to make commercial insurance simple, clear, and tailored to each industry. Embroker operates a digital-first online platform where businesses can compare, quote, purchase, and manage commercial insurance policies directly, with industry-specific programs for funded startups, tech companies, law firms, venture capital and private equity firms, financial services professionals, consultants, real estate agents, and small businesses. Its coverage portfolio includes Business Owners Policy (BOP), commercial general liability, professional liability, technology errors and omissions, cyber insurance, directors and officers, employment practices liability, commercial crime, key person, workers compensation, and lawyers professional liability, often bundled into industry packages such as the Startup Bundle, Law Bundle, and MPL Bundle. In 2017 Embroker partnered with Munich Re to underwrite its own digital insurance products; in 2020 it launched Embroker Access for retail and wholesale brokers; and in 2023 it launched Embroker One, an AI- and machine-learning-driven platform for real-time risk assessment and policy recommendations. The company has protected 9,500+ businesses across 16,000+ policies and raised a $100M round in 2021 led by FTV Capital. Embroker's revenue model is brokerage commissions, managing general agent (MGA) underwriting fees on its own products, and platform access for partner brokers; there is no public developer API, SDK, or open-source release — its GitHub organization contains only archived forks of third-party libraries and a small number of internal tooling repositories.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Embroker the way a machine reads it — 2 machine-readable artifacts, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Embroker scores 15.1/100 (emerging), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Embroker
Each block below is one kind of artifact we hold for Embroker. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
GraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Embroker GraphQL Schema
Embroker is a San Francisco-based digital business insurance broker and insurtech platform that enables businesses to compare, quote, purchase, and manage commercial insurance p...
GRAPHQLSecurity Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Embroker — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Commercial 2
Pricing, plans, and the legal terms of use
Company 8
The organization behind the API
Scroll within the panel for all 8 ·
Other 20
Properties that don't map to a standard resource type
Scroll within the panel for all 20 ·
← All providers · Data indexed from github.com/api-evangelist/embroker · machine-readable index on apis.io