Developers

Implement one API and your reservation system sells on any conversational channel.

You host a ten-endpoint API and Bota calls it live in every conversation: availability, prices, extras and the booking. No inventory sync, no queues, nothing to install. Implement it yourself with the contract and the validator in front of you, or let your AI agent do it.

API reference Guide for agents (Markdown)

Not another chatbot

If your rental company runs its own system, don't build the chatbot: connect it.

A chatbot built from scratch talks. Bota sells: it knows car rental, quotes with your real rates, applies your rules and confirms the booking in your system, on any conversational channel and in each customer’s language.

Three ways to integrate

Your system is already integrated

Karve, Wheelsys, Rently, RentHub, Rentsyst and HQ Rental Software. No code: create the account, connect your access and operate in minutes.

See integrations

You run your own system

You host Bota's standard API (ten JSON endpoints over HTTPS) and Bota calls it. OpenAPI 3.1 contract, real examples on every endpoint and a validator with the same schema we use in production.

See the OpenAPI contract

Your AI agent integrates it for you

More and more car rental companies build their own system with Claude Code, Codex, Antigravity or Cursor. The guide is written so that same agent connects your system to Bota end to end, and asks you for one thing only: to create the account.

See the guide for agents

How the standard API works

Register a sandbox

One call, no account: you get the sandbox key, the token Bota will send to your endpoint and the claim link. It expires after 30 days.

curl -sS -X POST https://www.bota-chat.com/api/public/developers/sandbox \
  -H 'Content-Type: application/json' \
  -d '{"email":"owner@your-rentacar.com","company":"Your Rent a Car","baseUrl":"https://api.your-rentacar.com/bota"}'

2
Implement the endpoints
Eight required and two optional. Bearer auth, money in cents, ISO-4217 currency, times in each office's timezone. Copy-ready examples on each one.
3
Verify from Bota
Bota calls your URL and validates every response with the same contract it applies in production. The report names the failing field. Repeat until it passes; optionally exercise the booking lifecycle.
```
curl -sS -X POST https://www.bota-chat.com/api/public/developers/sandbox/{id}/verify \
  -H 'Authorization: Bearer bota_sbx_…' \
  -H 'Content-Type: application/json' \
  -d '{"includeBookings": false}'
```
4
Go live
The person in charge opens the claim link and creates the account with the same email: the verified endpoint is connected. Then the agent can create the web chat; WhatsApp and phone are connected from the dashboard.

The ten endpoints

Contract v1.5.0

Ids chain: the office from /offices goes into /availability; the chosen offer carries groupId, tariffId and rateRef into /bookings; tariffId keys /extras, /concepts and /rate-rules.

Method	Path	Purpose	Required
GET	/health	Health check	Yes
GET	/offices	List offices	Yes
POST	/availability	Search availability	Yes
GET	/extras	List available extras	Yes
GET	/concepts	List rate concepts (schema v2, optional)	Optional
POST	/rate-rules	Bulk rate rules (preferred)	Optional
POST	/bookings	Create booking	Yes
GET	/bookings/{bookingId}	Get booking detail	Yes
POST	/bookings/{bookingId}/cancel	Cancel booking	Yes
POST	/bookings/{bookingId}/modify	Modify booking dates	Yes

For AI agents

Ask your agent and let it work

The guide is written for machines: ordered steps, absolute URLs, copy-ready examples and a single point where a person is needed. Claude Code, Codex, Antigravity, Cursor or whichever harness you use can complete the integration on its own.

Registers the sandbox and keeps the two keys.
Implements and verifies until every check passes.
Hands you a link and you create the account with your email.
Creates the web chat with the key and the snippet for your site.

Paste this sentence into your agent.

Read https://www.bota-chat.com/api/public/provider-api-guide and follow its steps to integrate my reservation system with Bota.

https://www.bota-chat.com/api/public/provider-api-guide

MCP server

For agents that sell, not integrate

Model Context Protocol over HTTP, stateless. Discover the companies selling with Bota, list their offices, search availability at the same price as their web chat and, where the company allows it, complete the booking: extras, driver details and confirmation in their system.

Endpoint: https://mcp.bota-chat.com/mcp
Tools: list_rental_companieslist_officessearch_availabilitychatselect_offerselect_extrasprovide_customer_detailsconfirm_booking
Client configuration: { "mcpServers": { "bota": { "url": "https://mcp.bota-chat.com/mcp" } } }

Try it

curl -sS -X POST https://mcp.bota-chat.com/mcp \
  -H 'Content-Type: application/json' -H 'Accept: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

The demo company is always available and its bookings are fictitious. Real companies decide whether they accept bookings from agents; otherwise the agent presents the quote and their contact.

Entry points for machines

Everything your agent needs, on stable URLs

None of them need an account or a key to read. If you only hand your agent one, make it the guide: it finds the rest from there.

www.bota-chat.com/llms.txtThe site map for language models: what each page holds and where it is.
www.bota-chat.com/api/public/provider-api-guideThe step-by-step integration guide, written for a machine to follow.
www.bota-chat.com/api/public/provider-apiThe OpenAPI contract of the standard API.
www.bota-chat.com/api/public/provider-api-docsThe browsable reference, for a person to read.
www.bota-chat.com/api/public/provider-api-devkitThe validator: it checks your implementation and tells you what fails.
www.bota-chat.com/api/public/developers/sandboxPOSTThe sandbox, no account and no card.
mcp.bota-chat.com/mcpPOSTThe MCP server, to sell car rentals from any agent.

Whichever agent you use: Claude Code, Codex, Antigravity or Cursor read these same URLs. They are meant not to change, so you can leave them written in your prompts or your internal docs.

Safeguards

HTTPS traffic to public addresses only: your sandbox URL goes through an anti-SSRF filter and Bota never follows redirects.
Secrets are shown once and stored hashed or encrypted. The claim link only works with the email used at registration.
Quotas per IP, per sandbox and per company on the sandbox and the MCP: every query costs a call to a reservation system and an AI turn.
A web chat created by an agent only works from your site's origins; agent bookings are attributed to their own channel and follow the company's rules.

Frequently asked questions

Do I need a Bota account to start integrating?

No. The sandbox is registered with an email and returns the keys immediately. The account is created at the end, once the integration is verified, through the claim link.

Can an AI agent do it without a person?

Everything but one step: creating the account and accepting the commercial terms is done by a person with the link the agent hands over. After that the agent can create the web chat. WhatsApp and phone require the account owner in the dashboard (Meta and Telnyx).

What if my system is already in the integrations list?

Nothing to code: create the account, connect your access and Bota operates in minutes. The guide for agents checks this before writing any code.

Is the price from the MCP server the same as the web chat's?

Yes. Every MCP search is a turn of the same engine the company's web chat uses, with its mandatory charges, time rules and one-way handling.

How much does it cost?

Integrating is free. Bota is paid per confirmed booking, with no setup fee and no lock-in. Terms are accepted when the account is created.

Your rental company can be running on Bota this week.

With your reservation system already integrated, or with the one you built.

Create account Talk to us