Kelley Blue Book Valuation Scraper

---

🎯 What this scrapes

Kelley Blue Book publishes the industry-reference valuation numbers used in negotiation, trade-in, and financing conversations — Fair Purchase Price, a Fair Market Price range, and original MSRP, all varying per trim within a single make/model/year. This Actor pulls those numbers straight from KBB's own page data for a list of vehicles you supply, one row per trim, so you never have to hand-check a page one vehicle at a time.

🔥 Features

• 🚗 Per-trim pricing — Fair Purchase Price, Fair Market Price low/high, and original MSRP, one row per trim.
• 📋 Batch up to 50 vehicles — structured make/model/year entries or raw KBB-shaped slug strings, mixed freely in one run.
• 🔁 We retry with backoff + rotate browser fingerprints — curl-cffi presents a real browser handshake and retries transient 429/5xx so a large batch finishes instead of dying midway.
• 🧱 One vehicle's miss never sinks the run — a page that can't be parsed is logged and skipped; every other vehicle in the batch still comes back.
• 🧊 Clean, typed rows — Pydantic-validated, ISO-8601 timestamps, stable schema. Export JSON / CSV / Excel straight from the Apify Console.
• 💰 You pay only for results that land. No data → no charge (only the small actor-start warm-up fee).

💡 Use cases

• Used-car dealers pricing trade-ins and lot inventory against KBB's reference numbers, at scale.
• Auto-finance and insurance analysts who need KBB valuation figures across many make/model/year combinations for underwriting or risk models.
• Pricing-intelligence tools that fold KBB's authoritative numbers into a broader vehicle-pricing pipeline alongside marketplace listings.

⚙️ How to use it

1. Click Try for free at the top of the Store listing.
2. Add one or more entries under Vehicles — make, model, and year (e.g. {"make": "honda", "model": "civic", "year": 2020}), or supply raw KBB-shaped Vehicle slugs (e.g. "toyota/camry/2021").
3. Leave Proxy configuration on its default — standard Apify Proxy is sufficient for this target.
4. Run the Actor and grab the dataset (JSON, CSV, or Excel) from the Console when it finishes.

📥 Input

Field	Type	Default	Description
vehicles	array of objects	[{"make": "honda", "model": "civic", "year": 2020}]	Structured make/model/year triples, up to 50.
vehicleSlugs	array of strings	[]	Optional "<make>/<model>/<year>" slug strings, parsed and appended to vehicles. Combined total capped at 50.
proxyConfiguration	object	{"useApifyProxy": true}	Apify Proxy configuration. Standard (non-residential) proxy is sufficient.

{
  "vehicles": [
    { "make": "honda", "model": "civic", "year": 2020 },
    { "make": "toyota", "model": "camry", "year": 2021 }
  ],
  "vehicleSlugs": [],
  "proxyConfiguration": { "useApifyProxy": true }
}

📤 Output

One row per trim.

{
  "make": "honda",
  "model": "civic",
  "year": 2020,
  "trim": "EX Sedan",
  "fair_purchase_price": 21453.0,
  "fair_market_price_low": 20100.0,
  "fair_market_price_high": 22800.0,
  "original_msrp": 23650.0,
  "offer_price": 20100.0,
  "offer_max_price": 22800.0,
  "currency": "USD",
  "source_url": "https://www.kbb.com/honda/civic/2020/",
  "scraped_at": "2026-09-15T12:00:00.000Z"
}

💰 Pricing

Pay-per-event — you pay for results that land, not per page attempted.

Event	Price	Trigger
Actor start	$0.20	Once per run
Result row	$0.003	Per trim row pushed to the dataset

Effective cost: $3.20 / 1 000 results ($0.20 flat start + 1 000 x $0.003 per row). A typical 10-vehicle run (~4 trims each, ~40 rows) lands around $0.32 total.

🚧 Limitations

• v1 covers the public /<make>/<model>/<year>/ valuation page only — no login-gated features (saved vehicles, price alerts, dealer quotes).
• No VIN-specific / condition-adjusted / mileage-adjusted trade-in valuations — that's KBB's interactive "value your car" flow, out of scope here.
• No listing or dealer-inventory data — this Actor emits valuation numbers only.
• www.kbb.com (US) only — no other KBB-branded regional sites.

❓ FAQ

Does this need a KBB account or API key? No — every field comes from KBB's own public valuation pages.

What if a make/model/year isn't in KBB's catalog? That vehicle is skipped and logged; the run still finishes successfully with rows for every vehicle that did resolve.

Can I mix structured vehicles and slug strings in one run? Yes — vehicles and vehicleSlugs are merged into one list before any fetch begins.

🙋 Your feedback

Found a bug or want a feature? Open an issue via apify.com/DevilScrapes — we read every report.