canonical: https://jentic.com/apis/fleetwire.io/fleetwire

# Fleetwire API

The Fleetwire API runs a vehicle rental operation end to end, covering the listings a company rents, their availability and daily pricing, the customers who book them, and the bookings themselves. It quotes a trip, tracks a booking through its status, and records charges such as tolls, violations, and fees against it, then voids them when needed. A separate partner surface lets connected systems list a company's vehicles and rentals and push charges in, and webhook endpoints deliver events so downstream tools stay in sync.

## For AI agents

Manage a vehicle rental business: list and price vehicles, check availability, quote trips, create customers, move bookings through their status, and record or void charges like tolls and fees.

## Scope

Does not handle payment processing, insurance claims, or vehicle telematics. Use for rental listing, booking, and charge management only.

## Capabilities

- List rental vehicle listings and check their availability for a date range
- Quote a trip with pricing for a listing and dates
- Create and update customer records
- List bookings and move a booking through its status
- Record or void charges such as tolls, violations, and fees on a booking
- Set or clear daily pricing on a listing
- Register webhook endpoints and read their delivery log

## Use cases

### Agent booking assistant

An AI agent connected through Jentic handles a rental enquiry start to finish: it lists the vehicles free for the requested dates, quotes a trip, creates the customer record, and reads back the booking, so the developer never hand-wires the bearer auth or the quote-to-booking sequence.

Example prompt: List vehicles available for the requested dates, quote a trip for the chosen listing, create the customer, and return the booking

### Dynamic pricing automation

A revenue tool keeps a fleet's rates current by setting daily pricing on each listing from demand signals and clearing overrides when a promotion ends, driving the daily-pricing endpoints directly instead of editing rates in a dashboard.

Example prompt: Set daily prices on a listing for the next 30 days and clear any stale pricing overrides

### Charge reconciliation

A back-office workflow posts tolls, violations, and extra fees to the right booking as they come in and voids any charge that was raised in error, keeping each booking's charge list accurate without manual edits.

Example prompt: Add a toll charge to a booking and void an earlier charge that was raised in error

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v2/listings` | List rental vehicle listings |
| GET | `/v2/listings/availability` | Check listing availability |
| POST | `/v2/quote` | Quote a trip |
| POST | `/v2/customers` | Create a customer |
| GET | `/v2/bookings` | List bookings |
| PUT | `/v2/bookings/{b_id}/status` | Update a booking's status |
| POST | `/v2/bookings/{b_id}/charges` | Add a charge to a booking |
| POST | `/v2/webhooks` | Create a webhook endpoint |

## Key resources

- **Listings** — List vehicles, check availability, and set or clear daily pricing
- **Bookings** — List bookings, update status, and manage their charges
- **Customers** — Create, read, and update customer records
- **Quotes** — Quote a trip for a listing and dates
- **Webhooks** — Register endpoints, list event types, and read the delivery log

## 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:** 45 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 99 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 19 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 73 / 100
- **View full report:** https://jentic.com/apis/fleetwire.io/fleetwire/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 Fleetwire by hand means handling its bearer-token auth, keeping the main v2 API and the separate partner surface apart, and sequencing quote to customer to booking yourself. Through Jentic you install once, import Fleetwire from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Fleetwire puts the listing id and booking id in the URL path (`/v2/listings/{l_id}`, `/v2/bookings/{b_id}`), so a rule can pin your agent to read-only listing and booking lookups. You choose the operations it may call, so write operations like updating a booking's status or adding a charge are not included unless you add them.
- **Credential handling:** Your Fleetwire token 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 'quote a vehicle rental' or 'add a charge to a booking', and Jentic returns the matching Fleetwire operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **Booqable** — General rental business management rather than a vehicle-rental-specific booking surface
- **Shopware** — E-commerce order management for goods rather than date-bounded rental bookings
- **Square** — Takes the payment for a rental that Fleetwire has quoted and booked

## FAQ

### What authentication does the Fleetwire API use?

The Fleetwire API authenticates with a bearer token in the Authorization header, per its OpenAPI spec. There are two kinds: an API token carrying read and write scopes for the main v2 surface, and a partner key for the partner endpoints. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never lands in the agent's context.

### Is there a Fleetwire MCP server?

You don't need an MCP server to give your agent Fleetwire. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the listing, quote, booking, and charge operations on demand, without a separate server's tool definitions loaded into its context.

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

Yes. Write a rule that allows only the read operations, such as listing vehicles, checking availability, and reading bookings, so the agent can answer questions about the fleet but cannot change prices, move a booking's status, or add charges, and every call it makes is logged.

### Can I add charges to a booking with the Fleetwire API?

Yes. The booking charges endpoint records tolls, violations, and fees against a specific booking, and a matching delete operation voids a charge that was raised in error, so the booking's charge list stays accurate.

### What are the rate limits for the Fleetwire API?

The OpenAPI spec does not specify rate limits. Check the vendor documentation at https://docs.fleetwire.io for current limits before running bulk pricing or charge jobs.

### How do I quote and create a booking through Jentic?

Search Jentic for 'quote a vehicle rental', which returns the Fleetwire quote operation with its input schema, then create the customer and read the booking back. To run it on your own infrastructure, install Jentic One from its GitHub repo.