Smartcar API
✓ Official Vendor SpecMaps GeolocationMappingbasic, oauth221 EndpointsREST
For Agents
Programmatically list user vehicles, get vehicle info. Covers 21 operations with basic, oauth2 authentication.
Use for: I need to user vehicles, I want to vehicle info, Search for vin, Find all odometer
Not supported: Does not handle payments, communications, or crm — use for maps and geolocation only.
Lock and unlock vehicles and get data like odometer reading and location. Works on most new cars. Smartcar provides a unified API to read vehicle data and send commands to vehicles across brands. The API exposes 21 endpoints secured with basic, oauth2 authentication.
Install Jentic One Beta
Connect the Smartcar API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Smartcar API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Smartcar API.
List user vehicles
Get vehicle info
Integrate Smartcar API into automated workflows
Query and filter Smartcar API records by parameters
Monitor Smartcar API operational status and events
Use Cases
Patterns agents use Smartcar API for, with concrete tasks.
★ Maps and Geolocation Operations
Use the Smartcar API to perform maps geolocation operations programmatically. The API provides 21 endpoints covering core functionality including list user vehicles, get vehicle info, get vin.
Call GET /vehicles to list user vehicles
Automated Vehicles Management
Automate vehicles operations by combining multiple Smartcar API endpoints. Agents can get vehicle info and then get vin in a single workflow.
Call GET /vehicles/{vehicleId} to get vehicle info, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Smartcar API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle basic, oauth2 tokens manually.
Search Jentic for 'list user vehicles', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
21 endpoints — lock and unlock vehicles and get data like odometer reading and location.
METHOD
PATH
DESCRIPTION
GET
/vehicles
List user vehicles
GET
/vehicles/{vehicleId}
Get vehicle info
GET
/vehicles/{vehicleId}/vin
Get VIN
GET
/vehicles/{vehicleId}/odometer
Get odometer
GET
/vehicles/{vehicleId}/location
Get location
GET
/vehicles/{vehicleId}/fuel
Get fuel tank level
GET
/vehicles/{vehicleId}/tires/pressure
Get tire pressure
GET
/vehicles/{vehicleId}/engine/oil
Get engine oil life
GET
/vehicles
List user vehicles
GET
/vehicles/{vehicleId}
Get vehicle info
GET
/vehicles/{vehicleId}/vin
Get VIN
GET
/vehicles/{vehicleId}/odometer
Get odometer
GET
/vehicles/{vehicleId}/location
Get location
GET
/vehicles/{vehicleId}/fuel
Get fuel tank level
GET
/vehicles/{vehicleId}/tires/pressure
Get tire pressure
GET
/vehicles/{vehicleId}/engine/oil
Get engine oil life
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Smartcar API basic, oauth2 credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'list user vehicles') and Jentic returns the matching Smartcar API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Smartcar API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Smartcar API through Jentic.
What authentication does the Smartcar API use?
The Smartcar API uses basic, oauth2 authentication. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.
Can I list user vehicles with the Smartcar API?
Yes. Use the GET /vehicles endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Smartcar API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I list user vehicles through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'list user vehicles'. Jentic returns the matching Smartcar API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the Smartcar API have?
The Smartcar API exposes 21 endpoints covering vehicles, control, ev operations.
GET STARTED