Data and limits
Where CarScout data comes from, how often it updates, what it leaves out, and the plan and rate limits.
Data sources
| Data | Source | Updates |
|---|---|---|
| Listing counts, average asking prices, mileage, and listings by state | Nationwide dealer listings | Weekly for popular models, monthly for others |
| Recalls and consumer complaints | NHTSA | With each snapshot |
| Fuel economy | EPA | With each snapshot |
| VIN decoding | NHTSA vPIC | On request |
Every market answer carries its snapshotDate. The MCP tools mark a snapshot older than 14 days as stale.
What the data leaves out
- Snapshots have no median price. Use the average: the lowest and highest asking prices are single listings and often outliers.
- Mileage is accurate only to a 50,000-mile band.
- Asking prices aren't sale prices or an appraisal of a specific car.
- Model-year recalls don't show whether a specific car had a recall repaired.
- The public API and tools don't return individual listings. Scouts return listings only to the account that created them.
For how the snapshots are built, see data and methodology.
Plans
The public tools and REST endpoints are free. Account tools need a paid plan: $5 a week, $15 a month, or $99 a year. Each plan includes 3 scouts, and you can add more. For details, see pricing.
Limits
| Limit | Value |
|---|---|
| Public market requests for each IP address | 30 a minute |
| Scouts included in a plan | 3 |
Alerts in one get_alerts page |
50 |
| API keys for each account | 5 |
| Scout checks | About every 24 hours |