For 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.
Use for: List the vehicles available for a date range, Quote a rental for specific dates, Create a customer record for a renter, Update the status of a booking
Not supported: Does not handle payment processing, insurance claims, or vehicle telematics. Use for rental listing, booking, and charge management only.
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.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Fleetwire 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.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ffleetwire.io%2Ffleetwire" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ffleetwire.io%2Ffleetwire" | 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.
What an agent can do with Fleetwire API.
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
Patterns agents use Fleetwire API for, with concrete tasks.
★ 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.
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.
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.
Add a toll charge to a booking and void an earlier charge that was raised in error
36 endpoints — 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.
METHOD
PATH
DESCRIPTION
/v2/listings
List rental vehicle listings
/v2/listings/availability
Check listing availability
/v2/quote
Quote a trip
/v2/customers
Create a customer
/v2/bookings
List bookings
/v2/bookings/{b_id}/status
Update a booking's status
/v2/bookings/{b_id}/charges
Add a charge to a booking
/v2/webhooks
Create a webhook endpoint
/v2/listings
List rental vehicle listings
/v2/listings/availability
Check listing availability
/v2/quote
Quote a trip
/v2/customers
Create a customer
/v2/bookings
List bookings
/v2/bookings/{b_id}/status
Update a booking's status
/v2/bookings/{b_id}/charges
Add a charge to a booking
/v2/webhooks
Create a webhook endpoint
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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.
Alternatives and complements available in the Jentic catalogue.
Specific to using Fleetwire API through Jentic.
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.
GET STARTED