UpdaterAgent is built around a hub-and-spoke integration model: every external service is encapsulated behind a typed broker interface in the Infrastructure layer, keeping business logic independent of third-party API details. This architecture supports 18 brokers today, covering the full logistics stack from load import to real-time vehicle tracking and AI-powered document analysis.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/ShohjahonSohibov/repo-for-agent/llms.txt
Use this file to discover all available pages before exploring further.
Integration summary
| Broker | Category | Purpose | Auth method | Frequency |
|---|---|---|---|---|
| QuickManage | TMS | Load, driver, truck data + webhooks | Bearer + HMAC | Polling 3hr + webhooks |
| Zippy | ELD | Vehicle position tracking | API creds | Polling 25min |
| Samsara | ELD | Alternative ELD platform | API token | Configurable |
| UTrackin | ELD | Vehicle tracking | OAuth 2.0 | Configurable |
| LevelEld | ELD | Level ELD tracking | API creds | Configurable |
| Telegram | Comm | Driver notifications, alerts | Bot token | Scheduled + on-demand |
| Nylas | Email processing, ratecon extraction | OAuth 2.0 | Webhooks | |
| Google Map | Routing | Route optimization, geocoding, ETA | API key | On-demand (fallback) |
| OSRM | Routing | Open-source routing (primary) | None | On-demand |
| Valhalla | Routing | Alternative routing engine | None | On-demand |
| HereRouting | Routing | HERE Maps routing | API key | On-demand |
| Nominatim | Geocoding | Address geocoding fallback | None | On-demand |
| GeoNames | Geocoding | Timezone lookup | None | On-demand |
| AskAI | AI | Document analysis, ticket suggestions | API key | On-demand |
| Eia | Data | Energy and fuel data | API key | Scheduled |
| OnTimeLogs | Logging | OnTime driver logs | API creds | Polling |
| RTA | Analytics | Real-time analytics | API key | On-demand |
Broker pattern
Every integration in UpdaterAgent follows a four-part structure defined insrc/UpdaterAgent.Infrastructure/Brokers/.
Interface — a typed contract that services depend on, never the concrete HTTP client:
HttpClient, registered as a scoped service:
appsettings.json or environment variables:
Result errors so callers receive structured failures instead of exceptions:
Each broker directory under
Brokers/ contains exactly these four concerns: IBroker.cs, Broker.cs, BrokerErrors.cs, and a Contracts/ folder for config and response DTOs.Per-company configuration
Each company can activate a different set of integrations. TheIntegrationProvider entity stores per-company credentials and the active provider selection:
Detailed integration guides
QuickManage
TMS sync, webhook setup, driver ID mapping, and manual import endpoints.
ELD providers
Zippy, Samsara, UTrackin, and LevelELD — position polling and ELD settings API.
Routing and geocoding
Hybrid OSRM + Google Maps routing strategy and geocoding fallback chain.