The modern JATO Specifications alternative

    JATO tells you what a version could have. VINdata.io tells you what this car has.

    JATO Specifications is built for comparing vehicle versions across the market: standard equipment, available options, packs, prices, colours and trims. VINdata.io starts from one VIN and returns the factory equipment recorded for that specific car — ready for listings, purchase checks and integrations.

    No credit card required · 1 free lookup · Cancel anytime

    JATO Specifications describes vehicles at version level. It standardises how manufacturers describe models, equipment, options and prices so analysts, manufacturers, leasing companies and platforms can compare vehicles consistently across brands and markets. That is valuable when you plan products, build choice lists or compare new-car offers. When you hold a specific used car, the question is different: which options did the factory actually fit to this vehicle? VINdata.io answers that from the VIN. You get the factory option list, codes and descriptions as recorded for the individual car, delivered via website, bulk lookup, REST API or MCP. We do not guess equipment from the model name or engine description.

    JATO Specifications — Market-wide, standardised specification data for comparing vehicle versions across brands, markets and price lists.

    Why teams switch from JATO Specifications

    Built for modern automotive workflows — fast, transparent, and developer-friendly.

    Per vehicle, not per version

    A version-level catalogue shows what was standard or available. A VIN lookup shows the options recorded for the individual car — the detail that matters when you buy, sell or describe a used vehicle.

    Start in minutes

    Create an account, look up a VIN on the website or request API access. No data-licensing project is needed to test the data on your own vehicles.

    Raw factory data via API and MCP

    Structured JSON with option codes and original descriptions, plus an MCP endpoint for Claude, ChatGPT and other AI tools.

    Equipment descriptions in multiple languages

    Request translated equipment descriptions while keeping the original description alongside, so nothing is lost in translation.

    VINdata.io vs JATO Specifications

    Side-by-side feature comparison

    FeatureVINdata.ioJATO Specifications
    Starting pointOne specific VINVehicle version / model range
    Equipment fitted to the individual carFactory-recorded options for the VINNot the core product (version catalogue)
    Standard and optional equipment per versionNot a version catalogue
    Packs and option relationshipsShown as recorded for the carWhere covered
    Factory option codesStandardised definitions
    Standardised equipment categories across brands
    New-car prices, colours and trims per version
    Market coverageMain European brands58 markets, 240 brands
    Technical data (engine, dimensions, EV data)Where available for the VIN
    Bulk lookup of VIN listsVia integration
    REST API and MCP for AI toolsAPI / JATO as a Service
    Self-service sign-upVia JATO sales

    Built for the work you actually do

    01

    Used-car purchase checks

    Look up the VIN before you buy and see which options the car left the factory with — instead of relying on the seller's description or the brochure for the version.

    02

    Listings and sales texts

    Use the recorded equipment list as the basis for your ad, so the text describes this car and not every option the version could have had.

    03

    Import lists and integrations

    Run whole VIN lists through bulk lookup or the API and bring the factory option data into your own system or AI workflow.

    Frequently asked questions

    Is VINdata.io a replacement for JATO Specifications?

    Not for everything. If you need to compare new-car versions, standard equipment, option prices and trims across many markets, JATO is built for that. If you need to know what a specific car was built with, VINdata.io is the more direct tool.

    What is the difference between version data and VIN data?

    Version data describes what a model version offered: standard equipment and available options. VIN data describes the individual car: which options were actually fitted at the factory. Two cars of the same version can have very different equipment.

    Do you standardise equipment into categories like JATO?

    No. We show the factory equipment as recorded, with codes and original descriptions, and we can translate the descriptions. We do not interpret or reclassify equipment, so you see what the factory recorded rather than our guess.

    Do you include new-car prices and colour lists?

    No. VINdata.io does not provide list prices or version catalogues. We focus on the factory data for the individual VIN.

    Can I test it on my own cars?

    Yes. Create a free account and look up your own VINs, or apply for API access to test the API and MCP endpoint.

    Need to know what this car actually has?

    Look up a VIN and see the factory equipment recorded for that specific vehicle.