Developer FAQ

Sign up at wearewarp.com/agents/account. Add a payment card for production bookings, then copy the wak_live_* API key shown after setup.

https://www.wearewarp.com/api/v1 for the public self-serve freight API.

Pass your key in the Authorization header as a Bearer token: Authorization: Bearer wak_live_YOUR_KEY. Content type is JSON.

Quote endpoints are free — POST /api/v1/freight/quote, /api/v1/ltl/quote, /api/v1/van/quote, /api/v1/box-truck/quote, /api/v1/ftl/quote, and the public /api/ltl-rates endpoint never charge. Only POST /api/v1/freight/book and /api/v1/book charge the card on file.

Any language that can make HTTP requests. REST API with JSON. Python, Node.js, Go, Java, Ruby, Rust, or any other language.

No. The API works with plain HTTP requests. Warp provides client libraries for Python and Node.js if you prefer.

Most developers can get a first quote in minutes. A production integration usually starts with quote, book, and track, then expands after payment, account, and exception workflows are confirmed.

The public self-serve quote endpoint allows 60 quote requests per agent per hour. Booking allows 10 booking attempts per agent per hour. Enterprise accounts can request higher limits.

The canonical public self-serve docs are at wearewarp.com/freight-api. The machine-readable OpenAPI 3.1 spec is at wearewarp.com/.well-known/openapi.json.

wearewarp.com/agents/cli for the full quickstart and 20-command reference. The package is @warpfreight/cli-agent on npm.

POST /api/v1/freight/quote with pickupZip, deliveryZip, pickupDate, pallets, and weightPerPallet. It returns a quoteId, carrier, rate, transitDays, and mode.

Minimum: origin zip, destination zip, item dimensions, weight, and quantity. Optional: freight class, vehicle type, accessorial services.

The self-serve path is LTL-first. Broader cargo van, box truck, FTL, and multi-carrier workflows are available for approved production accounts and should be confirmed before launch.

Quotes are valid for a set window (typically 24 to 48 hours). The expiration is included in the response.

Yes. No fuel surcharges, no hidden accessorial fees, no terminal handling charges. The quoted rate is what you pay.

Temperature-controlled workflows are available for approved production accounts. They are not part of the public self-serve quote request shape today.

Not for most shipments. Warp auto-classifies based on dimensions and weight. You can specify freight class if you know it.

Multi-stop shipments are an approved-account workflow, not a public self-serve endpoint in this repo today. Talk to Warp before building against it.

LTL, box truck, and cargo van are priced per pallet. The rate includes pickup, cross-dock handling (for LTL), line haul, and delivery.

Yes. Get the all inclusive rate via API, add your margin, charge your customers your price.

POST /api/v1/freight/book with the quoteId from /api/v1/freight/quote plus pickup and delivery address/contact details. Production booking charges the card on file.

Warp dispatches a local 3rd-party carrier through the Warp driver app. You receive a shipment ID and tracking number.

Yes, before pickup. Contact Warp support or use the cancellation endpoint.

Modifications to pickup date, contact info, and instructions are supported before the shipment is picked up.

Yes. Street address, city, state, zip code, and contact name/phone for both pickup and delivery.

Yes. Call the booking endpoint for each shipment. For high-volume batch operations, contact Warp for bulk booking support.

Standard business hours (8am to 5pm) by default. Appointments and custom windows can be specified.

Yes. The API supports fully autonomous operation. Set business rules (max spend, required transit, preferred modes) and let agents book within parameters.

GET /api/v1/freight/track/{shipmentId} with the shipmentId or tracking number returned by booking. It returns the current tracking payload as structured JSON.

PICKED_UP, SCANNED_IN, DEPARTED, IN_TRANSIT, ARRIVED, SCANNED_OUT, DELIVERED, EXCEPTION.

Yes. Local 3rd-party carriers use the Warp driver app with live GPS, barcode scan events, proof of delivery photos, and e-signatures.

Webhooks are not part of the public self-serve API yet. Use the tracking endpoint for polling. Approved enterprise accounts can request event push workflows through Warp.

Event type, timestamp, location, shipment ID, and event-specific data (scan details, GPS coordinates, delivery photo URL).

For public self-serve integrations, yes: poll GET /api/v1/freight/track/{shipmentId}. Webhook-style event pushes are approved-account workflows.

Our AI backbone, Orbit, monitors every shipment for exceptions: late pickups, missed scans, route deviations, temperature deviations, dwell anomalies, and delivery exceptions. Flags issues before your team has to chase them.

Yes. ELD integrations on all line haul trucks provide continuous location data, not just check calls at pickup and delivery.

The public self-serve API is LTL-first for quote, book, and track. Quote calls are free; production bookings require a card on file. Warp also supports truckload, box truck, and cargo van through approved production workflows.

Yes. Every Warp box truck is 26 foot and liftgate equipped. Temperature controlled units available.

Cartons, cases, parcels, or up to 3 pallets. Same day dispatch available.

Freight is picked up by a local 3rd-party carrier, routed through Warp operated cross-dock facilities, moved via line haul, and delivered by another local carrier. 1 to 2 handoffs vs 3 to 5 at traditional LTL terminals.

Yes for approved production workflows. Temperature control is not part of the public self-serve quote request shape today.

44,000 lbs for a 53 foot dry van.

Not in the public self-serve request shape. The self-serve flow is LTL-first. Approved accounts can request broader mode selection workflows.

$0. No software fees, no per-API-call charges, no integration fees. You pay when you ship.

No. All inclusive pricing. No fuel surcharges, no accessorial fees, no terminal handling charges.

Invoices are not a public self-serve endpoint in this repo today. Approved accounts can use enterprise/customer workflows for invoice data.

Documents are not a public self-serve endpoint in this repo today. Approved accounts can use enterprise/customer workflows for BOL, POD, and related documents.

For recurring volume, a Warp rep builds a custom rate card. Contact Warp at wearewarp.com/book-a-meeting.

Yes, if they can make authenticated HTTP requests and follow your business rules. Point them at wearewarp.com/freight-api and exercise the free quote endpoints before issuing booking calls.

Any tool or agent that can make HTTP requests: Codex, Cursor, Claude via API-capable workflows, LangChain, CrewAI, custom agents, and MCP-compatible tools.

Yes. The @warpfreight/cli-agent CLI outputs JSON by default. AI agents can execute warp-agent ltl/van/box-truck/ftl quote, warp-agent book, warp-agent track as shell commands. After warp-agent login runs once, the saved ~/.warp/config.json handles auth for every subsequent call.

AI that autonomously takes action on freight operations: quoting, booking, tracking, exception handling, and invoice reconciliation. Not just alerts.

Use the Warp API for freight operations and your AI framework (LangChain, CrewAI, custom) for decision logic. See wearewarp.com/ai-freight-agent for a full guide.