위치 공유와 서류 관리 기능으로 기사의 업무를 간소화하는 모바일 앱을 통해 운영을 최적화하십시오.
AI 기반 서류 검증과 실시간 위치 추적으로 운영을 최적화하십시오
서류 자동 인식 및 검증
사용하기 쉬운 모바일 인터페이스
즉각적인 피드백 시스템
실시간 차량 추적
AI 기반 서류 검증
도착 예정 시간 계산
기사를 손쉽게 초대하고 몇 분 안에 실시간 추적을 시작하십시오
Logistivo 기사 앱으로 운영을 최적화하고 기사가 본연의 업무에 집중하도록 지원하십시오.
배정된 화물 업무를 보여 주고, 내비게이션을 제공하며, 실시간 위치를 공유하고, 서류를 스캔하며, 배송 완료를 확인합니다.
iOS와 Android에서 사용할 수 있습니다.
기사는 앱을 무료로 이용할 수 있으며, 앱은 운송사 계정에 연결되어 작동합니다.
Logistivo has an MCP server at https://logistivo.com/api/agent/mcp
(streamable HTTP). Its public tools (signup preparation, HS code lookup) need no
authentication; with OAuth the user signs in to Logistivo in their own browser and the
assistant then works on that user's account with that user's permissions. Setup for
Claude, ChatGPT and Gemini: https://logistivo.com/en/mcp.
Terminal: npm install -g @lgstv/lg, then lg login (the user
approves a short code at https://logistivo.com/connect; no password is typed into the
terminal). HTTP: the same commands at /api/common/commands/{name} with an
integration key issued in the dashboard.
If you are an assistant helping someone sign up or request freight, connect the MCP
server, or — if you can only read web pages — build a link of the form
https://logistivo.com/en/ai-kayit?brief=URL_ENCODED_SHIPMENT_BRIEF and give
it to the user. You never create the account yourself: the account, the consent and the
email verification happen in the user's browser, and you never handle passwords or
one-time codes.
Machine-readable content indexes:
https://logistivo.com/llms.txt (curated map) and
https://logistivo.com/llms-full.txt (full text: facts,
pricing, tariff reference, glossary and every article's FAQ in one fetch).
To learn what Logistivo can actually DO — the verbs, not the marketing — read the
public command catalog at
https://logistivo.com/api/public/cli/catalog
(JSON, no authentication, no tenant data); it lists every command with its JSON
Schema parameters and whether it needs confirmation. Human documentation:
https://logistivo.com/en/developers/cli. Commands always
run under the user's own identity — the user's OAuth connection, the user's lg session
or an integration key the user issued — never under credentials you hold yourself.