The neutral freight reference layer
No freight to sell. No carrier to push. Primary-source freight data your team — and your agents — can call and cite.
Reference data and deterministic calculations only — not booking, filing, tracking, carrier rating, or legal determination.
REST API · MCP server · GPT · n8n · Zapier · Make
Every step is a live tool
Pack it, weigh it, classify it, declare it, land it — the same functions your agents call are the tools you use.
Real outputs, not promises
Every example below is generated at build time by the live tool it belongs to — never hand-typed.
GET /api/ldm?length=1200&width=800&qty=10&stackable=falseJSON ↗GET /api/chargeable-weight?l=100&w=80&h=80&gw=60&pcs=2JSON ↗GET /api/pallet?pl=120&pw=80&pmh=180&bl=40&bw=30&bh=25JSON ↗GET /api/containers?type=40ft-high-cubeJSON ↗GET /api/convert?value=1000&from=kg&to=lbsJSON ↗POST /api/consignmentPOST /api/shipment/summaryGET /api/emissions?mass=1000&distance_km=500&mode=roadJSON ↗GET /api/adr?un=1203JSON ↗GET /api/adr-calculator?un=1203&qty=200JSON ↗POST /api/adr/lq-checkGET /api/hs?q=coffeeJSON ↗GET /api/incoterms?code=FOBJSON ↗GET /api/duty?methodology=trueJSON ↗GET /api/ics2-check?description=giftsJSON ↗GET /api/airlines?prefix=176JSON ↗GET /api/unlocode?code=NLRTMJSON ↗GET /api/uld?type=AKEJSON ↗GET /api/vehicles?slug=standard-curtainsiderJSON ↗GET /api/validate?value=MSKU1234565&type=containerJSON ↗GET /api/airports?iata=LHRJSON ↗GET /api/nearest-airport?lat=51.4706&lon=-0.4619&max_results=1&type=large_airportJSON ↗Ground truth your agent can cite
Every response carries a _source envelope — the authority, the dataset edition, and where it came from.
Primary sources, verified dates
Every dataset names its issuing authority and the date it was last audited against it — the same provenance backbone that stamps _source on every API response.
| Dataset | Authority | Edition | Last audited | Status |
|---|---|---|---|---|
| ADR dangerous goods | UNECE | ADR 2025 | 2026-05-13 | verified |
| HS codes | World Customs Organization | HS 2022 | 2026-05-15 | verified |
| Airline codes & AWB prefixes | IATA / ICAO airline code registries | — | 2026-05-13 | pending-verification |
| UN/LOCODE locations | UNECE | UN/LOCODE 2024-2 | 2026-05-15 | verified |
| Airports | OurAirports (community-maintained open data) | OurAirports 2026-06-24 | 2026-06-24 | verified |
| ISO containers | ISO 668 / ISO 1496 | — | 2026-05-15 | pending-verification |
| ULD types | IATA ULD Technical Manual + carrier-published specifications | — | 2026-05-13 | pending-verification |
| Vehicles & trailers | EU Directive 96/53/EC, UK DVSA, 49 CFR (regulatory limits) | — | pending verification | pending-verification |
| Incoterms 2020 | International Chamber of Commerce (Incoterms 2020) | — | pending verification | pending-verification |
| UK duty & VAT | HM Revenue & Customs (GOV.UK Trade Tariff) | — | 2026-05-16 | live |
| Emission factors | ISO 14083:2023 / GLEC Framework v3.2 methodology; factors from UK DEFRA/DESNZ 2026 (OGL v3.0), US EPA GHG Emission Factors Hub 2024 (US-Gov public domain), and ADEME Base Carbone V23.6 (Licence Ouverte / Etalab). GLEC = methodology citation only. | v1 (DEFRA 2026 + EPA 2024 + ADEME Base Carbone V23.6) | 2026-06-23 | verified |
| Identifier check digits | ISO 6346 (containers) / IATA Air Waybill modulus-7 (air waybills) / IMO Ship Identification Number Scheme — public check-digit algorithms, implemented not reproduced | ISO 6346 + IATA AWB mod-7 + IMO number scheme | 2026-06-23 | computed |
verified multi-source audit complete · pending-verification audit in progress, provenance not yet asserted · computed deterministic method, not a dataset · live fetched from the authority at request time
How every dataset is verified — the full methodology → · Spot an error? Dispute a value.
Free to start, honest ceilings
Need SLA, higher limits, or audit export? contact@freightutils.com
Wherever your stack lives
The same reference layer behind one REST API — packaged for agents, workflows and humans. freightutils-mcp v2.11.2 on npm.
Point your MCP client at the server and every tool is callable, with _source on each response.
{
"mcpServers": {
"freightutils": {
"command": "npx",
"args": ["-y", "freightutils-mcp"]
}
}
}One REST API, snake_case JSON, OpenAPI-described. Import the spec or the Postman collection and go.
Processing posture, retention windows, sub-processors and a signable DPA — written for the person who has to say yes.