APIs, ML, real-time tracking, integration
Technology posts
The engineering posts: how the EcoFreight API actually computes emissions, where ML route optimisation helps and where it loses, real-time vs quarterly emissions data, and honest API comparisons.
5 posts in this category
technology
Freight emissions API vs SDK: when to use which, and what to ask vendors
Most vendors push SDKs because they make better case studies. For many freight integration patterns the raw REST API is what you actually want. When SDK is the right call, when it is not, and the six questions to ask any emissions vendor before signing.
technology
Freight emissions API comparison 2026 — EcoFreight vs Climatiq vs Cloverly vs BigMile
I work on EcoFreight. Honest, biased-but-disclosed comparison of the freight emissions APIs I have integrated against — methodology, public pricing, latency, primary-data ingestion, and where each one actually wins.
technology
How ML Route Optimisation Cut Emissions 10-15% on Asia-Europe Lanes — and Where It Still Loses to Human Planners
I have shipped ML route optimisation into production on two carriers. The honest number is 10-15% on Asia-Europe — not 23%, not 50%. Here is what the model does, where it loses to a planner (cold start, port strikes, off-distribution typhoons), and what actually goes in the request.
technology
From Spreadsheets to Real-Time: What Changes When You Automate Emission Tracking
Most companies still calculate freight emissions in Excel, quarterly, with 3-month-old data. An API-based approach gives you per-shipment numbers in milliseconds. We compare the two workflows and what switches when you make the move.
technology
Inside Our Emission Engine: How EcoFreight Turns a Route Into a Carbon Number
A single API call to EcoFreight calculates WTW emissions in under 50ms. Here's what happens behind the scenes — from geocoding origins to selecting emission factors to handling data quality tiers.