# Falcon Freight Labs > Creators of TMF (Transportation Management Functions) — giving AI agents the tools to execute freight. Rate, book, track, and document across LTL carriers through native MCP integration. ## What is TMF? TMF (Transportation Management Functions) is the infrastructure layer that gives AI agents and developers the tools to execute freight operations. TMF sits between applications and carriers — the same way Stripe sits between apps and banks. TMF is not a TMS (Transportation Management System). A TMS is an application-layer product built for humans. TMF is the infrastructure layer underneath — providing freight functions that TMS platforms, 3PLs, and AI agents consume via API. ## Example Functions TMF makes freight operations available to AI agents as executable functions. Starting with: - **Rate** — Get pricing from multiple LTL carriers simultaneously. Quotes returned in a standardized format for comparison. - **Book** — Schedule pickups and create shipments across carriers through a unified interface. - **Track** — Monitor shipment status across carriers with normalized tracking events. - **Document** — Generate BOLs, labels, and shipping paperwork. These are starting points — the function surface will grow as the platform matures and partners identify new workflows. ## Current Focus TMF is launching with **Rate** and **Book** (pickup scheduling) — two clearly defined workflows with high complexity and heavy reliance on carrier APIs. They make an ideal starting point: rating requires translating between carrier-specific formats, authentication methods, and pricing structures, while booking orchestrates pickup scheduling across different carrier workflows. Together they demonstrate that AI agents people already use — like Claude — can execute real freight operations end-to-end. They also provide a natural path to onboard design and development partners who can shape the platform as Track and Document capabilities come online. ## AI Agent Integration TMF is AI-native by design. Any AI agent — Claude, AWS Bedrock agents, custom-built agents — can discover and execute freight functions through: - **MCP (Model Context Protocol)** — Native integration for Claude Desktop and AWS Bedrock. Agents discover TMF tools automatically. - **REST API** — OpenAPI-specified endpoints for direct integration by any application or agent framework. TMF is agent-agnostic. People are building great agents. People have built great TMS products. TMF provides the freight functions layer between the two, so neither has to solve carrier integration themselves. An AI agent can receive a natural language shipping request, translate it into TMF API calls, receive live carrier quotes in a standardized format, compare options, and execute a booking — with no carrier-specific code. ## Live Carriers - **SAIA** — Full rate + book lifecycle operational - **R+L Carriers** — Integration complete - Expanding to ODFL, Estes, Dayton Freight A single API call returns pricing from all integrated carriers simultaneously. ## Who TMF Is For - **AI agent builders** — Every supply chain agent needs freight execution capabilities. TMF is the fastest path. - **TMS platforms** — White-label TMF functions instead of building and maintaining carrier integrations. - **3PLs and brokers** — AI agents assist freight coordination through TMF without adding overhead. - **Shippers** — Access AI-powered freight operations without understanding carrier infrastructure. - **Developers** — Skip months of carrier-by-carrier integration. Freight execution out of the box. ## Technical Details - MCP-native — agents discover and call freight functions directly - REST endpoints available for direct application integration - OpenAPI specification for developer tooling - Parallel quote processing across carriers - Standardized internal codes mapped to carrier-specific requirements - Automated carrier auditing — AI-driven test suites validate every integration across 40+ checks ## Links - Home: https://falconfreightlabs.com - What is TMF: https://falconfreightlabs.com/tmf/