Install Jentic One Beta

Connect the CarSpecsAPI to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CarSpecsAPI, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcarspecsapi.com%2Fcarspecsapi" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcarspecsapi.com%2Fcarspecsapi" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with CarSpecsAPI API.

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

GET STARTED

Start building with CarSpecsAPI API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use CarSpecsAPI API for, with concrete tasks.

★ 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.

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.

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.

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.

Download the full specifications database and load it into a local store for offline trim lookups

Key Endpoints

7 endpoints — 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.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using CarSpecsAPI API through Jentic.

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.

CarSpecsAPI

AI ReadinessAI-Aware (A-)72/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentData TransformationapiKey7 EndpointsREST

For 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.

Use for: Decode this VIN and return the trim and engine specifications, Look up the full specifications for a specific trim id, List every car make available in the database, Find all models built by a given manufacturer

Not supported: Does not handle vehicle pricing, dealer inventory, or ownership history. Use for car specification lookups and VIN decoding only.

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: A-Signals: 4

14%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: CSignals: 4

77%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the CarSpecsAPI to your agent

Capabilities

Start building with CarSpecsAPI API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

CarSpecsAPI

Jentic AI Readiness Score

CarSpecsAPI

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness