rexai-image-generation

RexAI Image Generation

Use RexAI's async image API to create images and return usable local files.

Quick Workflow

1. Use REXAI_API_KEY for authentication. If it is missing, teach the user how to configure it for their platform before running the job. Read it live from the OS on Windows (powershell [Environment]::GetEnvironmentVariable('REXAI_API_KEY','Machine')) — a bash/PowerShell session started before the key was set holds a stale snapshot.
2. Choose the product ID (verify against the current instance's product list with one probe; these IDs have drifted before):
   • Text-to-image: gpt-image-2.
   • Image-to-image: the same gpt-image-2 product with the -Image parameter — the relay selects the image-to-image route when the body carries images. gpt-image-2-i2i does NOT exist (404 image_product_not_found); do not use it.
3. Pick the zero-install executor for the user's platform:
   • Windows/Codex: use scripts/rexai-image.ps1; it only needs built-in PowerShell/.NET.
   • macOS/Linux: use scripts/rexai-image-macos.sh; it uses common system tools (bash, curl, perl, base64).
4. Use scripts/rexai-image.mjs only when Node is already available.
5. Report the local file path, job id, source URL if present, and expiry time if present.

Read references/api.md when you need endpoint details, supported sizes, error codes, or examples.

API Key Setup

First check whether the key is already available. Do not print the key value:

if ($env:REXAI_API_KEY) { "REXAI_API_KEY is set" } else { "REXAI_API_KEY is missing" }

If it is missing, tell the user to choose one setup path:

Windows PowerShell, current session only:

$env:REXAI_API_KEY = "cr_xxx"

Windows PowerShell, persistent for new terminals:

setx REXAI_API_KEY "cr_xxx"

macOS/Linux, current shell only:

export REXAI_API_KEY="cr_xxx"

macOS zsh, persistent for new terminals:

printf '%s\n' 'export REXAI_API_KEY="cr_xxx"' >> ~/.zshrc