database api · rest + mcp · source-linked

Vehicle data API for source-linked car specifications.

Search resolved vehicle variants by make, model, model year, trim, powertrain, and specification fields, with the source behind each populated value available for review.

Built for automotive data engineers, analytics teams, EV product builders, insurers, and applications that need normalized vehicle specifications

Get the 133-record sample View pricing API reference

GET/v1/apex

cURL

authenticated production request

curl --get \
  "https://api.apex-db.org/v1/apex" \
  --data-urlencode "brand=Alfa Romeo" \
  --data-urlencode "limit=5" \
  --header "Authorization: Bearer $API_KEY"

43,077

records

sources

133

email sample

Full release 2026-10-21 · dated 2026-10-21. The sample bundle is delivered by email; production API calls require paid access.

record and matching

Understand what one result represents

Vehicle sources use different grains, market-year meanings, test cycles, trim labels, identifiers, and update schedules. Apex resolves those records without pretending that WLTP, EPA, registration, manufacturer, and derived facts are interchangeable.

Car specifications at vehicle-variant grain

A served row represents a resolved vehicle variant, not a VIN history, registration event, image asset, or generic nameplate. Make, model, model year, trim, body, and powertrain distinctions remain available for matching.

Registration-year and model-year meanings remain source-dependent.
Powertrain, emissions, range, and battery facts retain their source context.

Search first; inspect provenance on detail

Use search to identify plausible canonical variants, then fetch the selected record by ID to review its full specification payload and per-field source evidence. This two-step path is more truthful than flattening provenance into a search result.

measured release evidence

Coverage claims carry a date and definition

Evaluate field completeness, source scope, freshness, record grain, and provenance against the dated full release—not against the evaluation bundle alone.

Coverage matrix →

Field, powertrain, market, and model-year completeness.

Data dictionary →

Types, units, applicability, and field caveats.

Source register →

Source classifications, terms, and published URLs.

Release evidence →

Version, dates, manifest, and delivery contract.

Coverage methodology Sources and licences Provenance model

limitations

Know the limits before purchase

Apex is reference data, not regulatory certification, emissions-compliance advice, a consumer vehicle-history report, or a VIN decoder.

WLTP, NEDC, EPA, registration, manufacturer, and derived values must be interpreted according to their documented field and provenance semantics.

Vehicle images, accident history, ownership history, and live telematics are not included.

Apex does not guarantee that every specification exists for every market, model year, or powertrain.

The API is not a substitute for source review where regulatory or financial decisions depend on a field.

next step

Evaluate the data before you buy

Download a representative sample by email, review current coverage, and choose the access model that fits your workload.

Get sample by email View pricing