Concirrus
Concirrus Ltd is a London-headquartered insurtech founded in 2012 that builds AI-driven underwriting software for the specialty and commercial insurance market — marine (hull, cargo, P&I), aviation, construction, property, and political violence and terrorism. Its platform (Quest, Marine One, the Underwriting Workbench, Exposure Management, Loss Run Intelligence, and an "Enterprise Model" universal submission-ingestion layer) ingests broker submissions, structures the risk data, scores behavioural risk, and returns rating and exposure decisions to carriers, MGAs and brokers — much of it aimed at the Lloyd's and London subscription market. Concirrus is a vendor to insurers rather than an insurer itself, so it touches quote and rating rather than bind, issue or FNOL. Its API posture is partner-gated: marketing describes "a modular, API first platform" and "seamless integration with London Market platforms", but as of 2026-07-25 there is no public developer portal, no published API reference, no downloadable OpenAPI/Swagger, no Postman collection, and no public GraphQL or webhook catalog. Every developer and docs hostname probed (developer./developers./docs./api. on both concirrus.com and concirrus.ai) does not resolve, and every on-site developer path returns 404. Integration is obtained through a commercial engagement or the partner ecosystem programme, not self-serve signup. No ACORD, AL3, NGDS or ACORD XML reference appears anywhere on the public site. Concirrus does publish a real compliance posture: in August 2025 it announced ISO/IEC 42001 (AI management), ISO/IEC 27001 (information security) and SOC 2 certification, claiming to be the first insurtech to hold all three — though no trust center or downloadable report accompanies the announcement.
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 Concirrus 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 — Concirrus scores 15.8/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 Concirrus
Each block below is one kind of artifact we hold for Concirrus. 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 Concirrus — 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 1
Pagination, idempotency, versioning, errors, and events
Access & Security 2
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 1
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 7
The organization behind the API
Scroll within the panel for all 7 ·
Other 4
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/concirrus · machine-readable index on apis.io