About FreightUtils

I’m Marius Cristoiu — a UK ADR-certified freight transport planner working live air cargo operations at Heathrow, after years in freight operations planning.

FreightUtils exists because the reference tools I needed in the office — LDM check, ADR exemption points, HS codes that don’t hallucinate, airline AWB prefix lookup — either didn’t exist in a free, agent-readable form, or they sat behind a licensed-text paywall, or they were last updated in 2014. So I built them.

Freight reference data is scattered. ADR is published by UNECE and resold through specialist printers. HS codes live in a 6,940-row WCO nomenclature most people read as a PDF. UN/LOCODE is a 116,129-row UNECE list that updates twice a year. None of it cross-links. None of it is queryable by an API or an agent without buying a book or paying an integrator.

FreightUtils is the layer that sits above those canonical sources and makes them queryable — from a browser, from a REST API, or from an MCP server an agent can call. The data is the product. The tools on top are how a freight planner uses it without writing code.

Plainly:

• Not a startup. No VCs, no funding round, no growth team. One sole trader registered in the United Kingdom.
• Not a chatbot wrapper. The data is curated and audited; the calculations are deterministic; nothing on the site asks a language model what the answer is.
• Not anonymous. My name is on every page and my personal LinkedIn is linked right here.
• Not the canonical source. Operators making consequential calls must verify against the publisher named on the methodology page.
• Not a marketing-led brand. There are no testimonials on the homepage, no logos of fake enterprise customers, no “trusted by 10,000+ teams” line.

Three lines:

• 18 tools are open for casual use — 25 requests per day per IP with no signup, or 100 per day with a free API key (just an email, no card).
• The Pro API tier is £19 per month for 50,000 requests — aimed at developers wiring FreightUtils into a TMS, WMS, or agent workflow.
• Every dataset is two-agent verified (Code transcribes, Chrome re-reads the live source) before it ships. The audit trail is on the methodology page; the per-record provenance is exposed on every REST endpoint.

Transparency over trust. Everything on the site is auditable against a named publisher; if a number is wrong, the fix is shipped and the changelog records the correction by date.

Email: contact@freightutils.com. The MCP server source is public: github.com/SoapyRED/freightutils-mcp. Issues, data corrections, and operator feedback all welcome; errors flagged are investigated within 48 hours.