CarFleet for developers

Reach a workspace from your own systems, or from an AI assistant. One API key, minted in Settings → API & MCP, works for both. You choose at minting whether a key can write — and no key of either kind can take a payment, issue an invoice or message a customer.

Start here

Connect an AI assistant

Step by step, for Claude, ChatGPT, Claude Code, Cursor or anything else that speaks MCP. Ten minutes, once, and no code. Afterwards you can ask your workspace what is going out today, who owes you money, or what is free next weekend — in plain language.

Where the writes stop

A read-write key reaches reference data — vehicles, add-ons, charge types, invoice settings — over MCP. Every REST endpoint reads. Nothing anywhere creates a booking, records a payment, or sends a customer anything.

That line is drawn where an action cannot be withdrawn. A UAE tax invoice number is burned the moment it is allocated and the sequence has to stay gapless; a card charge and a message reach the outside world. Those keep a person in the loop — ask an assistant to draft, then press the button yourself. It also cannot read identity documents: Emirates ID, passport and licence numbers are encrypted and unreachable through any key, and contact details are stripped before an assistant sees them.

Saying so here is cheaper than letting you find out halfway through building.