Reconcile driver balances before the payout goes out
Connect taxiCRM to the AI agent: drivers, trips, shifts, balances, payouts and fines. The agent reconciles shifts with transactions and spots negative balances.
How the agent works with taxiCRM
The agent calls the taxiCRM public API on your fleet subdomain and starts from the list of cabinets — trips and transactions are tied to those. From there it reads drivers and their balances, shifts, trips, payouts and payment details, cars and rental agreements, fines, driver chats and the fleet CRM pipelines. Out of that come the morning summary for yesterday, the picture of who owes what and the list of drivers approaching a payout.
A driver balance is not a line in a card but a result: shifts, trips, deductions, fines and transfers land in it as transactions, and the agent rebuilds the sum from them instead of trusting a single number. A fleet usually holds several aggregator cabinets, and one driver often works through two at once, so a total from one cabinet is a part of the earnings, not all of them. That is why the agent always names which cabinet and which period a figure covers.
For writes the agent does what does not move money: registers a driver, creates a deal in the fleet pipeline or a car, pauses a rental agreement, messages a driver in chat. Every such action is shown before it is sent — a message goes to a live person behind the wheel, not into a report. Money methods are stricter: paying out a driver, changing a balance and unblocking a transaction are closed by the spec and answer 402 until they are opened on request to taxiCRM support.
The connection is the fleet subdomain plus its API key; the connector signs every request itself, so no signature has to be passed by hand. The key belongs to the fleet rather than to a person: there is no separate user account behind the agent, it sees all the cabinets of the account, and access is revoked by replacing the key. Lists are read page by page and always inside period bounds, so a large fleet never turns into one heavy export and old shifts do not drift into a fresh summary. If a method is closed, there were no shifts in the period or a chat is empty, the agent says so directly instead of showing an empty table.
Integration scenarios
Driver balances before payout
The agent reconciles shifts, trips and transactions and shows which drivers went negative and what balance each one brings into the payout.
Fines and rental agreements
The agent collects unpaid fines and paused rental agreements and links them to specific cars and drivers in the fleet.
Morning fleet summary
Every morning the agent sends yesterday totals: trips, shifts and driver transactions broken down by aggregator cabinets.
Review of driver conversations
The agent goes through fleet chats, collects driver requests left without a reply and shows which questions come up most often.
Driver hiring in the pipeline
The agent walks the deals in the fleet pipeline, shows which stage candidates got stuck at and registers a new driver once you hand over the contact.
Cars that stood idle
The agent matches the fleet cars against shifts and trips for the week and names the ones that never moved while their rental agreement stayed active.
taxiCRM examples
В минусе 17 водителей из 143, суммарно −86 400 ₽.
Свёл смены, поездки и транзакции за неделю по двум кабинетам агрегаторов. У 11 из них минус закрывают неоплаченные штрафы, ещё у четверых договор аренды стоит на паузе вторую неделю.
How to connect
Before you connect
- A taxiCRM fleet cabinet with access to the company settings
- An arrangement with taxiCRM support if you need driver payouts
- 1
Open the fleet dashboard, note the subdomain
The account address looks like https://yourfleet.taxicrm.ru — the part before .taxicrm.ru is the subdomain. The public API lives at the same address.
- 2
In Company settings open API
Path: «Компания» → «Настройки компании» → “API” (Company → Company settings → API). The fleet API key lives here; every request is signed with it.
- 3
Copy the fleet API key
One key covers the whole fleet and opens all of its data — drivers, trips, shifts, payouts, penalties, rentals. Treat it as a password.
FAQ
With the fleet subdomain and API key: the subdomain is the part of your cabinet address before .taxicrm.ru, and the key sits under Company → Company settings → API. The connector signs the request itself, so you do not need to pass a signature.
Drivers and their balances, trips, shifts, transactions, payouts and payment details, cars and rental agreements, fines, driver chats and the fleet CRM pipelines.
It can: register drivers, create deals and cars, pause a rental and message a driver in chat. By default it works in read and summary mode.
Paying out a driver, changing a balance and unblocking a transaction are opened only on request to taxiCRM support, as the spec states. Reading data works right after you connect.