canonical: https://jentic.com/apis/smartcar.com/smartcar

# Smartcar API

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.

## For AI agents

Programmatically list user vehicles, get vehicle info. Covers 21 operations with basic, oauth2 authentication.

## Scope

Does not handle payments, communications, or crm - use for maps and geolocation only.

## Capabilities

- 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

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'list user vehicles', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| 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 |

## Key resources

- **Vehicles** — Vehicle data and information
- **Control** — Vehicle control commands
- **EV** — Electric vehicle specific endpoints
- **Users** — User and connection management
- **Webhooks** — Webhook subscriptions for vehicle events

## Why Jentic

- **Setup:** Wiring Smartcar by hand means running its OAuth2 authorization-code flow, using basic auth for token exchange against api.smartcar.com, and managing retries yourself. Through Jentic you install once, import the Smartcar API from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** Smartcar puts the vehicle id in the URL path (/vehicles/{vehicleId}/...), so a rule can pin your agent to one vehicle: it can read that vehicle's location, odometer, fuel, and tire pressure and nothing else. You choose the operations it may call, so only the reads you grant are available.
- **Credential handling:** Your Smartcar credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get a vehicle's location' or 'read the odometer', and Jentic returns the matching Smartcar operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Here** — Alternative maps geolocation API
- **Tomtom** — Alternative maps geolocation API
- **Googleapis** — Complementary maps geolocation API

## FAQ

### What authentication does the Smartcar API use?

The Smartcar API uses basic, oauth2 authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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.

### Can I limit what my agent is allowed to do with the Smartcar API?

Yes. Jentic One runs self-hosted, so your own rules decide which Smartcar operations and credentials the agent may use. Because Smartcar puts the vehicle id in the URL path (/vehicles/{vehicleId}/...), you can pin the agent to a single vehicle and grant only specific reads, such as GET /vehicles/{vehicleId}/location, /odometer, /fuel, or /tires/pressure, while withholding everything else. Any operation you do not grant is simply unavailable to the agent.