Zensurance

Zensurance is a Toronto-based digital commercial insurance brokerage founded in 2016 that sells small-business and freelancer coverage online across every Canadian province, placing risk with Canadian carriers rather than underwriting it. Its book is commercial property and casualty — general and commercial general liability, professional liability and errors and omissions, cyber liability, directors and officers, commercial property, commercial auto, builder's risk, and a long tail of trade- and profession-specific packages — sold through a quote-to-bind web flow marketed as an instant online price with licensed broker support and claims advocacy behind it. It sits in the thin digital-broker layer beneath Canada's Big-Few carrier oligopoly, in a market with no open-insurance mandate — OSFI supervises federally-regulated insurers prudentially while FSRA, the AMF, and the other provincial regulators own market conduct, and Consumer-Driven Banking excludes insurance outright. Its API posture reflects that. Zensurance publishes no public, self-serve developer portal, no reference documentation, and no downloadable OpenAPI, Swagger, GraphQL, or AsyncAPI definition. The company's partnership page advertises "seamless API integrations and co-branded white-label tools" for distribution partners, but the only route to that surface is a partnership application form — the integration is partner-gated and privately negotiated. A first-party host at api.zensurance.com answers on the public internet (HTTP 200, returning a bare version string, with a /health endpoint) but it is the undocumented backend for Zensurance's own quoting and policy application, not a published product API. No ACORD, AL3, ACORD XML, NGDS, or agency-management-system integration claim appears anywhere on the company's public web properties. The one machine-addressable surface the company does publish for automated consumers is an llms.txt at www.zensurance.com/llms.txt — a 178KB marketing index of its pages, blog posts, and FAQs (which inadvertently lists its zenstage.wpengine.com staging host rather than the production domain). It describes insurance products for AI assistants; it documents no API.

Zensurance is profiled on the APIs.io network. Tagged areas include Insurance, Canada, Insurtech, Broker, and Property and Casualty.

Zensurance’s developer surface includes engineering blog, support, signup flow, and 10 more developer resources.

17.8/100 emerging ▬ flat Agent 0/100 human only Full breakdown ↓
scored 2026-07-27 · rubric v0.5
0 APIs
InsuranceCanadaInsurtechBrokerProperty and CasualtyCommercial InsuranceSmall Business InsuranceCyber InsuranceDigital BrokeragePartner Gated

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 17.8/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 1.3 / 20
Commercial Clarity 6.8 / 20
Operational Transparency 0.7 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/zensurance: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Zensurance Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 1

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 5

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: zensurance
url: https://raw.githubusercontent.com/api-evangelist/zensurance/refs/heads/main/apis.yml
name: Zensurance
kind: company
description: Zensurance is a Toronto-based digital commercial insurance brokerage founded in 2016 that sells small-business
  and freelancer coverage online across every Canadian province, placing risk with Canadian carriers rather than underwriting
  it. Its book is commercial property and casualty — general and commercial general liability, professional liability and
  errors and omissions, cyber liability, directors and officers, commercial property, commercial auto, builder's risk, and
  a long tail of trade- and profession-specific packages — sold through a quote-to-bind web flow marketed as an instant online
  price with licensed broker support and claims advocacy behind it. It sits in the thin digital-broker layer beneath Canada's
  Big-Few carrier oligopoly, in a market with no open-insurance mandate — OSFI supervises federally-regulated insurers prudentially
  while FSRA, the AMF, and the other provincial regulators own market conduct, and Consumer-Driven Banking excludes insurance
  outright. Its API posture reflects that. Zensurance publishes no public, self-serve developer portal, no reference documentation,
  and no downloadable OpenAPI, Swagger, GraphQL, or AsyncAPI definition. The company's partnership page advertises "seamless
  API integrations and co-branded white-label tools" for distribution partners, but the only route to that surface is a partnership
  application form — the integration is partner-gated and privately negotiated. A first-party host at api.zensurance.com answers
  on the public internet (HTTP 200, returning a bare version string, with a /health endpoint) but it is the undocumented backend
  for Zensurance's own quoting and policy application, not a published product API. No ACORD, AL3, ACORD XML, NGDS, or agency-management-system
  integration claim appears anywhere on the company's public web properties. The one machine-addressable surface the company
  does publish for automated consumers is an llms.txt at www.zensurance.com/llms.txt — a 178KB marketing index of its pages,
  blog posts, and FAQs (which inadvertently lists its zenstage.wpengine.com staging host rather than the production domain).
  It describes insurance products for AI assistants; it documents no API.
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
tags:
- Insurance
- Canada
- Insurtech
- Broker
- Property and Casualty
- Commercial Insurance
- Small Business Insurance
- Cyber Insurance
- Digital Brokerage
- Partner Gated
created: '2026-07-25'
modified: '2026-07-25'
specificationVersion: '0.19'
apis: []
common:
- type: Website
  url: https://www.zensurance.com/
- type: Blog
  url: https://www.zensurance.com/blog
- type: BlogRSS
  url: https://www.zensurance.com/feed
- type: Partners
  url: https://www.zensurance.com/zensurance-partnerships
  name: Zensurance Partnership Program
  description: Partner program page. Advertises "seamless API integrations and co-branded white-label tools" for distribution
    partners, but exposes no documentation, no endpoints, and no specification — access is by partnership application form
    only.
- type: CustomerPortal
  url: https://app.zensurance.com/
  name: Zensurance Customer Application
  description: Authenticated first-party web application for quoting and managing policies. Login wall, not a developer surface.
- type: GitHubOrganization
  url: https://github.com/zensurance
  name: Zensurance Inc.
  description: Public GitHub organization ("Toronto based Insurtech startup"). Repositories are internal tooling, Google Apps
    Script templates, and forked Azure AI samples — no API definitions or client SDKs published.
- type: Careers
  url: https://www.zensurance.com/careers
- type: PrivacyPolicy
  url: https://www.zensurance.com/privacy-policy
- type: TermsOfService
  url: https://www.zensurance.com/terms-of-use
  name: Terms of Service
  description: Public terms of service for the Zensurance website and customer application. Verified HTTP 200 on 2026-07-25.
- type: Support
  url: https://www.zensurance.com/contact
  name: Contact Us
  description: Public contact page — phone, email, and broker contact form, plus 24/7 claims support. Zensurance also runs
    a Zendesk instance at zensurance.zendesk.com, but its help centre is not public (/hc/en-us returns 403; the root redirects
    to a sign-in wall), so the contact page is the only open support channel.
- type: SignUp
  url: https://www.zensurance.com/quote
  name: Get a Quote
  description: Self-serve quote-to-bind entry point, which is how a customer account is created. This is the consumer sign-up
    path — there is no developer or API sign-up, and no partner API onboarding outside the partnership application form.
- type: LLMsTxt
  url: llms/zensurance-llms.txt
  name: Zensurance llms.txt
  description: Harvested verbatim from https://www.zensurance.com/llms.txt (HTTP 200, 178KB). A marketing index of pages,
    blog posts, and FAQs for AI assistants — no API, endpoint, or developer content in it. Its links point at the zenstage.wpengine.com
    staging host rather than www.zensurance.com.
- type: DomainSecurity
  url: security/zensurance-domain-security.yml
  name: Domain and transport security posture
  description: Probed TLS/HSTS on www, api, and app hosts and DNSSEC/CAA/SPF/DMARC on zensurance.com. HSTS everywhere; no
    DNSSEC, no CAA; SPF present, DMARC at p=quarantine; api and app negotiate TLS 1.2 only.
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com