Laka
Laka is a European InsurTech with deep micro-mobility expertise, insuring bikes, e-bikes, e-scooters and cycling gear against theft, accidental damage and loss, and providing riders and businesses with liability and personal accident cover. Laka exposes two partner-facing APIs. The Quote API is a lightweight integration for Introducer partners — retailers, e-commerce stores, bike brands and online communities — that returns pricing to riders, shares rider information to pre-fill onboarding, hands customers directly into Laka onboarding, and checks whether a rider has taken out cover. The Platform API supports Group partnerships where Laka issues the partner a Group policy whose benefits are extended to the partner's members: partners can list policies, add and remove beneficiaries, manage products and documents, and create, submit and track claims. Both APIs run as regional instances across the UK (gb) and EU (nl), are secured with API keys, and require x-api-region and x-api-language headers so the insured party is attributed to the correct regulatory region.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Laka the way a machine reads it — 21 machine-readable artifacts across 2 APIs, 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 — Laka scores 41.2/100 (developing), with a separate agent-readiness read of 26/100 (agent aware). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Laka's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/laka/"
title="Laka on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/laka.svg"
alt="Laka Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/laka/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/laka/"
title="Laka on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/laka/card.svg"
alt="Laka Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Laka
Each block below is one kind of artifact we hold for Laka. 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 9
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.
Laka accounts API
The accounts API from Laka — 6 operation(s) for accounts.
Laka claims API
Claims API
Laka deeplinks API
The deeplinks API from Laka — 1 operation(s) for deeplinks.
Laka fleets API
The fleets API from Laka — 1 operation(s) for fleets.
Laka policies API
The policies API from Laka — 14 operation(s) for policies.
Laka quote API
The quote service gets quotes.
Laka quotes API
The quotes API from Laka — 1 operation(s) for quotes.
Laka reporting API
The reporting API from Laka — 3 operation(s) for reporting.
Laka tasks API
The tasks API from Laka — 1 operation(s) for tasks.
Scroll within the panel for all 9 ·
Open Collections 10
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONLaka accounts API
OPEN COLLECTIONLaka accounts claims API
OPEN COLLECTIONLaka accounts deeplinks API
OPEN COLLECTIONLaka accounts fleets API
OPEN COLLECTIONLaka accounts policies API
OPEN COLLECTIONLaka accounts quote API
OPEN COLLECTIONLaka accounts quotes API
OPEN COLLECTIONLaka accounts reporting API
OPEN COLLECTIONLaka accounts tasks API
OPEN COLLECTIONScroll within the panel for all 10 ·
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.
Resources
Every other property we hold for Laka — 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 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 4
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/laka · machine-readable index on apis.io
This is an independent, third-party profile of Laka, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.