Break down driver shifts and fleet orders right in chat

The agent calls the Yandex Taxi Fleet API and reads the whole fleet: cars and the profiles of drivers and couriers, onboarding applications, orders together with their GPS tracks, transactions and blocked balance, the fleet work rules and the contractors' hours on the road. Out of these pieces it assembles a shift breakdown, a reconciliation of transactions against the work rules and a picture of who really takes shifts and who is merely listed.

Every request here is bound to a specific fleet: the partner id goes into the header, into the parameters and into the request body, so the agent always works within the boundaries of one fleet and never mixes data from different ones. An order in Fleet is not a single row but a bundle with a driver, a car, a track and transactions, and the order status on its own does not answer whether the passenger was delivered: for that the agent goes to the track and to the transaction history.

By its nature the work here is read-only: the agent builds reports, pulls the track for a disputed trip, shows the drivers with growing cancellations and the ones whose balance is blocked ahead of a payout. It does not edit driver or car records without your explicit request — behind such an edit in a fleet stands a living person and their shift. The agent backs its conclusions with figures from the same sections it took them from.

The Fleet API limits are hard and differ by section: the order list is returned many times slower than cars and transactions, and an export over a long period runs into both the page size and the request rate. So the agent cuts the period into chunks, walks the pages and says upfront how long it will take instead of breaking the report off halfway. Tracks and transactions it pulls pointwise, for specific orders rather than for the whole fleet at once, and it states plainly when a section is closed and there is no data.