5 minMCPAgentsWialon API
Giving an AI agent read access to Wialon
Why the Wialon tools are one remote MCP endpoint rather than a package, what it does with your token, and why a skill comes with twelve tools.
Read itWriting
Notes from building on Wialon
What the API does rather than what the documentation says it does: the traps, the response shapes that change under you, and what it takes to put an agent in front of any of it. Written while building FleetAI, and checked against the calls it makes.
4 minWialon APITrips
The truck that drove 208 km and reported as stationary
Wialon events/load answers in two different shapes depending on how many trip detectors an account has, and reading the wrong one loses every trip — silently.
Read it
4 minWialon APIFleet data
How many vehicles are online is not one question
Wialon gives you seven states, not a boolean. Two panels on the same dashboard said 19 and 29 for a fleet of 58 — here is the rule that settled it.
Read it
4 minWialon APIReports
Getting a Wialon report as a PDF over the API
Two calls, and four details that quietly break the export: the format bitmask, compress defaulting to 1, errors arriving as JSON at HTTP 200, and one report result per session.
Read itAll of this is in the product
The traps above are handled by the tools rather than by whoever is asking. Bring your own Wialon token and ask in plain words.