Contact Cox Automotive (parent company of KBB) through the developer/partner inquiry process — KBB valuations are not available via a self-serve public API and require a commercial licensing agreement
During the partnership process, specify your use case (dealer retail display, consumer-facing tool, internal analytics, etc.) as access tiers and data fields are determined by contractual agreement
Once approved, receive API credentials and documentation under NDA; implement OAuth 2.0 or API key authentication as specified in the partner documentation
Query vehicle values by providing year, make, model, trim, mileage, condition, and ZIP code — all significantly affect the returned valuation; the API returns trade-in, private party, and/or suggested retail values depending on your licensed data set
Comply with KBB's display guidelines and attribution requirements (logo, disclaimers) which are contractually mandated whenever KBB values are shown to end users
Known gotchas
Displaying KBB valuations without the required branding and disclaimers violates the license agreement and can result in access termination; review the usage guidelines before building any UI
Valuations are region-specific and require a valid US ZIP code; results for the same vehicle can vary significantly by geography so do not cache a value obtained with one ZIP and display it for a user in a different region
The API is not intended for bulk scraping or competitive benchmarking; rate limits and terms of service prohibit using the data to build a competing valuation product — ensure your use case is clearly within the licensed scope
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp