
Use different Imagild API keys for your development and production applications, but do not confuse separate keys with separate accounts, wallets, or sandbox permissions. Both keys still call the live Imagild API under their owning account. A safe development setup uses offline fixtures for repeated tests and a deliberately approved live smoke test when needed.
Key Takeaways
- Name keys by application environment and store their values outside source control.
- Keys on one account share membership, points, and per-account request limits.
- Switching an environment must preserve existing operation and task IDs, not regenerate completed work.
Write an environment matrix before copying secrets
An application's own environment names are useful operational labels. They are not evidence that Imagild provides an isolated sandbox.
| Application environment | Credential policy | Typical work |
|---|---|---|
| Local unit tests | No live key | Fixed catalog, accepted-task, failure, and content fixtures |
| Development integration | Named development key | Approved access check or controlled live generation |
| Production | Named production key | Customer-approved generation and authenticated downloads |
| Incident investigation | Operator-controlled access | Read existing task records and sanitized diagnostics |
Create the named keys through the API console. Record their owner, creation date, expiry, application environment, and secret-store reference. Do not put the secret itself into this matrix.
Replicate's API-token guidance also recommends environment separation and replacing exposed tokens. That is an operational pattern to adopt; it does not grant Imagild keys another provider's scopes or features.
Keep configuration explicit
A minimal backend deployment can receive:
APPLICATION_ENV=production
IMAGILD_API_BASE=https://imagild.com/api/relay/v1
IMAGILD_API_KEY=<injected by the deployment secret store>
The angle-bracketed value describes a secret-store action, not a usable credential. Never expose the value through a browser-prefixed environment variable, a checked-in configuration file, or a frontend error response.
Use the same published API base in each approved live environment. To test without generating media, point your test harness to a fixture server you control and clearly label its responses as simulated. Do not invent a separate Imagild sandbox hostname or assume that a key named “test” changes billing.
Budget shared resources deliberately
Separate keys do not create separate pools of points. A development generation on the same account uses points that production could otherwise use. At current image rates, ten 4K experiments use 200 points; the model hub shows each tier before you submit.
The current request limits are also per account: ten generation/upload writes and 120 reads per minute. A development polling loop can therefore interfere with another application using a different key on that account. Place development limits in your own application and schedule controlled experiments outside important production runs.
If you need different ownership or billing boundaries, settle the account arrangement before integration. Do not represent key names as team-role enforcement or read-only permissions.
Validate a deployment without creating duplicate work
Before switching production configuration, confirm the secret-store entry belongs to the intended account, check membership and expiry in the console, and make an authenticated GET /models request. The catalog verifies access and currently offered models; it does not reveal a complete ownership or billing audit.
Then inspect your own operation table. Keep pending operation IDs, idempotency keys, request parameters, and task IDs through the deployment. Configuration changes should not cause a worker to treat an accepted job as new.
OWASP's REST security checklist provides the independent security principle: authenticate and authorize protected resources rather than trusting a convenient environment label.
Define a rollback and cleanup decision
Keep a record of which deployment reads which secret-store reference. If a deployment fails before a new generation is intended, restore configuration and continue reading saved tasks instead of submitting replacements.
Revoke development keys no longer needed, and retain only sanitized logs. A record containing an operation ID, task ID, model, resolution, HTTP status, and error request ID is more useful than one containing a full Authorization header. The points planning guide and failed-job next-action guide help keep resource use separate from deployment troubleshooting.
Related tasks
- Imagild Points, Resolution and Jobs: Plan a Creation Before You Spend
- What Should You Check Before Retrying a Failed Image or Video Job?
Sources and scope
- Imagild API console and integration guide: Product entry point and current API access, credential and task integration instructions; detailed facts also cross-checked against the 2026-10-28 repository contract.
- Imagild model hub: Current public media model choices and resolution-based point prices; not evidence of model equivalence, pixel quality or measured uptime.
- OWASP REST Security Cheat Sheet: General REST security principles: endpoint authorization, secure handling of credentials, input validation and response content-type checks. Does not define Imagild product behavior.
- Replicate API token security: General guidance for separating credentials, storing them through environment configuration and revoking exposed tokens. No Replicate platform features or guarantees are attributed to Imagild.
Product instructions were checked against the current Imagild API contract and the public model catalog. Code, budgets and acceptance checks are illustrative; this article does not claim a new paid generation test, an uptime measurement, a search-volume study or a ranking of AI citations.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: Original Imagild product screenshot captured on 28 October 2026; model availability and prices may change. This image is not an API response or a performance benchmark.