Spot ATI.SU loads still without a carrier right in chat

The agent calls the exchange API at api.ati.su and reads the same sections you see in the account: cargo and orders, auctions and carrier responses, the firm directory with their trucks and sites, conversations in the exchange messenger, ATI-Doki documents, time slots and the rate index. It requests the sections one at a time, under the specific question, rather than pulling the whole exchange: a question about a trip raises the listing, its responses and the carrier card and leaves the rest alone.

The exchange is built so that the status of a listing on its own says little: a load sits marked as posted for a week and collects not a single response. So the agent counts not the status but the time a trip spends without a carrier and the number of responses on each listing. The rate in your order is compared against the ATI.SU index for the lane, keeping in mind that the index is a market reference for the route, not the price of a particular deal.

By default the agent works read-only: it builds a morning summary of auctions and new responses, pulls up a firm card together with its trucks and sites before a trip is handed over, and puts what it found into a reply in chat. Anything that changes state on the exchange — a message to a carrier in the messenger, a move on an order — it first shows in full and sends only after your confirmation.

The rate is capped at ten requests per second, so large exports are collected in parts and spread over time rather than fired at the exchange in parallel. Lists are taken page by page and the agent stops once it has the period it was asked for, not once the data runs out. About a section that did not answer it says so directly instead of showing an empty table.