AI/ML API gateway details

A multi-model API aggregation platform; the docs list an OpenAI-compatible interface, model list, and image/audio/video APIs, ideal for overseas developers wanting unified access.

Best for: For developers who need one key to call many kinds of models and can use overseas billing.

Current status

Reachable

Latency reference

910 ms

/models check

Model list in the docs

Last verified

2026-07-01

Status notes

An overseas multi-model aggregator, suited to developers who can use overseas billing.

Pricing mode

Billed per model and API type; prices and available models per the official pricing page.

Price tags

Standard price, Pay-as-you-go

Free quota

May offer trial credit; refer to the dashboard after signup.

Usually you create an API key in the platform console, then replace the SDK's baseURL, model name, and auth details per the docs. Test streaming, function calling, error codes, and rate limits before launch.

import OpenAI from "openai";

const client = new OpenAI({
  apiKey: process.env.AI_GATEWAY_API_KEY,
  baseURL: "see the platform docs"
});

const response = await client.chat.completions.create({
  model: "gpt-4.1-mini",
  messages: [{ role: "user", content: "Test one call through an AI gateway." }]
});

• Supported models: OpenAI, Claude, Gemini, DeepSeek, Grok, Qwen, Midjourney, Flux and more.
• Capabilities: OpenAI-compatible, Streaming, Function calling, Image generation, Speech-to-text, TTS, Embeddings, Balance query.
• Documentation completeness: High; editorial stability score 4.1 / 5.

• Overseas platforms aren't always friendly to China networks and payments; verify rate limits and refund rules before large-scale use.
• Third-party relay pricing, models, and availability can change, so re-check them periodically.

Is AI/ML API compatible with the OpenAI API?

This entry is marked as supporting the OpenAI-compatible format, but the exact base_url, model names, and parameters still follow the official docs.

Is AI/ML API ready for production?

Run a small-traffic load test, rate-limit test, and error-code test first, and confirm the billing rules; keep a backup provider for important workloads.