Skip to main content
AI Gen Studio API keys are scoped to one environment: sandbox or live. The key prefix shows which environment a request will use.
EnvironmentKey prefixProvider callsCredit usageBest for
Sandboxaigen_test_NoNoIntegration tests, CI, webhook receiver development, Postman collections
Liveaigen_live_YesPaid API creditsProduction or controlled staging with real images

​
Sandbox

Sandbox requests exercise the API contract without processing images through paid providers. Use sandbox to validate:
  • authentication and key handling;
  • request shape and idempotency behavior;
  • status polling;
  • webhook receiver logic;
  • error handling and retry behavior.
Sandbox enhancements are isolated from live enhancements. A sandbox key cannot read live enhancements, and a live key cannot read sandbox enhancements.

​
Live

Live requests create real provider work and consume paid API credits. Live API access requires the account to meet the paid credit requirements documented in Credits. Live is appropriate when:
  • source image URLs are production-ready and publicly reachable;
  • webhook verification is implemented if webhooks are enabled;
  • the integration stores external_id and enhancement ids;
  • retry logic uses idempotency keys correctly;
  • operators can inspect failed items and retry only after fixing inputs.
  1. Build the integration with a sandbox key.
  2. Test single-image requests with each preset.
  3. Test a small batch with 2 to 5 images.
  4. Add webhook verification or polling with backoff.
  5. Run a controlled live batch before enabling the full catalog import.