canonical: https://jentic.com/apis/fleetengine.googleapis.com/fleet-engine

# Google Local Rides and Deliveries API

The Google Fleet Engine Local Rides and Deliveries API manages the vehicles, trips, and delivery tasks behind on-demand ride and last-mile delivery operations. It creates and searches trips, registers and updates vehicles and their attributes, provisions delivery vehicles, and creates and lists delivery tasks individually or in batches. A task can be patched as a delivery progresses, and billable trips can be reported for usage accounting. Access is authorized with Google OAuth 2.0 on the cloud-platform scope.

## For AI agents

Create and search trips, register and update vehicles and delivery vehicles, create and patch delivery tasks, and report billable trips for Google Fleet Engine ride and delivery fleets. Authorized with Google OAuth 2.0.

## Scope

Does not render maps, geocode addresses, or compute driving routes. Use for Fleet Engine ride and delivery fleet operations only.

## Capabilities

- Create on-demand ride trips and search a provider's trips
- Register, update, list, and search vehicles and update their attributes
- Provision delivery vehicles and list them for last-mile fleets
- Create delivery tasks individually or in batches and list them
- Patch a task's state as a delivery progresses
- Report billable trips for usage accounting

## Use cases

### Agent-Driven Dispatch

An AI agent connected through Jentic can run dispatch for a rides-and-deliveries provider without a developer wiring Google OAuth and the provider resource paths. The agent registers a vehicle, searches for available vehicles for a request, and creates the trip, keeping the fleet assigned. Jentic injects the OAuth credential at call time so it never reaches the agent.

Example prompt: Search for available vehicles for a provider, create a trip for the ride request, and confirm the trip was created

### Last-Mile Delivery Task Management

Delivery operators can push a day's stops into Fleet Engine and track them as drivers progress. The agent batch-creates delivery tasks, assigns them against delivery vehicles, and patches each task's state as it is completed. This keeps the operational record current for a last-mile fleet.

Example prompt: Batch-create delivery tasks for a route, then patch a task's state to completed as the driver finishes it

### Fleet Vehicle Registration

Providers onboarding drivers register each vehicle and keep its attributes current. The agent creates a vehicle, updates its attributes, and lists the provider's vehicles to confirm the roster. This keeps the fleet inventory accurate as drivers join and leave.

Example prompt: Create a vehicle for a provider, update its attributes, then list the provider's vehicles to confirm it is registered

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v1/{parent}/trips` | Create a trip |
| POST | `/v1/{parent}/trips:search` | Search trips for a provider |
| POST | `/v1/{parent}/vehicles` | Register a vehicle |
| GET | `/v1/{parent}/vehicles` | List vehicles for a provider |
| POST | `/v1/{parent}/tasks` | Create a delivery task |
| POST | `/v1/{parent}/deliveryVehicles` | Provision a delivery vehicle |
| POST | `/v1/{name}:report` | Report a billable trip |

## Key resources

- **Trips** — Create and search on-demand ride trips for a provider
- **Vehicles** — Create, read, update, delete, list, and search vehicles and update attributes
- **Delivery Vehicles** — Create and list delivery vehicles for last-mile fleets
- **Tasks** — Create tasks individually or in batches, list them, and patch task state
- **Billable Trips** — Report billable trips for usage accounting

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 41 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 56 / 100
  - Developer Experience & Jentic Compatibility: 56 / 100
  - AI-Readiness & Agent Experience: 19 / 100
  - Agent Usability: 94 / 100
  - Security: 63 / 100
  - AI Discoverability: 59 / 100
- **View full report:** https://jentic.com/apis/fleetengine.googleapis.com/fleet-engine/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Fleet Engine by hand means setting up Google OAuth 2.0 on the cloud-platform scope, refreshing tokens, and threading the provider resource name through every path yourself. Through Jentic you install once, import Fleet Engine from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** Fleet Engine puts the provider resource name in the URL path, so a rule can pin your agent to one provider and the operations you pick, such as creating trips and listing vehicles. You choose which operations it may call, so destructive ones like deleting a vehicle are not included unless you add them.
- **Credential handling:** Your Google OAuth 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 'create a trip for an on-demand ride' or 'batch-create delivery tasks', and Jentic returns the matching Fleet Engine operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Detrack** — Real-time last-mile delivery tracking and proof of delivery
- **Track-POD** — Delivery management with routing and electronic proof of delivery
- **Routific** — Route optimization for a fleet of delivery stops
- **Samsara** — Vehicle telematics and driver safety for physical fleets

## FAQ

### What authentication does the Fleet Engine API use?

Per its OpenAPI spec, the Fleet Engine API uses Google OAuth 2.0, with the cloud-platform scope, in either the implicit or authorization-code flow. Through Jentic the credential is stored encrypted by your own instance and injected at call time, so it never reaches the agent.

### Is there a Fleet Engine MCP server?

You don't need an MCP server to give your agent Fleet Engine. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls operations like creating a trip or batch-creating delivery tasks on demand, without loading another server's tool definitions into its context.

### Can I limit what my agent is allowed to do with Fleet Engine?

Yes. Fleet Engine puts the provider resource name in the URL path, so a rule can pin your agent to one provider and the operations you pick, such as creating trips and listing vehicles, so it cannot delete a vehicle unless you add that operation, and every call it makes is logged. This matches a dispatch bot that should assign work without destructive power.

### Can I manage delivery tasks with the Fleet Engine API?

Yes. Create delivery tasks individually or in batches, list them for a provider, and patch each task's state as the delivery progresses. You provision delivery vehicles the tasks are carried out against.

### What are the rate limits for the Fleet Engine API?

The OpenAPI spec does not specify rate limits. Check the Google Maps Platform documentation at https://developers.google.com/maps/documentation/mobility for current Fleet Engine quotas before scaling up dispatch volume.

### How do I dispatch a ride with the Fleet Engine API through Jentic?

Search Jentic for 'create a trip for an on-demand ride', which returns the vehicle search and trip creation operations with their input schemas. The agent finds an available vehicle, creates the trip, and confirms it, with your stored OAuth credential injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.