Vehicle API
The Vehicle API by Edmunds provides comprehensive access to automotive datasets covering vehicle makes, models, trims, specs, media, pricing (TMV), incentives, dealer information, and reviews. Enables developers to build automotive shopping tools, vehicle configurators, and consumer research applications.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Vehicle API the way a machine reads it — 53 machine-readable artifacts across 7 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Vehicle API scores 58.0/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Vehicle API
Each block below is one kind of artifact we hold for Vehicle API. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 7
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Vehicle API Inventory API
Dealer vehicle inventory
Vehicle API Makes API
Vehicle manufacturer make data
Vehicle API Media API
Vehicle photos and videos
Vehicle API Models API
Vehicle model information
Vehicle API Pricing API
True Market Value pricing data
Vehicle API Specs API
Vehicle technical specifications
Vehicle API Styles API
Vehicle trim and style configurations
Scroll within the panel for all 7 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Vehicle API (Edmunds)
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Vehicle Api Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Vehicle Api Finops
FINOPSFeatures 6
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Vehicle Make and Model Data
Comprehensive database of vehicle makes, models, and trim levels with OEM specifications, features, and configuration options.
True Market Value Pricing
Edmunds TMV pricing data including new vehicle suggested retail, invoice prices, and used vehicle values by condition and mileage.
Vehicle Media
Photo and video assets for vehicle makes, models, and trims including exterior, interior, color swatch, and 360-degree images.
Dealer Inventory
Real-time dealer inventory search with make, model, year, zip code, radius, and price range filtering.
Incentives and Rebates
Manufacturer incentives, rebates, financing offers, and lease programs by vehicle, region, and customer type.
Vehicle Reviews and Ratings
Edmunds editorial reviews and consumer ratings for vehicle models including performance, comfort, value, and reliability scores.
Spectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Vehicle API API Rules
SPECTRALVehicle API API Rules
SPECTRALJSON Schema 8
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
InventoryItem
JSON SCHEMAMake
JSON SCHEMAModel
JSON SCHEMAModelYear
JSON SCHEMAPhoto
JSON SCHEMAPriceResponse
JSON SCHEMAStylePrice
JSON SCHEMAStyle
JSON SCHEMAScroll within the panel for all 8 ·
JSON Structure 8
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Vehicle Api Inventory Item Structure
JSON STRUCTUREVehicle Api Make Structure
JSON STRUCTUREVehicle Api Model Structure
JSON STRUCTUREVehicle Api Model Year Structure
JSON STRUCTUREVehicle Api Photo Structure
JSON STRUCTUREVehicle Api Price Response Structure
JSON STRUCTUREVehicle Api Style Price Structure
JSON STRUCTUREVehicle Api Style Structure
JSON STRUCTUREScroll within the panel for all 8 ·
Examples 8
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Vehicle Api Make Example
EXAMPLEVehicle Api Model Example
EXAMPLEVehicle Api Photo Example
EXAMPLEVehicle Api Style Example
EXAMPLEScroll within the panel for all 8 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 4
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Automotive Shopping Tools
Build vehicle search and comparison tools that let consumers filter by make, model, year, price, and features with TMV pricing guidance.
Dealer Management Systems
Power dealer websites and CRM systems with accurate vehicle specs, pricing, and inventory data synced from Edmunds.
Vehicle Configurator
Enable consumers to build and price vehicles with available trims, packages, options, and colors with live pricing calculations.
Used Car Valuation
Integrate used vehicle pricing into trade-in calculators, appraisal tools, and consumer value estimators using TMV data.
Integrations 3
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
AutoTrader
Cross-reference vehicle listings with AutoTrader inventory using Edmunds vehicle identifiers and specs for consistent data.
Cars.com
Combine Edmunds vehicle data with Cars.com listings for enriched consumer shopping experiences.
Dealer CRM Systems
Integrate vehicle specs and pricing into Salesforce, CDK, and Reynolds and Reynolds dealer management systems.
Resources
Every other property we hold for Vehicle API — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/vehicle-api · machine-readable index on apis.io