Environments
One Production API
Archie runs one API at one base URL. There is no separate sandbox host and no isolated test tier. The sandbox or live label you can put on a key is there to help you organize keys, and it changes nothing about how a call behaves.
The Base URL
Every call goes to https://api.heyarchie.ai. That is the production endpoint, and it reaches the live system where your real clients and ledgers live. There is no second host to point a test environment at.
curl https://api.heyarchie.ai/api/v1/skills/clients.list/invoke \
-H "Authorization: Bearer sk_live_xxxxxxxxxxxxxxxx" \
-H "Content-Type: application/json" \
-d '{"limit": 5}'The Sandbox and Live Labels
When you create a key you can tag it sandbox or live, and the default is sandbox. That tag is a label your organization holds in the key's metadata. Archie does not read it, and it grants or restricts nothing. A key tagged sandbox and a key tagged live behave identically against the same production system.
The label is useful for your own bookkeeping. You might tag the key your CI uses as live and a key on a developer's laptop as sandbox, then filter by that tag in the portal. You can change it any time without rotating the key.
Whatever Happened to the Sandbox
Archie used to offer a browser playground where you could try skills without a key. That surface was retired, so if you are looking for it, that is why it is gone. It was never a separate data environment, just a place to experiment, and the sandbox label on a key is unrelated to it.
To rehearse a call safely today, point a scoped key at a test client and read the trace afterwards. Every response carries an x-archie-trace-url, so you can see exactly what Archie did before you run it for real.