Autodealerdata CIS Automotive API
Official vendor OpenAPI document · agent-readyData EnrichmentCompany DataapiKey35 EndpointsREST
For Agents
Authenticate with API credentials to mint a JWT, then query US automotive market data - vehicle prices, days-to-sell, dealer inventories, regional sales, and market share - for a given brand, model, region, or zip code.
Use for: Get the average sale price of a Toyota Camry in California, Find how many days a Ford F-150 takes to sell on dealer lots, List all dealers in a given zip code, Retrieve monthly sales totals for a brand in a region
Not supported: Does not handle vehicle telemetry, repair instructions, or insurance quotes - use for US automotive market data, pricing, and dealer lookups only.
CIS Automotive (autodealerdata.com) is a market data API for the US automotive retail industry, covering new and used vehicle pricing, days-to-sell, dealer inventories, market share, and historical sales by region. The API uses a JWT workflow - clients authenticate at /getToken with API credentials, then pass the JWT as an argument on every other call. Endpoints are organised by data category (sales data, pricing, premium dealer lookups) and many are gated by plan tier. The data set is sized for analytics teams in dealer groups, lenders, and automotive marketing platforms.
Install Jentic One Beta
Connect the CIS Automotive API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CIS Automotive API, 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.
1
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%2Fautodealerdata.com%2Fautodealerdata" | sh2
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%2Fautodealerdata.com%2Fautodealerdata" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 CIS Automotive API.
Mint a JWT from API credentials via GET or POST /getToken
List regions, brands, and models served by the API via /getRegions, /getBrands, /getModels
Pull pricing analytics - list price, sale price, sale price histograms - for new vehicles
Calculate days-to-sell and days-of-supply for a model in a region
Retrieve regional sales totals and per-day sales by brand via /regionSales and /regionDailySales
Look up dealers by zip code, region, or ID using premium endpoints
Generate sub-user keys with /makeSubUserKey and revoke them with /revokeSubUserKey
Use Cases
Patterns agents use CIS Automotive API for, with concrete tasks.
★ Pricing analytics for a dealer group
Power a dealer-group dashboard that compares the group's asking and selling prices against regional market averages. After minting a JWT at /getToken, the dashboard calls /listPrice and /salePrice for the brand and region of each rooftop, /salePriceHistogram to see how the group's deals fall on the regional curve, and /daysToSell to flag slow-moving inventory. Refreshing once per night keeps the dashboard close to live without exhausting plan quotas.
Mint a JWT, then call /salePrice with brand, model, region for each rooftop and store the result keyed by (rooftop, week)
Lender risk model inputs
An auto lender uses CIS Automotive to feed days-to-sell and market-share signals into its loan-to-value risk model. /daysToSell, /daysSupply, and /modelYearDist provide collateral-velocity inputs, while /regionSales and /salePriceHistogram supply the price distribution the lender uses to value collateral if a loan defaults. The JWT workflow keeps the long-lived API key off lender batch jobs by minting fresh tokens per nightly run.
For each loan, call /daysToSell and /salePrice with the vehicle's brand, model, and region to populate the LTV model
Dealer locator on a marketplace
An automotive marketplace surfaces dealers near the user's zip code by calling the premium /getDealers endpoint with the user's zip and a radius. /getDealersByID then fetches enriched detail (address, phone, brand mix) for each result. Because the data set is plan-gated, the integration must be ready to handle 403 responses from premium endpoints if the account downgrades.
Mint a JWT, then GET /getDealers with the user's zip and a radius to return a list of nearby dealerships
Agent-driven vehicle research
An AI shopping assistant helps a buyer compare a make and model across regions. The agent searches Jentic for the right CIS Automotive operation, calls /salePrice and /daysToSell across two or three regions, and summarises which region offers better value. Through Jentic the JWT lifecycle is managed inside the credential vault - the agent never juggles /getToken calls itself.
Compare /salePrice across the user's home region and one neighbouring region for a target brand and model, then explain the price gap
Key Endpoints
35 endpoints — cis automotive (autodealerdata.
METHOD
PATH
DESCRIPTION
POST
/getToken
Mint a JWT from API credentials
GET
/salePrice
Stats on sale price of new vehicles
GET
/daysToSell
Days a vehicle takes to sell
GET
/daysSupply
Days of supply on dealer lots
GET
/regionSales
Brand sales by region and month
GET
/getDealers
Premium dealer lookup by zip code
GET
/topModels
Top models in a given region
GET
/vehicleHistory
Simple vehicle history report
POST
/getToken
Mint a JWT from API credentials
GET
/salePrice
Stats on sale price of new vehicles
GET
/daysToSell
Days a vehicle takes to sell
GET
/daysSupply
Days of supply on dealer lots
GET
/regionSales
Brand sales by region and month
GET
/getDealers
Premium dealer lookup by zip code
GET
/topModels
Top models in a given region
GET
/vehicleHistory
Simple vehicle history report
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the CIS Automotive API by hand means minting a JWT at /getToken, rotating it before expiry, and mapping the right query across roughly 35 pricing and dealer-lookup endpoints yourself. Through Jentic you install once, import the CIS Automotive API from the API Directory, store the key once, and your agent calls it.
Permission scoping
CIS Automotive carries its lookup targets in query parameters rather than as resource ids in the URL path, so scope your agent to the operations it needs, such as fetching sale price or finding dealers near a zip code. Because you choose the allowed operations, the token-minting call at /getToken is not included unless you add it.
Credential isolation
Your CIS Automotive credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'get a vehicle sale price' or 'find dealers near a zip code', and Jentic returns the matching CIS Automotive operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using CIS Automotive API through Jentic.
What authentication does the CIS Automotive API use?
CIS Automotive issues a JWT from /getToken when called with valid API credentials. Every subsequent endpoint accepts the JWT as a request argument. Through Jentic the API credentials are held in the credential vault, /getToken is called server-side, and only the short-lived JWT flows to the agent.
How do I get the average sale price of a vehicle from the CIS Automotive API?
Mint a JWT at /getToken, then GET /salePrice with the brand, model, and region you care about. The response includes mean, median, and distribution statistics for new-vehicle sale prices in that region.
Which CIS Automotive endpoints are premium?
Endpoints tagged 'Premium' in the spec - /getDealers, /getDealersByRegion, /getDealersByID, /regionSales, /vehicleHistory, /similarSalePrice - require a paid plan. Calls from a free or basic account return a 403; check your plan before relying on these in production.
How do I find dealers in a zip code through Jentic?
Search Jentic for 'find dealers in a zip code' and load the GET /getDealers operation. Execute it with the zip code and a radius - Jentic mints the JWT for you and returns the dealer list. Get started with Jentic One, the self-hosted execution layer.
What are the rate limits for the CIS Automotive API?
CIS Automotive enforces per-plan request quotas managed in the customer dashboard rather than the OpenAPI spec. JWTs are short-lived; the spec recommends caching them rather than calling /getToken on every request to stay within plan limits.
Can I use my RapidAPI keys directly against api.autodealerdata.com?
No. RapidAPI customers must call the API through RapidAPI's gateway, while customers signed up directly authenticate at api.autodealerdata.com using /getToken with their CIS-issued credentials. The two key types are not interchangeable.
Can I limit what my agent is allowed to do with the CIS Automotive API?
Yes. Jentic One is self-hosted, so your own rules decide which CIS Automotive operations and credentials the agent may call. Because this API carries its lookup targets in query parameters rather than in the URL path, you scope the agent to just the operations it needs, such as GET /salePrice for pricing or GET /getDealers for finding dealers near a zip code. Since you choose the allowed operations, the token-minting call at /getToken stays out of the agent's reach unless you add it.
GET STARTED