Build quote, landed-cost, and logistics-agent workflows on carrier-backed freight intelligence instead of scraped spreadsheets or stale PDFs.
Start with the Shipping Rate APIREST API + MCP access • x402 pay-per-call support • 26,303 verified D&D tariffs • 9 shipping lines in 195 countries
The ShippingRates API exposes freight intelligence for teams that need more than a single ocean-rate lookup. It combines carrier-backed D&D tariffs, local charges, port intelligence, transit schedules, surcharges, and route context in one public API surface.
Each public page links back to the ShippingRates methodology because the API is only useful when users can understand where the numbers came from. Source URLs, carrier files, and validation outcomes are preserved through the ingestion flow before data becomes customer-facing.
Freight forwarders use the API to quote faster without manually checking every carrier table. SaaS builders use it to add shipping intelligence to procurement, trade-finance, and supply-chain products. AI agents use it to answer operational questions with structured data instead of free-text guesses.
The first-party API is the canonical path for production workloads. Apify remains useful for discovery, while the direct API and MCP server are the surfaces designed for serious integrations.
Shipping cost workflows are risky when a quote engine silently invents missing inputs. ShippingRates keeps unsupported tariff shapes fail-closed: if a source cannot be represented safely, it is recorded as an acquisition or validation issue instead of being pushed into the API.
That conservative approach makes the API better suited for commercial workflows where a wrong D&D slab, local charge, or port scope can become a real customer dispute.
Every growth page in this cluster points to the ShippingRates methodology because carrier-backed freight intelligence needs visible provenance. The product is strongest when users can see how source data is acquired, validated, promoted, and limited.