Edmunds API

Name: Edmunds API API
Brand: Edmunds API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentCompany DataapiKey36 EndpointsREST

For Agents

Look up vehicle specifications, market pricing, and dealer information by make, model, year, VIN, or style. Useful for car-research agents and pricing tools.

Quickstart

Get started with Edmunds API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"get the true market value of a vehicle"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Edmunds API API.

Look up car makes, models, years, and styles by ID, slug, or filter

Decode a VIN or squish-VIN into the underlying year, make, model, and style

Retrieve True Market Value (TMV) for new, used, certified, and typically-equipped vehicles by style and ZIP code

Pull True Cost to Own (TCO) data by make, model, and style across the five-year ownership window

GET STARTED

Start building with Edmunds API API

Explore with Jentic

View OpenAPI Document

Use for: I need to look up the True Market Value of a 2022 Honda Civic in ZIP 90210, Decode this VIN and tell me the year, make, model, and trim, Find dealerships near a ZIP code that sell a specific make, Get the five-year True Cost to Own for a Toyota RAV4

Not supported: Does not handle vehicle purchase transactions, financing applications, insurance quotes, or vehicle title transfers — use for vehicle data, pricing, dealer lookups, and reviews only.

Jentic publishes the only available OpenAPI document for Edmunds API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Edmunds API, keeping it validated and agent-ready. The Edmunds API exposes the dataset behind Edmunds.com — vehicle specifications, True Market Value (TMV) and True Cost to Own (TCO) pricing, dealer information, vehicle photos, and dealer ratings and reviews. The 36 endpoints cover make, model, year, style, engine, transmission, colour, equipment, VIN decoding, new-and-used pricing, dealership lookups, and review submission. Authentication is a query-parameter API key, so it is straightforward to call from server-side automations, vehicle-research chat agents, or pricing tools.

Use Cases

Patterns agents use Edmunds API API for, with concrete tasks.

★ Car-research conversational agent

A consumer-facing chat agent helps shoppers narrow down a vehicle by asking about budget, body style, and brand preferences. The agent calls the Edmunds API to list makes and models, fetch styles for a chosen model year, and quote the TMV and TCO for a candidate trim in the user's ZIP code. Because every Edmunds operation is callable with a single API key in the query string, the agent can run end-to-end research without OAuth handshakes.

Given a user-stated budget and ZIP code, list candidate styles via /api/vehicle/v3/styles and return the TMV from /v1/api/tmv/tmvservice/calculatenewtmv for each candidate.

VIN decoding and pricing for dealer tools

A dealer or marketplace tool accepts a VIN from a trade-in form and needs to derive the vehicle's year, make, model, and trim, then quote a fair market price. The Edmunds VIN decode endpoint resolves the VIN to a styleId, after which the TMV endpoints return new, used, certified, or typically-equipped pricing for that style. The combined flow drives consistent valuations across a dealer network.

Call GET /api/vehicle/v2/vins/{vin} to retrieve the styleId, then GET /v1/api/tmv/tmvservice/calculateusedtmv with that styleId and the customer's ZIP to return a used-vehicle price.

Dealer discovery and reputation lookup

A car-buying assistant needs to surface dealerships that carry a chosen make, then show their reputation before recommending a visit. The Edmunds dealer endpoints list dealerships by make and franchise, and the dealer ratings and reviews endpoints return aggregate scores. The assistant can also submit a new review on behalf of an authenticated buyer.

List dealers for a make via /api/dealer/v5/dealership/{dealershipId}/franchises, then call /v1/api/drrrepository/getdrrbydealerid for each to return reputation scores.

Edmunds API as an agent tool through Jentic

An AI agent platform exposes vehicle research as a callable tool. Through Jentic, the agent searches by intent ('look up car market value'), receives the matching Edmunds operation with its input schema, and executes the request. The agent never sees the raw API key, which Jentic injects at execution time.

Search Jentic for 'get the true market value of a vehicle', load the operation schema, and execute the call for a given make, model, year, and ZIP code.

Key Endpoints

36 endpoints — jentic publishes the only available openapi specification for edmunds api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/api/vehicle/v3/makes

List car makes

GET

/api/vehicle/v3/styles

List vehicle styles

GET

/api/vehicle/v2/vins/{vin}

Decode a VIN to its style

GET

/v1/api/tmv/tmvservice/calculatenewtmv

Get True Market Value for a new vehicle

GET

/v1/api/tmv/tmvservice/calculateusedtmv

Get True Market Value for a used vehicle

GET

/v1/api/tco/getmakeswithtcodata

List makes with True Cost to Own data

GET

/api/media/v2/{make}/{model}/{year}/photos

Get vehicle photos

GET

/api/vehicle/v3/makes

List car makes

GET

/api/vehicle/v3/styles

List vehicle styles

GET

/api/vehicle/v2/vins/{vin}

Decode a VIN to its style

GET

/v1/api/tmv/tmvservice/calculatenewtmv

Get True Market Value for a new vehicle

GET

/v1/api/tmv/tmvservice/calculateusedtmv

Get True Market Value for a used vehicle

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Edmunds api_key query parameter is stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped execution access only — Jentic injects the key into outgoing requests so the raw secret never enters the agent's context.

Intent-based discovery

Agents search Jentic by intent — for example 'decode a VIN' or 'get the market value of a used car' — and Jentic returns the matching Edmunds operation along with its input schema, so the agent can call the right endpoint without reading 36 specs by hand.

Time to first call

Direct integration: 2-3 days to wire up the api_key, model the responses, and add caching. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

NHTSA Vehicle API

NHTSA offers free public VIN decoding, recall, and complaint data, without TMV pricing or dealer information.

Choose NHTSA when the agent only needs free VIN decoding or safety/recall data and does not require Edmunds' commercial pricing dataset.

Complementary

Marketstack API

Marketstack provides equity-market pricing data — useful when an automotive workflow also tracks public auto-maker financials.

Pair with Edmunds when the agent's workflow combines vehicle pricing research with auto-maker stock or sector data.

Complementary

Twilio API

Twilio sends SMS notifications to buyers once a vehicle valuation or dealer match is ready.

Use alongside Edmunds in a car-shopping assistant to message users when a price quote, recall, or dealer match is generated.

FAQs

Specific to using Edmunds API API through Jentic.

Why is there no official OpenAPI spec for Edmunds API?

Edmunds does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Edmunds API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Edmunds API use?

Edmunds uses an API key passed as the api_key query parameter on every request. Jentic stores the key encrypted in its vault and injects it at execution time so the agent never receives the raw secret.

Can I decode a VIN with the Edmunds API?

Yes. GET /api/vehicle/v2/vins/{vin} decodes a full VIN, and GET /api/vehicle/v2/squishvins/{squishVin} decodes a 10-character squish VIN, returning the year, make, model, and styleId.

How do I get True Market Value pricing through Jentic?

Run pip install jentic, search Jentic for 'get the true market value of a new car', load the schema for /v1/api/tmv/tmvservice/calculatenewtmv, and execute with the styleId and ZIP code. Jentic returns the price payload for the agent to use.

What are the rate limits for the Edmunds API?

Rate limits are not declared in the OpenAPI spec and depend on the API key tier issued by Edmunds. Build retries with exponential backoff and cache lookups of static reference data such as makes and models to reduce call volume.

Can I find dealers and read their reviews with this API?

Yes. The dealer endpoints list dealerships and their franchises, and the dealer ratings and reviews endpoint returns scores by dealer ID. There is also a POST /api/dealerreviews/v2 endpoint to submit a new review.