Tai Software API
A public REST API with a developer portal at docs.taicloud.net, webhooks, and published rate limits. Auth is a single x-api-key per customer with no OAuth, and keys arrive through LSP onboarding. The documented surface is shipment-centric; accounting and master data endpoints are thinner.
Frequently asked questions
Tai Software scores D on Supergood's API Report Card. A public REST API with a developer portal at docs.taicloud.net, webhooks, and published rate limits. Auth is a single x-api-key per customer with no OAuth, and keys arrive through LSP onboarding. The documented surface is shipment-centric; accounting and master data endpoints are thinner.
Without a usable official API, teams fall back on manual exports, file drops, or one-off vendor integrations. The other option is an unofficial API layer like Supergood that automates the authenticated web app directly. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
Tai Software (operating as Tai TMS) is a cloud-based transportation management system purpose-built for freight brokers.
Vertical: Fleet / Trucking / Logistics - specifically TMS for freight brokerages and 3PLs (not asset-based carriers). Freight broker reps, operations managers, dispatchers, accounting teams and IT integration owners use Tai TMS to: receive customer RFQs, rate-shop across direct carrier APIs and load boards (DAT, Truckstop, Newtrul) in a single screen, book LTL and FTL shipments with auto-generated BOLs and rate confirmations, post loads to multi-board (DAT, Truckstop, 123Loadboard), onboard and monitor carriers via Highway / MyCarrierPackets (FMCSA/insurance/SaferWatch checks), track shipments in real time via project44, MacroPoint and Open Track, automate AR/AP (factoring via Triumph/RoadSync, payments via Relay/CardConnect/Global Payments), handle freight claims via FreightClaims/GLS, sync email + CRM via Front, and expose orders/shipments/tracking to customers via the public API (`bookDomesticShipment`, `getShipmentDetails`, `trackingUpdate`).
6/10 within freight-broker TMS.
For freight brokers running on Tai TMS, the platform is the system of record for the brokerage: customer/shipper master data, carrier master data + compliance status (FMCSA, insurance, SaferWatch via Highway/MyCarrierPackets), quotes and rates (LTL contract pricing across direct carrier APIs + load-board spot pricing from DAT/Truckstop), orders/shipments and BOLs, load postings on multi-board, carrier assignments and rate confirmations, real-time tracking events flowing in from project44/MacroPoint/Open Track and ELD providers (Motive), PODs and shipment documents, AR invoices to shippers and AP bills to carriers (with factoring via Triumph/RoadSync and payments via Relay/CardConnect/Global Payments), carrier scorecards and lane-level margin, freight claims and email/CRM threads synced via Front.
Founded 2005 as Teknowlogi; the Tai TMS product was originally marketed by Teknowlogi as 'the first cloud-based expert platform' for logistics in 2017 (PRNewswire launch).
Auth is API-key only (`x-api-key`) - no OAuth 2.0, so credential rotation and per-user scoping are coarse vs Rose Rocket / Samsara. Production base URL is per-tenant (`[site-code].taicloud.net`) - integrators must discover and configure the site-code per customer; can't hit a single global host. Full sourced list under Sources below.
Common alternatives include McLeod Software (LoadMaster / PowerBroker), Descartes Aljex TMS, MercuryGate, Turvo, Revenova TMS (Salesforce-native), Rose Rocket. Graded alternatives appear under "More from the report card" below.
Supergood's grades measure one thing: can a customer's engineering team get their own data out programmatically? Supergood checks six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and rolls them into a letter grade. Supergood re-verifies grades, and they only move on evidence.
Yes, via a managed API layer. Supergood builds REST APIs and MCP servers for authenticated enterprise web apps, so AI agents and internal tools can read and write data programmatically. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
Not that we could find. As of August 2026 there is no official Tai Software MCP server in any public registry, and no maintained community server we're aware of. We re-verify this periodically — report an inaccuracy below if we missed one.
Not natively. Tai Software doesn't publish an MCP server, so MCP clients like Claude, Cursor, and Codex have nothing to connect to out of the box. If that changes, this page will reflect it.