FedEx Freight (SCAC: FXFE) hosts its LTL fuel surcharge page behind Cloudflare’s anti-bot protections. Direct httpx requests and residential proxies are rejected before the origin is reached. NexusFeed bypasses the block by routing every FedEx extraction through ScraperAPI’s render API inDocumentation Index
Fetch the complete documentation index at: https://docs.nexusfeed.dev/llms.txt
Use this file to discover all available pages before exploring further.
ultra_premium mode with country_code=us, which presents the request as a residential browser session and loads the page successfully.
Carrier overview
| Field | Value |
|---|---|
| SCAC code | FXFE |
| Full name | FedEx Freight |
| Headquarters | Memphis, TN |
| Coverage | National |
| DOE diesel price | No — FedEx Freight does not publish DOE diesel on its tariff page |
| Historical weeks available | Current week only |
| Extraction method | scraper_api |
| Cache TTL | 7 days |
| Scraping cost | Higher than other carriers due to ScraperAPI ultra_premium + render credits |
Why the render API
FedEx’s fuel surcharge page is served with Cloudflare’s JavaScript challenge. NexusFeed attempted:- Direct httpx → blocked
- Residential proxy → blocked
- Standard ScraperAPI render → partial response, HTML not hydrated
ultra_premium+render+country_code=us→ success
Example request
Example response
FedEx’s
doe_diesel_price_usd is always null. The upstream tariff page publishes the surcharge percentage and effective date, but does not disclose the DOE #2 diesel trigger. Confidence is scored against effective_date and fuel_surcharge_pct only.Use cases
- Auditing FedEx Freight LTL invoices for the current week.
- Quoting shipments moving on FedEx Freight where a live surcharge is required.
- Including FedEx in multi-carrier carrier selection for lanes where it is a realistic option.