Skip to main content
POST
Match Score
Takes a shopper intent (a question or short description) and a caller-supplied list of VINs. Returns each VIN’s match score against the intent, an in_stock flag, and an optional price_fit against price_min / price_max. The vehicles are not re-encoded; Vault reuses each one’s already-stored vector for the comparison. Use this endpoint when an LLM holds a shortlist from a prior turn (a /v2/search result, a hand-picked set, a previously-shown group) and wants to re-rank just that shortlist as the shopper adds a constraint or shifts intent. For ranking against a dealer’s full inventory, use POST /v2/search instead. Scores fall in the natural-language low range (typically 0.20 to 0.40), which is expected for question-vector versus vehicle-vector comparisons. Treat the relative ranking, not the absolute value, as the signal. For a worked end-to-end example showing /v2/search and /v2/match-score together in an agentic flow, see the Semantic Search guide.

Body

application/json
api_key
string
required
intent
string
required
vins
string[]
required
dealership_id
integer | null
price_min
integer | null
price_max
integer | null

Response

Successful Response