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.Documentation Index
Fetch the complete documentation index at: https://docs.nexusfeed.dev/llms.txt
Use this file to discover all available pages before exploring further.
Carrier overview
| Field | Value |
|---|---|
| SCAC code | AVRT |
| Full name | Averitt Express |
| Headquarters | Cookeville, TN |
| Coverage | Southeast-focused, expanded national |
| DOE diesel price | Yes |
| Historical weeks available | Current week only (upstream JSON endpoint returns only /api/fuel_surcharges/current) |
| Extraction method | api_mirror |
| Cache TTL | 7 days |
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 cleanapi_mirror response with a full _verifiability block either way.