wefox
wefox is a Berlin-headquartered digital insurance distribution platform that connects insurance carriers, brokers, and end customers through a single technology stack. Founded in 2014 and originally known as FinanceFox, the company operates across Germany, Austria, Switzerland, Italy, the Netherlands, Spain, and France, selling personal-lines products such as motor, home, liability, life, and commercial insurance via its in-house carrier (wefox Insurance) and a network of independent brokers. wefox positions itself as an "indirect" insurtech — meaning it distributes through human advisors augmented by software rather than selling direct-to-consumer — and has historically been one of Europe's most highly funded insurtech companies, with backing from Mubadala, Target Global, Salesforce Ventures, OMERS Ventures, Eurazeo, Mountain Partners, and others. The platform itself is a multi-tenant SaaS used by brokers and agents to manage customer relationships, quote and bind policies across multiple carriers, handle claims, and trigger commissions. wefox does not publish a public developer portal, OpenAPI specifications, SDKs, or a github.com/wefox organization; integration with the wefox platform is carrier-, broker-, and partner-mediated rather than self-service, and there is no Tier-1 developer surface to document. This repo profiles wefox as an insurance distribution business and tracks any future move toward a public API program.
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 wefox 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 — wefox scores 10.8/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 wefox
Each block below is one kind of artifact we hold for wefox. 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 wefox — 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.
Access & Security 1
Authentication, authorization, and security posture
Commercial 2
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 5
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/wefox · machine-readable index on apis.io