Integrate with the Nash API (REST or GraphQL) using your Nash account credentials.
Create a delivery by submitting pickup location, dropoff location, package details, and timing constraints to the delivery creation endpoint.
Configure a dispatch strategy in your Nash account: choose Preferred Order to define a prioritized list of providers, or Dynamic Dispatch to let Nash's algorithm balance cost, speed, and reliability automatically.
Nash attempts delivery with the top-ranked provider; if that provider fails or is unavailable, Nash automatically falls back to the next eligible provider without requiring a new API call from your side.
Subscribe to Nash webhook events to receive real-time status updates including driver assignment, pickup, and dropoff confirmations.
Use Nash's analytics and delivery history endpoints to monitor provider performance and adjust your fallback configuration over time.
Known gotchas
Provider availability varies by geography; configure your provider list in Nash to only include carriers that actually operate in the pickup and dropoff zip codes — Nash does not prevent you from listing a provider with no local coverage.
Fallback to a secondary provider adds latency; communicate realistic delivery time estimates to end customers that account for potential provider-switching delays.
Nash's platform is designed for businesses with recurring delivery volume; pricing and provider access tiers may require a commercial agreement — confirm coverage and rates before building production workflows.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp