# UVeye

> UVeye builds AI-powered automated vehicle inspection systems — "the MRI for cars." A vehicle drives
> through a scanning lane and UVeye returns a full condition report in seconds across four modules:
> Artemis (tires and tread), Helios (undercarriage), Atlas (exterior body damage) and Apollo
> (interior). The systems run in dealership service lanes, fleet and leasing depots, auctions and
> remarketing lots, rental returns, OEM plants and logistics/PDI ports. The UVeye Public API v1
> exposes that inspection data to third parties.

Generated by the API Evangelist enrichment pipeline on 2026-08-02. UVeye does not publish an
llms.txt of its own (probed: 404 on uveye.com, api.uveye.dev, api.v1.uveye.dev, uveye.dev).

## What the API does

- **Inspection details** — full inspection record by `inspectionId`, `vin`, `licensePlate` or
  `uniqueId` (barcode), with the Artemis/Helios/Atlas/Apollo module objects nested inside.
- **Latest inspections** — discovery: the most recent inspections for a `siteId`, `siteGroupId`
  (BAC for GM dealers) or `vin`, over a window of days, hours or a count. This is how you find the
  `inspectionId` values the other endpoints take.
- **Public link** — a customer-shareable link to an inspection. Expires 30 days after creation;
  the exact expiry comes back in `expirationDate`.
- **Inspection shared** — records that a public link was sent to a customer.
- **Quote** — appraisal data for an inspection: offer price, total reconditioning cost, and damages
  grouped by car part with per-repair estimates and images.
- **Image** — the raw inspection image behind a signed `?key=` URL. You do not build these URLs; they
  arrive embedded in the other endpoints' responses and expire after 1 hour.
- **Merchandise** — submit dealer inventory (≤100 vehicles per request); UVeye scans, renders
  multi-angle imagery and POSTs it back to your webhook. Mark VINs sold to stop merchandising them.

## How to call it

- Base URL (development, as published): `https://api.uveye.dev/v1/`. Production-US URLs are
  distributed through the "Production-US" Postman environment, which is not published anonymously.
- Every data operation is a **POST** with the identifier in the JSON body. Only `/image` is a GET.
  Any other method returns `405 unknown method, please use POST`.
- Auth: `uveye-api-key: <key>` header for everything except Merchandise. Generate the key in the
  Global Keys tab of the UVeye Back Office. Merchandise uses a separate
  `Authorization: Bearer <merchandise API key>` credential issued at onboarding.
- Supply exactly one identifier per lookup. Omitting all of them returns
  `400 Missing search criteria`.
- No pagination, no cursors, no rate-limit headers, no `Idempotency-Key`. Merchandise inventory
  resubmission is content-hash deduplicated and safe to repeat.
- Errors are an HTTP status plus a short message string — not RFC 9457 problem+json.

## Specs and artifacts

- [OpenAPI 3.1 (derived)](openapi/uveye-public-api-v1-openapi.yml): 8 operations + 1 webhook
- [Postman collection (verbatim, as published)](postman/uveye-public-api-v1-postman-collection.json)
- [Overlay](overlays/uveye-public-api-v1-overlay.yaml)
- [Authentication profile](authentication/uveye-authentication.yml)
- [API conventions](conventions/uveye-conventions.yml)
- [Error catalog](errors/uveye-problem-types.yml)
- [Webhook catalog](asyncapi/uveye-merchandise-webhooks.yml)
- [Rate limits](rate-limits/uveye-rate-limits.yml)
- [Lifecycle](lifecycle/uveye-lifecycle.yml)
- [Changelog](changelog/uveye-changelog.yml)
- [Sandbox / environments](sandbox/uveye-sandbox.yml)
- [Data model](data-model/uveye-data-model.yml)
- [Conformance](conformance/uveye-conformance.yml)
- [Agentic access contracts](agentic-access/uveye-agentic-access.yml)
- [Agent skills](skills/_index.yml)
- [Candidate MCP tool set (not published by UVeye)](mcp/uveye-mcp.yml)

## Docs

- [UVeye Public API v1 documentation](https://api.v1.uveye.dev/)
- [UVeye Back Office (issue API keys)](https://us.backoffice.uveye.app/)
- [Customer support](https://uveye.com/customer-support/)
- [Integrations](https://uveye.com/partners/integrations/)
- [Technical overview](https://uveye.com/technical-overview/)
- [Trust center — ISO/IEC 27001:2022, SOC 2 Type 2](https://trust.uveye.com/)
- [Privacy policy](https://uveye.com/privacy-policy/)
- [Terms and conditions](https://uveye.com/terms-and-conditions/)
- [Blog](https://uveye.com/blog/)

## Not published

No OpenAPI or AsyncAPI of UVeye's own, no GraphQL, no MCP server, no A2A agent card, no
`/.well-known/` documents (including security.txt), no SDKs in any public package registry, no CLI,
no public status page and no deprecation policy. Report vulnerabilities to security@uveye.com via
the trust center.