Image Generation API

When using the GetToken relay service, Codex cannot generate images directly through the built-in client ImageGen.

Built-in ImageGen needs a key that can connect directly to the OpenAI Images API. GetToken provides a relay service API key, and that key does not take over the direct ImageGen path inside Codex.

Image generation with the GetToken relay service must use the gettoken-imagegen Skill.

Install ItCopy Anchor Link

Open the Stable Image API console, choose macOS or Windows, copy the one-line install command, run it, and restart Codex.

Already installed? Run the same command again to update to the latest version. Your config and task history are preserved. You can also let Codex run <skill>/bin/<platform>/gettoken-imagegen update.

RequirementCopy Anchor Link

When generating images in Codex, image generation tasks must be handled by gettoken-imagegen.

Do not use:

• Built-in Codex ImageGen
• Image generation paths that depend on an official OpenAI direct key

Use:

• gettoken-imagegen Skill
• GetToken API Key
• OpenAI-compatible Images API endpoint

Configure the EndpointCopy Anchor Link

The installer writes the image API key and stable image endpoint into the skill configuration. Do not expose the API key in source code, screenshots, or public commands after installation.

Install LocationCopy Anchor Link

The Skill is installed under ~/.agents/skills/gettoken-imagegen. Run the install command on the same machine where Codex runs.

TroubleshootingCopy Anchor Link

Why not use built-in ImageGen directlyCopy Anchor Link

Built-in Codex ImageGen requires a key that can connect directly to the OpenAI Images API. When using the GetToken relay service, that direct path does not work, so gettoken-imagegen must handle image generation.

Codex Cannot Find the SkillCopy Anchor Link

Confirm the Skill is installed under ~/.agents/skills/gettoken-imagegen, then restart Codex.

Windows Installation Does Not WorkCopy Anchor Link

Confirm that you use the PowerShell install command on native Windows.

Generation FailsCopy Anchor Link

Check:

1. The image API key is configured.
2. You can reach the stable image endpoint.
3. The output directory exists and is writable.

API ReferenceCopy Anchor Link

The GetToken Image Generation API follows the OpenAI Images specification. It supports gpt-image-2, gpt-image-2.5-flare, and gpt-image-2.5-sunburst for text-to-image generation and image edits.

• Base URL: https://api.gettoken.dev/image/v1 (China-optimized: https://api.clawto.link/image/v1)
• Endpoints:
  • POST /images/generations (text-to-image)
  • POST /images/edits (image edits, multipart/form-data)
• Auth: Authorization: Bearer <image API key> (image keys are managed separately)
• Response: identical to the OpenAI spec — images are returned as data[].b64_json with a usage token summary; response_format is always b64_json

Text-to-image /images/generationsCopy Anchor Link

Image edits /images/editsCopy Anchor Link

ExamplesCopy Anchor Link

Text-to-image:

curl https://api.clawto.link/image/v1/images/generations \
  -H "Authorization: Bearer $IMAGE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "gpt-image-2.5-flare",
    "prompt": "A clean product photo on a white desk",
    "n": 1,
    "size": "2048x2048",
    "quality": "high",
    "background": "auto",
    "output_format": "png"
  }'

Image edit:

curl https://api.clawto.link/image/v1/images/edits \
  -H "Authorization: Bearer $IMAGE_API_KEY" \
  -F "model=gpt-image-2.5-flare" \
  -F "prompt=Replace the background with a clean studio backdrop" \
  -F "[email protected]" \
  -F "input_fidelity=high" \
  -F "size=2048x2048" \
  -F "quality=high"

Pricing (per image)Copy Anchor Link

Stable Image tiers are classified by the longest edge of the actual output size returned upstream; only when no recognizable size is returned does the requested size apply. auto, empty, or unrecognized sizes fall back to 2K. The direct API passes custom WxH through, but generation still depends on upstream support for that size.