image2-router

Route text-to-image and image-to-image requests across OpenAI-compatible API providers.

7|Updated May 22, 2026

Search Tags:#automation #image generation #image editing #text-to-image #openai-compatible #api routing

Ready to run

npx skills add https://github.com/Dimen01/skills --skill image2-router

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: image2-router
Source: https://github.com/Dimen01/skills/tree/main/skills/image2-router
Command: npx skills add https://github.com/Dimen01/skills --skill image2-router

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openai, and includes scripts (resource) and assets (resource) components.

What problem does it solve?

This skill solves the fragmentation of OpenAI-compatible image generation APIs by providing a unified routing layer that handles multiple providers, automatic fallbacks, and environment-based secret management.

Core Features & Use Cases

Unified Routing: Automatically routes image generation requests to the best available provider or a user-specified service.
Flexible Transport: Supports both standard SDK calls and direct curl-based transport to bypass common timeout and connectivity issues.
Use Case: When a primary image generation service is down or timing out, this skill automatically retries the request across a configured list of alternative providers like Sakura, FHL, or Riclab.

Quick Start

Use the image2-router skill to generate a high-quality image of a futuristic city using the default provider settings.

Frequently Asked Questions about image2-router

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I route text-to-image generation requests to multiple OpenAI-compatible APIs?▼

To route text-to-image generation requests, you can use a unified routing layer that automatically directs API calls to configured OpenAI-compatible providers like Sakura, FHL, or Riclab. This handles request distribution and provides automatic fallbacks if a primary service fails.

What is the best way to handle OpenAI-compatible image generation API timeouts and connectivity issues?▼

To handle API timeouts and connectivity issues during image generation, implement a routing skill that supports flexible curl-based transport alongside standard SDK calls. This bypasses common network failures and automatically retries requests across alternative configured providers.

Can I use standard SDK calls to switch between different OpenAI-compatible image generation services?▼

Yes, you can use standard SDK calls to switch between OpenAI-compatible image generation services. A unified routing layer facilitates this process, allowing seamless switching between specified services while maintaining robust transport mechanisms for reliable image delivery.

How does automatic fallback work for text-to-image API routing when a provider goes down?▼

Automatic fallback for text-to-image API routing works by sequentially retrying the generation request across a configured list of alternative OpenAI-compatible providers, such as Sakura, FHL, and Riclab, ensuring visual content creation continues even if the primary service is down.

Do I need to manually manage API keys for multiple image generation providers?▼

You do not need to manually manage API keys for multiple providers during routing. The system utilizes environment-based secret management to securely handle credentials for various OpenAI-compatible image generation services automatically.

What are the limitations of using a unified routing layer for image generation APIs?▼

The main limitation of a unified routing layer is its restriction to OpenAI-compatible image generation APIs. It cannot route to services with proprietary API structures and requires pre-configuring alternative providers to ensure successful fallbacks during network timeouts.