01Your app
Vehicle photos CarHub SDK Capture & upload
Vehicle intelligence,
through one API.
Turn vehicle images and data into inspections, enriched records, and listing-ready media. Models, data, and SDKs—inside your product.
Vehicle photos02Intelligence, connected
CarHubAPI
AI modelsVehicle data
Damage detection
One key. One integration.
03Your customer experience
Damage analysisExample
Condition report
Visible damage, located and classified.
- Damage locations
- Affected panels
- Severity assessment
Your interface. Our intelligence. Your customer.
Available in 66+ countries🇺🇸 🇨🇦 🇲🇽 🇬🇧 🇩🇪
Model Context Protocol
Build your app with agents and CarHub endpoints.
Use our MCP to bring active CarHub models into your agent as tools, with the same API key, limits and pricing.
Two ways to build
Create the application, or integrate the platform directly.
Choose the route that fits your team. Both use the same automotive AI, SDKs and vehicle data underneath.
CarHub Apps
AUTOSAVED App builder
Describe what your team needs
What would you like to build for your automotive workflow?
Create me an app to take pictures of my cars and put them in a showroom.
Building Showroom Capture GENERATING
Planning the capture flow
Adding guided photography
Creating the showroom scene
Preparing managed deployment
Ask for a change or describe another app…
LIVE PREVIEW
Showroom Capture
Showroom
12 VEHICLES
READY TO PUBLISHStudio 012026 vehicle
8 photos · showroom applied
Inventory Take photos
Your first app preview is ready02:18
CarHub Apps
Describe it. See it take shape.
Start with the workflow in your own words. CarHub assembles the capture experience, automotive intelligence and managed deployment into an app your team can keep editing.
Explore AppsBuild directly
Prefer APIs and SDKs?
Integrate the same platform into software your team already owns.
Explore the platformChoose an outcome
Start with one API call. Move from a first request to a production workflow.
Each solution combines the necessary models, capture steps and review points into one implementation path. Every underlying endpoint remains available separately.
Image productionImage production
Automotive remarketing
Standardise exterior imagery, recover weak source photos and replace license plates without sending a vehicle through a studio.
Marketplaces & DMSDealershipsAuctions & logistics
/v1/render/backgroundExplore →
Condition intelligenceCondition intelligence
AI tire inspection
Identify the tire, locate each wheel and grade visible tread, sidewall damage and wear consistently across a fleet or inspection flow.
DealershipsRental & car sharingAuctions & logistics
/v1/tire/detectExplore →
Damage intelligenceDamage intelligence
Exterior damage inspection
Turn a guided photo set or walkaround into damage masks tied to named body parts, ready for triage, handover or review.
DealershipsInsurance & claimsRental & car sharingAuctions & logistics
/v1/damage/detectExplore →
Vehicle identityVehicle identity
License plate scanning
Scan a vehicle plate from a phone photo and return normalised text, issuing country and region—whether it is angled, distant or captured in poor light.
Marketplaces & DMSDealershipsRental & car sharingAuctions & logistics
/v1/plate/readExplore →The stack
Three layers. One key, one schema, one invoice.
Take the whole stack or one endpoint from it. Nothing here requires adopting the rest.
Layer 1
Components
What your customer looks at
player · capture · review · report
4 SDKs Explore layer
Layer 2
Models
What reads the vehicle
segment · damage · severity · pricing · render
23 endpoints Explore layer
Layer 3
Data
What we do not compute ourselves
VIN · specs · battery · history · finance
9 domains Explore layer
Layer 1 · Components
Drop finished components straight into your website.
Four SDKs — player, capture, review, report — shipped for Web, iOS and Android, so nobody on your team writes a WebGL viewer or a guided-capture camera flow.
Player SDK
Embeddable 360° player — drops into your own site against a vehicle URL
Capture SDK
Camera flow that guides a non-expert through a complete shot set, start to finish
Review SDK
Human-in-the-loop validation and correction of model output
Report SDK
Composed condition report, customer-branded, web or export
Web · iOS · Android
Layer 2 · Models
A car arrives as photographs. It leaves as structured data.
Each endpoint is priced and rate-limited on its own. Call one in isolation, or chain the set — nothing assumes you adopted the others.
Hover a model to see it run · the tracks park while you read
Layer 3 · Data
Everything true about a vehicle that a model cannot see.
Sourced from supported vehicle-data providers, then normalised into one schema behind the same key. You integrate one contract instead of provider-specific formats.
9 source domains Open Layer 3 →
- Identity
- VIN decode, build sheet, factory options, plate → VIN lookup
- Specs
- Technical data, equipment, dimensions, powertrain
- Battery
- State of health, usable capacity, range and charging data
- Value
- Market pricing, residuals, depreciation curves
- History
- Mileage records, ownership, accidents, write-off status
- Compliance
- Recalls, service campaigns, emissions, homologation, taxes
- Financing
- Outstanding balances, lender records and settlement data
- Parts
- OEM references and catalogues — feeds pricing/repair
- Risk
- Stolen-vehicle, fraud and risk checks
Domain 01
VIN + plateFactory record
Domain 02
PowertrainEquipment
Domain 03
State of healthRange
Domain 04
Market viewResiduals
Domain 05
OwnershipMileage
Domain 06
RecallsEmissions
Domain 07
SettlementLender record
Domain 08
OEM catalogueRepair
Domain 09
StolenFraud
Available across supported marketsNormalised into one schema · one key
Get started
Start with one endpoint.
Send a photo to /v1/vehicle/pose and read the response. Everything else on this page runs on the same key.
Key issued on email verification · every endpoint priced on its own · one invoice