Insurance verification platform

Vehicle ownership and condition checks that feel simple on a phone and controlled in the insurer workspace.

i60 Inspect separates the public customer journey from the protected insurer portal. The policyholder opens a signed link and completes a short capture wizard. The insurance company signs in to its organization, manages API keys, and creates journeys from its own systems.

Public verify No auth on the client link Better Auth Email, orgs, and API keys Railway Fast SvelteKit deployment
How it works

One platform, two very different surfaces.

Live shape
Public journey

Northfield Mutual

Signed route, phone-first wizard, guided capture, and visible progress for the policyholder.

ND 274-618 express tier
Insurer workspace

Northfield Mutual org

Protected access for account setup, organization branding, and API key management.

API keys Verified email
POST https://i60-inspect-production.up.railway.app/api/v1/journeys
Headers:
  x-api-key: ins_live_xxxxxxxxxxxx
  content-type: application/json
Body:
{
  "policyNumber": "NF-2481194",
  "customerName": "Lebo Maseko",
  "existingCustomer": true,
  "tenureMonths": 38,
  "channel": "existing-book",
  "vehicle": {
    "registration": "ND 274-618",
    "make": "Toyota",
    "model": "Corolla Cross",
    "year": 2023
  }
}
Platform shape

Designed around the way insurers actually operate.

The customer flow is intentionally short and camera-led. The operational controls sit behind the insurer organization where they belong.

Public client journey

The vehicle check link stays public. The long signed route is the gate, so the policyholder never hits a login wall on the phone.

Insurer workspace

Each insurance company is an organization with its own users, branding, API keys, and journey creation rights.

API-led orchestration

Your policy admin system creates journeys with an organization key, then sends the link through its own communication channels.

Mobile-first evidence

The capture flow is optimized for phone cameras, safe-area spacing, sticky progress, and one clear action at a time.

Operating flow

The journey stays light for the customer and structured for the insurer.

1. Create

Generate a secure journey

The insurer system submits customer and vehicle details to the API using an organization key.

2. Capture

Open a short wizard on the phone

The customer follows a compact camera-led sequence with progress, prompts, and clear evidence requirements.

3. Review

Return a defensible pack

The insurer receives a structured result for ownership checks, condition review, and anti-fraud triage.

Why this auth model

Better Auth fits the workspace side cleanly.

  • Organization-owned API keys keep external integrations scoped to the insurer workspace.
  • Email/password plus email verification is enough for the first release and avoids social-login clutter.
  • AI should support screenshot detection, damage triage, and continuity checks, not make silent final decisions.
  • Existing trusted policyholders can stay on a shorter journey while higher-risk cases step up automatically.
Mobile sample

The client flow is ready to test now.

Open the sample signed journey to inspect the phone wizard, sticky progress header, and camera-led capture steps.