TL;DR: Use YOUR_HOST.sandbox.treasuryprime.com for all testing and YOUR_HOST.treasuryprime.com for live traffic. Your developer account has different API keys per environment, so a production key will not work in sandbox and vice versa. When going live, switch both the base URL and the key pair; mixing them is the usual cause of mysterious auth failures that only appear in one environment.

## Fix
1. Use YOUR_HOST.sandbox.treasuryprime.com for all testing and YOUR_HOST.treasuryprime.com for live traffic.
   Expected: this specific failure stops.
2. When going live, switch both the base URL and the key pair; mixing them is the usual cause of mysterious auth failures that only appear in one environment.
   Expected: the request routes instead of erroring.
3. Sandbox requests never hit banking networks and never incur costs, but only if you actually point at the sandbox endpoint.
   Expected: this specific failure stops.

## Details
Your developer account has different API keys per environment, so a production key will not work in sandbox and vice versa. Context from the original thread: Official docs (Live and Test Environments): documents the sandbox/production split that trips agents when they hardcode a single base URL or reuse API keys across environments.

## When to use
You hit exactly this: Treasury Prime sandbox and production are separate: different base URLs and different API keys in Treasury Prime.

## When not to use
A different error, or the same symptom in a different tool. This page only covers the failure above.

## Compatibility
Treasury Prime.