FREIGHT DATA INFRASTRUCTURE · MCP-NATIVE

The freight data API
for engineers and AI agents.

Connect ELDs, TMS platforms, and insurance systems through one unified API. Build freight applications faster with REST and MCP-native integrations.

No credit card · Sandbox data · Start in seconds

Ship in minutes,
not months.

Motive
{
  "externalId": "10294",
  "lat": 36.112,
  "lon": -115.142,
  "speedKph": 62
}
Samsara
{
  "gps": {
    "latitude": 36.112,
    "longitude": -115.142
  },
  "speedMilesPerHour": 39
}
Geotab
{
  "x": 36.112,
  "y": -115.142,
  "diagnostic": {
    "value": 62,
    "unit": "kph"
  }
}
GET/v1/vehicles
{
  "id": "veh_10294",
  "carrier": "Ridgeline Freight LLC",
  "position": {
    "lat": 36.112,
    "lon": -115.142
  },
  "speed_mph": 39,
  "odometer_mi": 418203.6,
  "engine_state": "on",
  "last_seen_at": "2026-11-14T22:31:08Z",
  "source": "motive"
}

Your AI agent
already knows how to use FennecMesh.

FennecMesh speaks MCP natively. No SDK, no glue code: 18 tools over live freight data, including the write access to onboard a carrier end to end. Point Claude, Cursor, or any MCP client at it.

agent · freight-ops live data
You Is Blue Mesa safe to book?
Agent Let me verify before you commit.
→ verify_insurance("2945118")
✗ fail — an excluded driver drove 27.1 h this week (ELD cross-check)
→ list_loads(status="in_transit")
3 loads in transit for Blue Mesa Transport
→ get_driver_hos("drv_0459…")
2h 05m drive time remaining
Agent Don't book. An excluded driver has been at the wheel and Unit 213 isn't on the policy. LD-1066 is the exposed load — want me to re-tender it?
{
  "mcpServers": {
    "fennecmesh": {
      "type": "http",
      "url": "https://fennecmesh.com/mcp",
      "headers": { "X-Api-Key": "your-api-key" }
    }
  }
}

Works with Claude Code · Cursor · Claude Desktop · any MCP client

Connect an agent →

18 tools. Zero glue code.

Telematics

fennecmesh_overviewfleet KPIs and freshness
list_vehiclesevery truck, live
get_vehicleidentity, driver, position
get_vehicle_historybreadcrumbs and stops
list_driversHOS clocks for everyone
get_driver_hos8-day duty log
list_hos_violationswho's out of hours
list_inspectionsDVIRs with defects
get_inspectiondefect drill-down

TMS

tms_summaryrevenue, margin, coverage
list_loadsone model for every TMS
get_loadstops + live truck, ETA, late flag

Platform

list_connectionsstatus and freshness
list_invitationsonboarding pipeline
create_invitationagent onboards the carrier itself

Insurance

verify_insuranceverdict, checks, ELD cross-check
list_insurance_verifiedevery carrier, worst first
fmcsa_lookuplive government filings

Ask Fennec AI
about your freight data.

Grounded in your live data — positions, hours, loads and insurance. HOS is planning info; the ELD is the legal record.

Which loads will arrive late?Who can take a 6-hour run?Is Blue Mesa safe to book?
Fennec AIlive data
Which of my loads will arrive late?
Two loads are trending late:
LD-2231Chicago → Denver
LateETA +2h 40m210 mi out
LD-1066Atlanta → Charlotte
LateMissed pickup
Ask Fennec AI…

One key.
Every freight system.