Latency benchmark
Real numbers. We ran curl against the Warp quote endpoint 5 times and took the median. The v1 agent API wraps the same upstream, so latency is identical.
190msMedian quote response time (LA to NYC, 2 pallets)How we measured
curl -s -o /dev/null -w "%{time_total}" \
-X POST https://wearewarp.com/api/freight-quote \
-H "Content-Type: application/json" \
-d '{"originZip":"90001","destinationZip":"10001","pallets":2}'Raw results
Run 1: 0.243s
Run 2: 0.165s
Run 3: 0.190s
Run 4: 0.205s
Run 5: 0.182s
Median: 0.190s (190ms)Comparison
| Provider | Quote latency | Self serve API | Source |
|---|---|---|---|
| Warp | 190ms (measured) | Yes | This page |
| Freightos | Requires sales call* | No self serve* | freightos.com/freight-tools |
| Uber Freight | Requires sales call* | No self serve* | uberfreight.com/shipper |
| Flock Freight | Requires sales call* | No self serve* | flockfreight.com |
* Competitor data unverified. "Requires sales call" means no publicly accessible self serve API or latency documentation was found as of April 2026. If you have data, let us know at support@wearewarp.com.
Methodology
Five sequential requests from a MacBook on residential WiFi in Los Angeles. POST to /api/freight-quote with origin 90001, destination 10001, 2 pallets. Measured with curl's %{time_total}. Median selected to reduce outlier impact.