canonical: https://jentic.com/apis/carspecsapi.com/carspecsapi # CarSpecsAPI The CarSpecsAPI API turns a VIN or a make-model query into structured car specifications, covering more than 70,000 trims from 1945 to the present. It organises data as a hierarchy of makes, models, generations, and trims, with up to 76 specification fields recorded per trim. A VIN decoder resolves a raw vehicle identification number to its matching trim, and a database export returns the whole dataset in a single request. Responses are JSON wrapped in a success, data, and meta envelope. ## For AI agents Decode a VIN or walk more than 70,000 car trims from 1945 to today, returning up to 76 specification fields per trim across make, model, generation, and trim levels. Serves JSON over REST with an API key passed in the X-API-Key header. ## Scope Does not handle vehicle pricing, dealer inventory, or ownership history. Use for car specification lookups and VIN decoding only. ## Capabilities - Decode a VIN into its make, model, generation, trim, and specification set - Look up every specification field recorded for a single trim, up to 76 fields per trim - Walk the vehicle hierarchy from make to model to generation to trim - Retrieve the models and generations produced for a manufacturer since 1945 - List the full set of car makes the database covers - Download the entire 70,000-trim specifications database in a single request ## Use cases ### Agent-Driven Vehicle Lookup An AI assistant that answers car questions can call CarSpecsAPI through Jentic to turn a VIN or a make-model query into structured specifications. The agent decodes the VIN, walks to the matching trim, and reads back engine, dimension, and performance fields without the developer wiring the X-API-Key header or the make-model-generation-trim hierarchy by hand. Jentic returns the matching operation and its input schema so the agent calls the right lookup directly. Example prompt: Decode the VIN 1HGCM82633A004352, follow it to the matching trim, and return the engine displacement and horsepower ### VIN Decoding for Used-Car Tools Dealer and marketplace tools that start from a vehicle identification number can decode it into a precise make, model, generation, and trim before pricing or listing the car. The decode operation accepts a VIN and returns the resolved trim together with its specification fields, so a used-car workflow never has to ask the seller to type the exact trim name. Example prompt: Decode a batch of VINs and attach the resolved trim name and body style to each vehicle record ### Enriching Vehicle Listings with Specifications A classifieds or inventory system can enrich a bare listing with a full specification record by resolving the vehicle to its trim and reading the trim's fields. CarSpecsAPI returns up to 76 fields per trim, covering engine, dimensions, and performance, so a listing page can show complete specs rather than free-text the seller entered. Example prompt: Look up the trim id for a listed vehicle and populate its horsepower, fuel type, and dimensions ### Offline Specifications Database Sync An application that needs low-latency or offline access to vehicle data can pull the entire dataset in one call and load it locally instead of paging through the hierarchy at request time. The database export returns every make, model, generation, and trim, which a service then refreshes on its own schedule. Example prompt: Download the full specifications database and load it into a local store for offline trim lookups ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/v2/cars/makes` | List all car makes | | GET | `/v2/cars/makes/{makeId}/models` | List models for a make | | GET | `/v2/cars/models/{modelId}/generations` | List generations for a model | | GET | `/v2/cars/generations/{generationId}/trims` | List trims for a generation | | GET | `/v2/cars/trims/{trimId}` | Get a trim's full specifications | | POST | `/v2/vin-decoder/decode` | Decode a VIN into make, model, generation, and trim | | GET | `/v2/cars/download-database` | Download the full specifications database | ## Key resources - **Makes** — List the manufacturers the database covers and drill into the models for a make. - **Models and Generations** — Browse the models of a make and the generations produced for each model. - **Trims** — Read the full specification record for a trim, up to 76 fields covering engine, dimensions, and performance. - **VIN Decoder** — Resolve a vehicle identification number to its matching make, model, generation, and trim. - **Database Download** — Export the complete specifications database in a single request. ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 72 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 100 / 100 - Developer Experience & Jentic Compatibility: 72 / 100 - AI-Readiness & Agent Experience: 57 / 100 - Agent Usability: 94 / 100 - Security: 50 / 100 - AI Discoverability: 100 / 100 - **View full report:** https://jentic.com/apis/carspecsapi.com/carspecsapi/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring CarSpecsAPI by hand means setting the X-API-Key header on every call, unwrapping the success, data, and meta response envelope, and tracking the quota reset yourself. Through Jentic you install once, import CarSpecsAPI from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** CarSpecsAPI puts each resource id in the URL path, such as the trim id in the trim-lookup route, so a rule can bound your agent to the specific lookup operations it needs. You choose which operations it may call, so the full-database export is not included unless you add it. - **Credential handling:** Your CarSpecsAPI key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'decode a VIN' or 'look up a trim's specifications', and Jentic returns the matching CarSpecsAPI operation with its input schema so the agent calls the right endpoint without reading the reference docs. ## Related APIs - **Auto.dev Vehicle Data API** — Also decodes VINs and US plates and returns vehicle specs, listings, and recalls. - **CarAPI.dev Automotive Data API** — Decodes VINs and adds theft-record checks, mileage history, and multi-country valuation. - **CarsXE Vehicle Data API** — Decodes VINs and plates internationally and adds images, history, and VIN OCR. - **CIS Automotive API** — Adds US market pricing, days-to-sell, and dealer inventory data for a vehicle. ## FAQ ### What authentication does the CarSpecsAPI use? The CarSpecsAPI authenticates with an API key sent in the X-API-Key header on every request, per its OpenAPI spec. Through Jentic the key is stored once, encrypted, by your own Jentic One instance and injected at call time, so it never enters the agent's prompt or logs. ### Is there a CarSpecsAPI MCP server? You don't need an MCP server to give your agent the CarSpecsAPI. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent can decode VINs and read trim specifications straight away. ### Can I limit what my agent is allowed to do with the CarSpecsAPI? Yes. Write a rule that allows just the lookup operations your agent needs, such as decoding VINs and reading trim specifications, so it can answer vehicle questions but cannot trigger the full-database export. Every call it makes is logged. ### Can I decode a VIN with the CarSpecsAPI? Yes. The decode operation accepts a vehicle identification number and returns the resolved make, model, generation, and trim along with that trim's specification fields, so an agent can go from a raw VIN to full specs in one call. ### What are the rate limits for the CarSpecsAPI? CarSpecsAPI's free tier allows 100 requests per day, resetting at midnight UTC, and counted responses carry X-RateLimit headers showing your remaining quota. Check the CarSpecsAPI documentation for higher paid tiers. ### How do I decode a VIN with the CarSpecsAPI through Jentic? Search Jentic for an intent like 'decode a VIN and return car specifications' and it returns the CarSpecsAPI decode operation with its input schema, so your agent sends the VIN and reads back the trim. To run it on your own infrastructure, install Jentic One from its GitHub repo.