Environments
Test and live, and why they can't cross.
Every agent is either test or live, fixed when you create it. Every key is too: gsk_test_ keys reach only test agents and gsk_live_ keys only live ones. A mismatch returns 403 environment_mismatch, so a production server can't call a test agent by mistake, and a script on a laptop can't touch production.
- Build and try things with test agents and test keys.
- Create a separate live agent for production, with its own policy.
- Both environments use the same credit balance; usage is charged the same.
NoteGasket has two environments. Separate staging and development environments are not available; use separate test agents for each.
Something wrong or missing? Tell us · Stuck? Help center