Execute Ideogram production deployment checklist and rollback procedures. Use when deploying Ideogram integrations to production, preparing for launch, or implementing go-live procedures. Trigger with phrases like "ideogram production", "deploy ideogram", "ideogram go-live", "ideogram launch checklist", "ideogram production ready".
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Complete pre-flight checklist for deploying Ideogram image generation to production. Covers API key management, timeout configuration, image persistence, error handling, monitoring, and rollback procedures.
.env file)https://api.ideogram.ai (no trailing slash)Api-Key header used (not Authorization: Bearer)is_image_safe response field checked before displaying to usersasync function ideogramHealthCheck(): Promise<{
status: "healthy" | "degraded" | "down";
latencyMs: number;
details: string;
}> {
const start = Date.now();
try {
const response = await fetch("https://api.ideogram.ai/generate", {
method: "POST",
headers: {
"Api-Key": process.env.IDEOGRAM_API_KEY!,
"Content-Type": "application/json",
},
body: JSON.stringify({
image_request: {
prompt: "health check: simple blue dot",
model: "V_2_TURBO",
magic_prompt_option: "OFF",
},
}),
signal: AbortSignal.timeout(30000),
});
const latencyMs = Date.now() - start;
if (response.ok) {
return { status: "healthy", latencyMs, details: "Generation succeeded" };
}
if (response.status === 429) {
return { status: "degraded", latencyMs, details: "Rate limited" };
}
return { status: "down", latencyMs, details: `HTTP ${response.status}` };
} catch (err: any) {
return { status: "down", latencyMs: Date.now() - start, details: err.message };
}
}set -euo pipefail
echo "=== Ideogram Pre-Flight Checks ==="
# 1. Verify production key
STATUS=$(curl -s -o /dev/null -w "%{http_code}" \
-X POST https://api.ideogram.ai/generate \
-H "Api-Key: $IDEOGRAM_API_KEY" \
-H "Content-Type: application/json" \
-d '{"image_request":{"prompt":"deploy check","model":"V_2_TURBO","magic_prompt_option":"OFF"}}')
if [ "$STATUS" != "200" ]; then
echo "FAIL: API returned $STATUS"
exit 1
fi
echo "PASS: API key valid (HTTP $STATUS)"
# 2. Verify image download
IMAGE_URL=$(curl -s -X POST https://api.ideogram.ai/generate \
-H "Api-Key: $IDEOGRAM_API_KEY" \
-H "Content-Type: application/json" \
-d '{"image_request":{"prompt":"deploy check","model":"V_2_TURBO","magic_prompt_option":"OFF"}}' \
| jq -r '.data[0].url')
DL_STATUS=$(curl -s -o /dev/null -w "%{http_code}" "$IMAGE_URL")
echo "PASS: Image download works (HTTP $DL_STATUS)"
echo "=== All pre-flight checks passed ==="| Alert | Condition | Severity |
|---|---|---|
| API Unreachable | Health check returns down | P1 |
| Auth Failure | Any 401 response | P1 |
| Rate Limited | >5 consecutive 429 responses | P2 |
| Slow Generation | P95 latency > 30 seconds | P2 |
| Credits Low | Balance below $10 | P2 |
| Safety Rejections | >10% of prompts rejected | P3 |
set -euo pipefail
# If Ideogram is down or producing bad results
# 1. Enable fallback mode (disable image generation, show placeholders)
kubectl set env deployment/app IDEOGRAM_ENABLED=false
kubectl rollout restart deployment/app
# 2. Verify fallback is active
curl -s https://app.example.com/health | jq '.services.ideogram'
# 3. Re-enable when resolved
kubectl set env deployment/app IDEOGRAM_ENABLED=true
kubectl rollout restart deployment/app| Alert | Condition | Action |
|---|---|---|
| API Down | 5xx or timeout | Enable fallback, notify on-call |
| Key Revoked | 401 | Rotate key, update secrets |
| Credits Empty | 402 | Top up billing, pause batch jobs |
| Rate Flood | 429 sustained | Reduce concurrency, queue jobs |
For version upgrades, see ideogram-upgrade-migration.
4dee593
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.