Skip to main content
Averitt Express (SCAC: AVRT) publishes its LTL fuel surcharge through a hidden JSON endpoint used by the carrier’s own web frontend. NexusFeed calls that endpoint directly, so the extraction is fast, reliable, and low-overhead — no browser rendering required. Averitt is routed through a residential proxy at the httpx layer because its origin is geography-sensitive.

Carrier overview

Why the proxy matters

Averitt’s fuel surcharge JSON API rejects traffic from certain cloud egress ranges, including Railway’s EU region. NexusFeed routes Averitt httpx requests through a residential proxy to present a US origin. The proxy is transparent to callers of this API — you’ll see a clean api_mirror response with a full _verifiability block either way.

Example request

Example response

Use cases

  • Auditing Averitt LTL invoices in real time.
  • Quoting southeastern lanes where Averitt is a preferred carrier.
  • Pairing with SEFL and ODFL for multi-carrier southeast benchmarking.