# NEXT Trucking

> NEXT Trucking ("NEXT") is a FreightTech company founded in 2015 and headquartered in the Los
> Angeles area, operating a digital freight marketplace focused on drayage at the Ports of Los
> Angeles and Long Beach, plus transloading, full-truckload over-the-road and expedited service.
> Its technology core is ATLAS, a proprietary transportation management system covering a container
> from delivery-order ingestion through job creation, dispatch, billing and payout. NEXT was
> acquired by Chicago-based digital freight broker CDL 1000 in February 2024; the brand and its
> applications remain live.

Generated by the API Evangelist enrichment pipeline on 2026-08-26 from this repository and from
live probes of NEXT Trucking's public surface. NEXT Trucking does not publish an llms.txt of its
own: https://nexttrucking.com/llms.txt returns HTTP 404.

## API status — read this first

NEXT Trucking markets API and EDI connectivity but publishes **no developer portal, no API
reference, and no machine-readable contract**. As of 2026-08-26:

- There is no OpenAPI, AsyncAPI, GraphQL SDL, WSDL, .proto, MCP server or A2A agent card on any
  NEXT Trucking host.
- The platform's service gateway, `https://svcs.us-west-2.prod.aws.nexttrucking.com`, is real and
  reachable, and returns HTTP 401 to every anonymous request.
- That gateway serves the Swagger UI asset bundle at `/<service>/swagger-ui/index.html` for 22
  services, but the OpenAPI documents it is configured to render (`/<service>/v3/api-docs`) are
  unrouted and return HTTP 404. The spec generator exists behind the wall; nothing is exposed.
- Integration is therefore a commercial conversation, not a self-service one: contact
  info@nexttrucking.com or (855) 688-6398.

An agent should not attempt to call NEXT Trucking programmatically without credentials issued
under a shipper or carrier agreement.

## Services

- [Drayage](https://nexttrucking.com/services/drayage/): port and rail container drayage, the
  company's core service at the Ports of Los Angeles and Long Beach.
- [Transloading](https://nexttrucking.com/services/transloading/): transfer of freight between
  containers and domestic trailers.
- [Full Truckload](https://nexttrucking.com/services/full-truckload/): over-the-road FTL capacity.
- [NEXTpedited](https://nexttrucking.com/services/nextpedited/): expedited service tier.
- [Our Technology](https://nexttrucking.com/our-technology/): the ATLAS TMS, shipper and carrier
  portals, mobile apps, and the EDI/API connectivity claim.

## Applications

- [Shipper / carrier web app](https://app.nexttrucking.com/signin): authentication entry point.
- [ATLAS operations console](https://atlas.nexttrucking.com/): internal operations SPA.
- [Instant quote](https://quotes.nexttrucking.com/home): per-shipment rate quoting for shippers.

## Identity

NEXT Trucking's applications authenticate against an Auth0 tenant that publishes standard
discovery documents anonymously:

- [OpenID Connect discovery](https://prod-nexttrucking.us.auth0.com/.well-known/openid-configuration)
- [RFC 8414 authorization server metadata](https://prod-nexttrucking.us.auth0.com/.well-known/oauth-authorization-server)

The scopes advertised there are the stock OIDC identity profile (openid, profile, email,
offline_access and related claims). They are not NEXT Trucking API permissions; no resource scope
set is published.

## Company

- [Company](https://nexttrucking.com/company/)
- [Blog](https://nexttrucking.com/blog/) ([RSS](https://nexttrucking.com/feed/))
- [Press](https://nexttrucking.com/press/)
- [Sign up](https://nexttrucking.com/sign-up-hub/)
- [Contact](https://nexttrucking.com/contact-us/)
- [Terms of Service](https://nexttrucking.com/terms-of-service/)
- [Brokerage Terms](https://nexttrucking.com/brokerage-terms/)
- [Privacy Policy](https://nexttrucking.com/privacy-policy/)
- [GitHub organization](https://github.com/NextDeveloperTeam) — exists, zero public repositories.

## Known broken links on the provider's own site

- `https://help.nexttrucking.com/hc/en-us` — TLS handshake fails; no certificate is served for that
  hostname. The underlying Zendesk help center is live at `https://nexttrucking.zendesk.com/hc/en-us`.
- `https://boards.greenhouse.io/nexttrucking` — HTTP 404.
- The Google Play listing for the driver app (`com.nexttrucking.trucker`) — HTTP 404.

## Optional

- [API Evangelist profile artifacts](https://github.com/api-evangelist/next-trucking): the
  authentication, scopes, conformance, well-known, lifecycle, plans and rate-limit artifacts this
  file summarizes, each with the probe evidence behind it.