CarsXE Vehicle Data API

What's the difference between the v1 and v2 plate decoder endpoints?

GET /v1/plate-decoder is the legacy endpoint that takes plate and state as query parameters. POST /v2/plate-decoder is the newer flow that accepts a JSON body and supports a richer parameter set. New integrations should default to v2; v1 remains for backwards compatibility.

Can CarsXE decode VINs registered outside the United States?

Yes. GET /v1/international-vin-decoder is dedicated to non-US VINs and returns make, model, year, and trim details for international registrations. Use GET /v1/specifications for US-registered VINs where the standard specification dataset applies.

How do I extract a VIN from a photo with CarsXE?

Submit the image to POST /v1/vin-ocr; the response contains the parsed 17-character VIN string. Pass that VIN into GET /v1/specifications, GET /v1/vehicle-recalls, or GET /v1/history to chain the OCR result into a full vehicle intelligence workflow.

What are the rate limits for the CarsXE API?

The OpenAPI specification does not declare numeric rate limits. CarsXE applies per-key throttling at its gateway based on plan tier; if you receive 429 responses, slow concurrency and check the dashboard at https://api.carsxe.com/docs for the limits attached to your account.

How do I value a vehicle through Jentic?

Run `pip install jentic`, then use Jentic's search to find the market-value operation with the query "get vehicle market value", load the schema, and execute with `{"vin": "1HGCM82633A123456"}`. Jentic posts to /v2/market-value with your CarsXE key from the vault and returns the estimated value as structured output.

Does CarsXE return vehicle images?

Yes. GET /v1/images takes a VIN and returns a set of image URLs for that vehicle, useful for listing pages or condition reporting when seller-supplied photos are missing or low quality.

Can I limit what my agent is allowed to do with the CarsXE Vehicle Data API?

Yes. Because CarsXE routes each lookup by its own path, your self-hosted Jentic One instance lets you scope access per operation, and your own rules decide which endpoints and credentials the agent may use. You can allow only the calls you need, such as VIN specifications via GET /v1/specifications or market value via POST /v2/market-value, while leaving plate decoding and VIN OCR out of the allowed set. The agent can invoke only the operations you permit, and your CarsXE key is injected at execution time rather than exposed to the model.