Ensurance
Ensurance Limited (ASX:ENA) was an Australian ASX-listed insurance underwriting agency headquartered in Perth, Western Australia, marketing itself as "innovating the online insurance sector." Its Australian arm, Ensurance Underwriting Australia, operated as a wholesale underwriting agency under an Australian Financial Services Licence, assembling a consortium of local and international capacity — including Lloyd's, Swiss Re and XL Catlin — behind construction-specific products sold exclusively through intermediaries: Licensed Builder Annual Construction, Plant and Liability, Project-Specific Construction, Trades Liability, Owner Builder, and Home and Contents insurance, distributed to a broker network the company described as 340-plus intermediaries. A sister company, Ensurance UK Limited, ran as a Managing General Agent authorised and regulated by the UK Financial Conduct Authority and a coverholder at Lloyd's. The group's API posture is nil and always was. Ensurance never published a public developer portal, API reference, OpenAPI or Swagger definition, Postman collection, GraphQL endpoint, webhook or event catalogue. What the company called its "customised online platform" for intermediaries was BOB (bob.ensurance.com.au), a form-based, session-login ASP.NET MVC quote-and-proposal wizard keyed to per-agent codes — an agent login wall, not a programmable interface. No ACORD, AL3, ACORD XML or NGDS reference appears anywhere in the company's live or archived web estate. As of this review the ensurance.com.au TLS certificate has expired and every path on the domain, along with the ensurance.ltd domain family, blanket 301-redirects to Chase Underwriting Solutions Pty Ltd, an Australian professional-lines underwriting agency that likewise publishes no API. Ensurance is recorded here as a partner-gated, no-public-API insurance provider in the Australian market — a faithful data point for a sector where the Consumer Data Right was designated for general insurance and then deferred, leaving carriers and underwriting agencies with no forcing function to expose anything.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles Ensurance the way a machine reads it — 1 machine-readable artifact, 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 — Ensurance scores 9.3/100 (minimal), 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 Ensurance
Each block below is one kind of artifact we hold for Ensurance. 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.
Security 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 Ensurance — 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.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/ensurance · machine-readable index on apis.io