Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Wawanesa Insurance

The Wawanesa Mutual Insurance Company, founded in 1896 in Wawanesa, Manitoba and headquartered in Winnipeg, is one of Canada's largest property and casualty mutual insurers, writing auto, home, condo, tenant, seasonal residence, farm and commercial lines across every province and territory through a 100% independent broker distribution model, alongside its wholly-owned life and group subsidiary Wawanesa Life. Wawanesa runs its policy, claims and billing on Guidewire InsuranceSuite following a roughly $300 million Strategic Systems Renewal that made it one of the first Canadian insurers to put its entire product suite online, and it has announced a broker-facing API programme — most notably a Commercial Small Business API aligned to CSIO data standards that supports real-time rating, quoting and binding — plus CSIO My Proof of Insurance electronic pink slips. None of that surface is public: Wawanesa publishes no developer portal, no API reference, no OpenAPI, and no self-serve signup. Probes of developer./developers./docs. wawanesa.com do not resolve, api.wawanesa.com answers 403 at the root, and the only integration path is the Salesforce-based Broker Platform behind an Okta login with onboarding brokered by a Wawanesa Business Development representative. Canada has no open-insurance mandate — Consumer-Driven Banking excludes insurance outright — so the connectivity layer here is CSIO, not ACORD, and the honest posture is partner-gated with no public API. What Wawanesa does publish is certification: it holds CSIO's API Security Standards Certification (2024-10-29), was the first CSIO member certified in JSON API Standards for Billing (2025-02-05), was the first insurer to attain Claims eDocs Certification (2022-04-04), and contributed nine reusable API packages — Quote, New Business, Policy Inquiry, Policy Update List, Policy Cancellation, Risk Appetite, Required Fields, Billing Inquiry and eDocs — to CSIO's Reusable Services Library for other carriers and BMS vendors to implement.

human only

Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.

Kin Score

API Evangelist profiles Wawanesa Insurance the way a machine reads it — 4 machine-readable artifacts across 1 API, 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 — Wawanesa Insurance scores 30.0/100 (thin), with a separate agent-readiness read of 14/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 Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 30.0/100 · thin
Contract Quality 0.0 / 25
Developer Ergonomics 3.5 / 20
Commercial Clarity 8.4 / 20
Operational Transparency 0.0 / 13
Governance 0.0 / 12
Discoverability 8.0 / 10
Regulatory · Securities & Market Data 13.1 / 15
Agent readiness — 14/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 10 / 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 4 / 4
Consent & Bot Identity 0 / 3

How we profile Wawanesa Insurance

Each block below is one kind of artifact we hold for Wawanesa Insurance. 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.

APIs 1

Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.

Individual APIs this provider publishes, each with its own machine-readable definition.

Wawanesa Commercial Small Business API

Broker-facing commercial small business API announced by Wawanesa on 2022-03-30, built with HUB International and described by Wawanesa as "fully aligned with CSIO data standard...

Security Posture 2

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.

Wawanesa Authentication

oauth2/openIdConnect · 3 schemes

SECURITY

Wawanesa Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.

OAuth scopes governing access to this provider's APIs.

Wawanesa Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Every other property we hold for Wawanesa Insurance — 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 3

Portal, sign-up, and the first successful call

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Learn 1

Tutorials, courses, talks, and written guidance

Operate 2

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

← All providers · Data indexed from github.com/api-evangelist/wawanesa · machine-readable index on apis.io