CarsXE
for LuumenAI
Vehicle data lookups by VIN or plate, and fleet-wide recall batches
Connect CarsXE and the agent can look up a vehicle the way your team does: decode a VIN into specifications, check recalls, pull title and salvage history, estimate market value, or read a license plate from an image. When you need to check a whole fleet, it submits a recall batch of up to 10,000 VINs as an approved step. Authentication is by API key.
The CarsXE toolbox
12 tools: 11 read, 1 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadCheck Lien and Theft RecordsRetrieve reportable US lien and theft events for a VIN.
- ReadDecode License PlateLook up vehicle identity from a license plate using CarsXE's current global v2 decoder.
- ReadDecode OBD CodeTranslate an OBD-II diagnostic trouble code into a readable diagnosis.
- ReadGet Vehicle Market ValueEstimate wholesale, retail, and trade-in values for a VIN using CarsXE's current v2 valuation, optionally adjusted for state, mileage, and condition.
- ReadGet Recall BatchMake exactly one read request for a CarsXE recall batch.
- ReadGet Vehicle HistoryRetrieve title, brand, junk/salvage, insurance, VIN-change, and historical title records for a VIN.
- ReadGet Vehicle ImagesFind up to 10 vehicle photos by make and model, with optional year, trim, angle, image type, size, color, quality, transparency, and license filters.
- ReadGet Vehicle RecallsFind safety recall campaigns either for one VIN or for a year, make, and model.
- ReadGet Vehicle SpecificationsDecode a 17-character VIN into vehicle identity, specifications, equipment, colors, and warranty data.
- ReadGet Year Make Model DataLook up detailed vehicle and trim information by year, make, and model without a VIN.
- ReadRecognize License PlateAnalyze a publicly accessible vehicle image and return license-plate candidates, regions, confidence, bounding boxes, and detected vehicle details.
- WriteSubmit Recall BatchCreate one asynchronous CarsXE recall-check batch for 1 to 10,000 VIN entries. Approval by default
One prompt, start to finish
What a governed CarsXE run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — submit recall batch — is shown as a plan and requires approval by default. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to CarsXE — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
GitHubRepos, actions, and runbook code as context and as actions.
GitLabMerge requests and pipelines proposed, triggered, and rolled back.
BitbucketRead commits, diffs, and branches in Bitbucket, then open the fix as a held write.
Azure DevOpsAzure DevOps repos and pipelines as context — and as approved actions.Put CarsXE to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.