Manage a bike or connected-device embedded insurance policy's risk items and file a claim using Qover's Policy and Claims APIs
domain: qover.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Request an API key from Qover's product team; Qover first grants access to a sandbox environment before issuing a production key.
Include the API key in the header of every REST request per Qover's key-based authorization scheme.
Use the Policy API to add or remove "risk-items" (the insured subjects, e.g., a bike or a fintech card) from a policy dynamically and in real time.
Use the Claims API to let a customer file a claim from your app or website and track its status.
Link the Policy and Claims APIs together to run automations such as claims-eligibility checks against active risk-items.
Known gotchas
Qover's exact endpoint set is not fixed/standard — it is configured per partner and per underlying insurer during implementation, so treat any endpoint list as provisional until confirmed with Qover for your specific program.
API keys must never be embedded in client-side code, public repos, or documentation files — Qover explicitly warns against storing keys in publicly accessible locations.
Sandbox and production use separately issued API keys; a sandbox key will not authenticate against production endpoints.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?