Auctions & logistics

A condition report a buyer will bid on, produced by whoever is standing next to the car.

One walkaround in, a full report out — identity, panels, damage, severity, tires, engine bay and a valuation — assembled by the models rather than by whoever had the clipboard.

Auction houses, remarketers, transporters and the yards in between

Today

A car changes hands four times between the yard and the buyer, and the only condition record is a paper sheet somebody filled in at dusk.

What changes

  • The same report whether the yard is in Lyon or Lisbon, produced by staff you did not have to train as inspectors.
  • Remote bidding on a 360 with damage pinned to the panel, instead of nine photos and a phone call.
  • Timestamped condition at every handover point, keyed to the VIN.

Where it starts

One endpoint, before you commit to anything.

One call is the entire report, billed as one blended inspection. A driver with a phone is the whole capture apparatus — no lane, no booth, no trained inspector.

the first call

per vehicle

POST/v1/inspections

model: the bundle — eight stages

async by default · webhook or poll · independently rate-limited

The chain

The flow that first call sits in.

Each row is a real endpoint, priced and rate-limited on its own. Call one, call the set, or let /v1/inspections chain them for you.

  1. 01
    POST/v1/video/onboard

    video-onboarding · per video

    One walkaround from a phone, indexed into positioned frames

  2. 02
    POST/v1/vehicle/analyse

    car-analyser · per vehicle

    Identity, attributes and an overall condition profile in one read

  3. 03
    POST/v1/parts/decompose

    parts-decomposition · per vehicle

    The component map every line of the report hangs on

  4. 04
    POST/v1/damage/detect

    damage-detection · per image

    What is wrong, located and typed per panel

  5. 05
    POST/v1/damage/severity

    severity-estimation · per detection

    How wrong — cosmetic through structural, per detection

  6. 06
    POST/v1/tire/detect

    tire-detection · per image

    Wear and sidewall damage graded per wheel, the line buyers always ask about

  7. 07
    POST/v1/engine/detect

    engine-detection · per image

    Engine-bay read: components present, leaks, missing elements

  8. 08
    POST/v1/pricing/vehicle

    car-pricing · per vehicle

    A valuation built from identity plus what was actually observed, not from a trim guess

Across the stack

What this path draws on, layer by layer.

Layer 1 · Components

all →
Player SDK
Embeddable 360° inspection viewer — drops into your own site against a tokenised report URL
Report SDK
Composed condition report, customer-branded, web or export

Layer 3 · Data

all →
Identity
VIN decode, build sheet, factory options, plate → VIN lookup
History
Mileage records, ownership, accidents, write-off status
Compliance
Recalls, service campaigns, emissions, homologation, taxes
Value
Market pricing, residuals, depreciation curves
Risk
Stolen and outstanding-finance checks

Where it goes

Then the same key runs the lot

The report is the wedge. Around it sits everything a lot page and an arbitration desk need, already normalised per country.

  • Lot disclosures

    Recalls, mileage records and write-off status pulled per country and normalised into one schema

  • Catalogue imagery

    image-backgrounding renders the lot photos from the capture you already took

  • Damage in transit

    A second inspection at delivery localises who caused what, on the same part map

  • Arbitration

    Every claim traceable to a masked detection on a named part, with the frame it came from

What we do not claim

The report is only as complete as the walkaround. video-onboarding reports which positions it actually got — a panel nobody filmed comes back as missing rather than as undamaged.

Start with /v1/inspections

One call, on your own data, before anything in your product changes.