English home / Model hubs
English model directory

Model hubs built around real API jobs

Each hub gives you the model ID, use cases, billing boundaries, a minimal request and an acceptance checklist. Use the dashboard for live availability and final billing.

8 English hubs in the first release·Updated 2026-09-27

Image APIs

Grok Imagine Image

Fast creative image generation, prompt variations and reference-image workflows.

Open hub

Gemini 3.1 Flash Image

Multimodal image generation and editing for product, social and batch creative work.

Open hub

Video APIs

Seedance 2.5

Async video tasks with a separate Seedance account and billing boundary.

Open hub

Grok Imagine Video

Prompt-to-video and image-to-video workflows with task status and download checks.

Open hub

Chinese model APIs

DeepSeek V4 Pro

Reasoning, coding and long-context tasks through an OpenAI-compatible request shape.

Open hub

Qwen 3.7 Max

Multilingual reasoning, structured outputs and tool-oriented workloads.

Open hub

GLM-5.3

Chinese-language workflows, coding and structured task automation.

Open hub

Kimi K3

Long-context reading, research notes and Chinese-English research workflows.

Open hub

Choose a starting point

Use the hub that matches the output you need to ship, then run the same acceptance test on two candidates. The model name is only a starting hypothesis; quality, latency, failure behavior and ledger cost decide whether it belongs in production.

Need to deliverStart withFirst comparison
Product or social imagesGrok Imagine Image or Gemini 3.1 Flash ImagePrompt adherence, usable-asset rate and cost per accepted image
Short video clipsSeedance 2.5 or Grok Imagine VideoTerminal success, duration, download reliability and final task charge
Chinese reasoning or codeDeepSeek V4 ProFixed test set, engineering acceptance and input/output usage
Structured multilingual outputQwen 3.7 Max or GLM-5.3Schema validity, retry rate and language consistency
Document-heavy researchKimi K3Constraint coverage, source fidelity and context cost

What every hub contains

Each page is written as a deployment decision record: exact model ID, supported workflow assumptions, billing unit to verify, a minimal request, failure boundaries, an acceptance checklist and questions that commonly cause duplicate requests or misleading cost comparisons.

Availability and final billing are always controlled by the live dashboard. Public pages explain how to test a route; they do not replace provider documentation or promise a fixed quality, rate or latency.