> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usenash.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Nash exposes two MCP servers. The docs MCP server at https://docs.usenash.com/mcp searches this documentation and needs no credentials. The Nash MCP server at https://mcp.usenash.com/mcp operates an organization's deliveries and needs a Nash API key. See https://docs.usenash.com/reference/build-with-ai.
> Use the Sandbox environment (https://api.sandbox.usenash.com/v1) for anything that creates or dispatches deliveries during development.

# Environments

> Base URLs and Portal links for the Nash Production and Sandbox environments, and how Sandbox differs from Production.

Nash runs separate Production and Sandbox environments in the US and AU regions; each has its own API base URL and Portal.

| | API Endpoint | Corresponding Nash Portal URL |
| :- | :- | :- |
| **Production** | `https://api.usenash.com/v1` | [`https://portal.usenash.com`](https://portal.usenash.com/) |
| **Production (AU)** | `https://api.ap-southeast-2.usenash.com/v1` | [`https://portal.usenash.com`](https://portal.usenash.com/) |
| **Sandbox** | `https://api.sandbox.usenash.com/v1` | [`https://portal.sandbox.usenash.com`](https://portal.sandbox.usenash.com/) |
| **Sandbox (AU)** | `https://api.sandbox.ap-southeast-2.usenash.com/v1` | [`https://portal.sandbox.usenash.com`](https://portal.sandbox.usenash.com/) |

## Production

All activity in the Production environment will be billed.

> [!NOTE]
>
> When you're getting ready to launch into production, follow the steps in
> [API key and Org ID](https://docs.usenash.com/reference/generating-api-key-and-org-id.md) to generate your
> production API key. Production API access is enabled by the Nash team — see
> [Production testing](https://docs.usenash.com/guides/production-testing.md) for how to request it.

## Sandbox

The Nash Sandbox is a free and fully-featured environment that allows you to test your integration without sending
requests to actual drivers. All Nash API functionality is supported in the Sandbox environment.

Most endpoints can be immediately tested in Sandbox with no extra configuration. Sandbox pairs simulated fleets with
real provider integrations, and unlike Production, it is free to use. This lets you test your implementation in
"production-like" conditions. Prices in Sandbox do not reflect Production settings.

### Fleet simulators

Nash provides a set of fleet simulators — mock fleets that emulate scenarios you might encounter while using Nash
in a production setting.

Fleet simulators will start the job (delivery) based on the scheduled pickup time.

* FleetSimulator: will cycle through several delivery statuses from `not_assigned_driver` up until `dropoff_complete` (see [Delivery Status](https://docs.usenash.com/reference/delivery-status.md)).
* FleetSimulatorFast: same as FleetSimulator but with a shorter cycling interval between statuses.
* FailingFleetSimulator: will send you a `failed` delivery status.

## Differences between Sandbox and Production

While we try to make the Sandbox environment mimic Production as much as possible, there are a few limitations that
you should be aware of:

* SMS notifications are not triggered in Sandbox.
* The behavior of fleets and fleet simulators is not an indication of how fleets will behave in the real world.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.