Datacircle

Best VIN decoder API in 2026

Last updated:

NHTSA, CarsXE and Auto.dev are the best VIN decoder API providers in our benchmark. We benchmarked 4 providers. We list the three we score highest. For each one, we show its top scoring plan, each part of the plan's score and what 1,000 VINs cost. We rank 47 plans by price. API Ninjas's $299 monthly plan is the cheapest paid plan per 1,000 VINs: $0.03. VINquery's $180 pack covers any number of VINs. VINquery's $180 pack costs less to start than API Ninjas's $299 monthly plan.

  1. #1 NHTSA: VIN decoder API

    NHTSA, free

    It returns all 8 key fields we check: Type, Engine, Fuel, Drivetrain, Size and weight, Airbags and belts, Driver assists, Plant.

    Overall score
    86.5
    $ per 1,000
    $0.00
    Price score
    100
    • $ per 1,000 VINs the provider can't decode: $0
    • Plans of this API we rank by price: 47
    • Plans cheaper per 1,000 VINs than this plan: 0
    Data score
    88
    Cost to get started score
    100
    • How you pay: free
    • Least to pay before your first result: $0
    Bundle score
    0
    • Also pays for, from the same budget: the provider's pages don't say
    Performance score
    100
    • This call's median time on 31 October 2026, minus the baseline: 0.049 s, counted as 0.1 s
    • NHTSA, Decode VIN (flat format), the fastest live provider we benchmarked: under 0.1 s, counted as 0.1 s
    • On 31 October 2026, we sent this provider all 20 VINs in our benchmark.
    • This plan scored 0.8778 out of 1 on those 20 VINs. That gives this plan a Data score of 88 out of 100.

  2. #2 CarsXE: VIN decoder API

    CarsXE, $49 monthly, Starter

    It returns 6 of the 8 key fields we check: Type, Engine, Fuel, Drivetrain, Size and weight, Plant.

    Overall score
    79.9
    $ per 1,000
    $24.50
    Price score
    83
    • $ per 1,000 VINs the provider can't decode: $0
    • Plans of this API we rank by price: 47
    • Plans cheaper per 1,000 VINs than this plan: 9
    Data score
    90
    Cost to get started score
    78
    • How you pay: monthly
    • Least to pay before your first result: $49
    Bundle score
    93
    • Also pays for: Specifications (Basic) · International VIN Decoder · Plate Decoder · Vehicle Images and 9 more
    Performance score
    14
    • This call's median time on 31 October 2026, minus the baseline: 2.366 s
    • CarAPI, the fastest provider we benchmarked that answers from a copy: 0.339 s
    • On 31 October 2026, we sent this provider all 20 VINs in our benchmark.
    • This plan scored 0.8994 out of 1 on those 20 VINs. That gives this plan a Data score of 90 out of 100.

  3. #3 Auto.dev: VIN decoder API

    Auto.dev, $299 monthly, Growth

    It returns 4 of the 8 key fields we check: Type, Engine, Drivetrain, Plant.

    Overall score
    54.2
    $ per 1,000
    $2.50
    Price score
    74
    • $ per 1,000 VINs the provider can't decode: the provider's pages don't say
    • Plans of this API we rank by price: 47
    • Plans cheaper per 1,000 VINs than this plan: 7
    Data score
    33
    Cost to get started score
    65
    • How you pay: monthly
    • Least to pay before your first result: $299
    Bundle score
    0
    • Also pays for: nothing else
    Performance score
    100
    • This call's median time on 31 October 2026, minus the baseline: 0.007 s, counted as 0.1 s
    • NHTSA, Decode VIN (flat format), the fastest live provider we benchmarked: under 0.1 s, counted as 0.1 s
    • On 31 October 2026, we sent this provider all 20 VINs in our benchmark.
    • This plan scored 0.3333 out of 1 on those 20 VINs. That gives this plan a Data score of 33 out of 100.

We don't rank 1 other provider we benchmarked: CarAPI. Each CarAPI plan is free or billed yearly. We don't score these plans.

The Data score on VIN decoder APIs

This score, out of 100, shows how much of a vehicle's record a provider's call returns for a VIN. We send each VIN to the provider. For each VIN, we count the parts the provider returned, such as the engine and the drive. We divide the number of parts the provider returned by the number of parts we count for the VIN. We count a part on a VIN when at least one live call returned that part for the VIN. We check a copy against the live calls. We never check a live call against a copy. The one exception is a VIN that fewer than two live calls found. For such a VIN, we count a part when any call returned it. We took each VIN from a dealer's listing of a car. The listing gives the car's year, make and model. We count Year, Make and Model on each VIN. If a value differs from the listing, we count it as missing. A year matches when it is the same number as the listing's. A make or a model matches when one name contains the other. We compare only letters and digits. We don't count a value given again in another unit. We don't count parts the VIN itself spells out, such as its check digit. We also don't count the decode status. We average each provider's scores over all VINs. Each VIN counts the same. A provider that finds no record of a VIN scores 0 on that VIN. Some providers ran on fewer VINs. We compare each of those providers with the others on the VINs it ran on. A provider can't score higher by running only on easy VINs. We lower the score when we test the call on fewer VINs than the benchmark has.

Best GTM APIs