Quote Russian Post prices and times before you ship anything

The agent works with the otpravka.pochta.ru account through its API: it calculates cost and time from the postcode, weight and dimensions, reads orders and shipments, pulls tracking statuses, runs addresses through normalisation and searches post offices by postcode or address. It starts from the account settings — that is how the connection itself is checked and how it becomes clear which sender parameters the calculations will run on.

Russian Post differs from courier services in that an address here is not a string but a postal object split into components: until an address is normalised, no shipment can be created. So the agent runs the addresses from your orders through normalisation and separately shows the lines Russian Post did not recognise — that is not an agent error but an address that will have to be fixed by hand. Tracking statuses arrive with the delay of sorting, and the agent reads them as a history, not as a fact of the current minute.

By default the agent calculates, searches and reports in chat: it builds a summary of shipments in transit, separates the delivered ones from those stuck in sorting and suggests a post office for the next batch. Anything that changes account data — an order, a batch — it first shows in full and sends only after your confirmation, and it does not answer a refusal with a repeat request.

Russian Post requires two headers at once — the application token and the account credentials — so the agent signs every call with them instead of opening a session. The rate stays within five requests per second, large exports go in parts, and the cost is calculated per parcel, because the tariff depends on the postcode, the weight and the dimensions. About a closed section the agent says so directly instead of showing an empty table.