Catalog only
Transport
Grab Thailand transport and ride types.
Consumer-facing transport page for ride types such as taxi, car, van, and motorcycle services in Thailand. Useful for product naming and user-visible service categories, not live dispatch or public API use.
Public
Official public consumer transport page
Free public
On product or market update
2026-05-11
Public web, file, catalog, or documented endpoint access with no paid gate implied in the source profile.
page reference only
service or stand name, operator or provider, legal status or certification, vehicle or service category, fare rule where applicable, pickup point or stand, airport terminal/gate where relevant, lat/lon, complaint channel, aggregate trip metrics or demand zone where exposed, quote/ETA fields only when authorized, source ID
High for official context; validate endpoint availability before automation.
Runtime truth
Catalog only
Not yet
No runtime entity scope yet.
No live observation ingestion yet.
Not wired into active decisions yet.
Profiled in the atlas and public pages, but not yet connected to live graph computation.
How this helps travel recommendations
Turns Thailand taxi and ride-hailing into source-backed decisions: whether a service is legal, what the fare rule actually is, where airport pickup happens, whether a stand or motorcycle-taxi win exists, which areas have strong taxi demand, and which app or complaint surface can actually support the claim.
Endpoint and API notes
Consumer-facing transport page for ride types such as taxi, car, van, and motorcycle services in Thailand. Useful for product naming and user-visible service categories, not live dispatch or public API use.
Open the source endpoint or documentation. Return to the Thailand data atlas.
Developer reference
Use DLT for legal registry, driver-license, operator-license, Taxi OK/VIP, complaints, and app-certification context; OTP/MOT for aggregate taxi GPS analytics and pickup/dropoff zones; AOT for airport taxi counters and surcharge rules; OSM/Google/Longdo/NOSTRA for stands and pickup points; and platform APIs only where explicit authorization exists.
Refresh weekly or when the catalog metadata changes; many agency catalogs update irregularly.
Turns Thailand taxi and ride-hailing into source-backed decisions: whether a service is legal, what the fare rule actually is, where airport pickup happens, whether a stand or motorcycle-taxi win exists, which areas have strong taxi demand, and which app or complaint surface can actually support the claim.
DLT, Thailand.go.th, MOT/OTP, AOT, DLT GPS, OSM/Overpass, Google Places, Longdo, NOSTRA, airport/operator pages, and partner-authorized ride-hailing or fleet integrations.
Example request
# Source landing/download page; inspect linked resources before automation.
curl -L "https://www.grab.com/th/en/transport/"Failure modes
- There is no single all-taxi Thailand API.
- Public taxi data is usually aggregate, legal, or airport-specific rather than live dispatch.
- OTP taxi GPS analytics do not expose raw GPS traces, live vehicle positions, driver identity, or passenger identity.
- Ride-hailing apps show ETA, fare, and driver data to users, but that does not make it a public ingest API.
- Airport taxi surcharge, baggage, and toll rules differ from street-hail or app pricing.
- Motorcycle taxis, metered taxis, airport limousines, and app hire-cars need different service models.
- Taxi stands and motorcycle-taxi wins are often under-mapped or informal.
- Complaint datasets are useful for trends, not for realtime operational quality.
Last checked and source confidence
Last checked: 2026-05-11.
Source confidence: Treat this profile as strongest for the exact role named above. It is weaker when the source is stretched into live availability, legal proof, or traveler-fit decisions it does not directly prove.