
If an Imagild API key appears in a public repository, browser bundle, screenshot, or shared log, treat it as exposed and revoke it through the API console. Removing the visible copy is not enough: someone may already have copied it. Replace the credential through a secure deployment process, then investigate accepted work without submitting duplicate generations.
Key Takeaways
- Revoke the exposed key; deleting a post or committing a redaction does not invalidate a copied secret.
- Replacement keys must stay on the server and outside the incident report.
- Revocation blocks later authenticated use of that key; it is not a cancellation or automatic refund for previously accepted work.
Contain access before reconstructing the incident
Identify the affected account and key using its name or non-secret prefix in the console. An authorized operator should revoke the exposed credential and record the time. Avoid reproducing the full value in tickets, chat messages, or screenshots intended to document the incident.
Then install a newly generated key in the application's secret store and deploy the updated configuration. If production depends on the exposed key, coordinate the change as an incident rather than extending its life merely for convenience.
Replicate's API-token security guidance independently recommends revoking an exposed token and using environment configuration. Apply that containment pattern to Imagild, while following Imagild's own account and key controls.
Search for copies without spreading the value
Review the places your application controls: repository history, CI output, deployed frontend assets, error reports, shell recordings, and shared runbooks. Remove or restrict exposed copies according to your organization's incident process.
Check your logging configuration before running more diagnostics. Logging a request object can capture its Authorization header even when application messages look harmless. The OWASP REST Security Cheat Sheet explains why sensitive credentials should not travel in URLs; the same practical caution applies to public diagnostic output.
| Record to retain | Record to exclude from shared reports |
|---|---|
| Key name or non-secret prefix | Complete Bearer value |
| Revocation and deployment times | Replacement credential |
| Application operation and task IDs, where appropriate | Unnecessary customer prompts or private media |
| Sanitized error code and request ID | Raw request headers or unrelated account data |
Task identifiers can still be sensitive within your organization. Share only what the receiving support or security team needs.
Verify access deliberately
Confirm the key is marked revoked in the console. A carefully controlled access check using the retired credential should no longer authenticate; GET /models avoids creating another paid task. Do not paste the old key into a public command example or a browser URL to perform this check.
Validate the replacement separately. It still needs an eligible account with active membership. A new credential does not repair expired membership, and a temporary 503 does not by itself prove that the retired key was revoked correctly.
Check the actual error response and the console state together rather than treating any failure as successful containment.
Reconcile work that may already exist
Review your application's operation log for requests accepted during the exposure window. Preserve each idempotency key, parsed request parameters, returned task ID, and last known status. The API console's last-used timestamp is useful context, not a complete record of every request.
Revoking a key does not establish that an earlier generation stopped. A valid replacement key under the same authorized account can be used to inspect owned tasks. Avoid creating a new operation simply because the previous deployment no longer authenticates.
For tasks marked failed or unknown, use the failed-job decision process. Confirmed failure and uncertain upstream submission have different billing implications; do not promise an immediate point release or a cash refund based solely on credential exposure.
Close the incident with a narrower secret path
Document where the exposure began, where the replacement now lives, which deployments were updated, and what evidence verified the old key's retirement. Record any unresolved tasks for follow-up with sanitized identifiers.
Use the points and job guide when reconciling the wallet, but keep financial conclusions tied to actual task and balance records. Imagild's revocation and idempotency mechanisms help limit follow-on mistakes; they do not prove that no unauthorized request occurred before revocation.
Related tasks
- What Should You Check Before Retrying a Failed Image or Video Job?
- Imagild Points, Resolution and Jobs: Plan a Creation Before You Spend
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.
- 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.