OpenAI-compatible integration
Keep the existing SDK pattern. Replace the Base URL and platform key to reduce migration effort.
client = OpenAI({
apiKey: API_ZENO_KEY,
baseURL: https://api.api-zeno.com/v1
})
Key
Model route
Billing record
A model API aggregation service for developers, creators, and teams.
Bring OpenAI-compatible calls, mainstream models, and unified billing into one gateway so integration, routing, and accounting stay connected.
Keep the existing SDK pattern. Replace the Base URL and platform key to reduce migration effort.
client = OpenAI({
apiKey: API_ZENO_KEY,
baseURL: https://api.api-zeno.com/v1
})
Key
Model route
Billing record
GPT, Claude, Gemini, DeepSeek, and other models can be selected, retried, and observed through one entry point.
Collect cost by model, group, and token usage while keeping request logs and cost signals visible.
The code block now belongs to integration: copy your existing SDK setup, point baseURL to api-zeno, then observe route, latency, and token usage.
https://api.api-zeno.com/v1
Create an account and use the free trial to complete your first request and validate the basic integration.
Use the model marketplace to review capability tags, status, and reference pricing, then choose the right model for the task.
Replace the original OpenAI SDK Base URL with https://api.api-zeno.com/v1, then call it with your API Key.
Use token-based billing for low-frequency or variable usage, and subscriptions for stable calls.
import OpenAI from "openai";
const client = new OpenAI({
apiKey: process.env.API_ZENO_KEY,
baseURL: "https://api.api-zeno.com/v1",
});
const completion = await client.chat.completions.create({
model: "gpt-4o-mini",
messages: [{ role: "user", content: "Hello api-zeno" }],
});200 OK
gpt-4o-mini
842ms
1,284
The API gateway supports backend calls, content generation, quota governance, billing traces, and supplier operations.
Text, image, video, and audio jobs can enter one creator workspace from the console.
Text
Image
Video
Audio
Quota, logs, permissions, and supplier boundaries live inside the same management view.
Common models are presented together across low $ consumption chat, strong reasoning, code generation, and multimodal capabilities, making it easier to choose by provider, capability tags, $ reference prices, and business scenario.
OpenAI
gpt-4o
Input reference price
2.50 $ / 1M Token
Output reference price
10.00 $ / 1M Token
Recommended scenario
Best for production scenarios that need stable general capability, image-text understanding, and complex business assistants.
OpenAI
gpt-4o-mini
Input reference price
0.15 $ / 1M Token
Output reference price
0.60 $ / 1M Token
Recommended scenario
Best for support routing, content summarization, lightweight Q&A, and high-concurrency calls with low $ consumption.
Anthropic
claude-sonnet-4
Input reference price
3.00 $ / 1M Token
Output reference price
15.00 $ / 1M Token
Recommended scenario
Best for long document understanding, code collaboration, knowledge-base Q&A, and high-quality writing.
gemini-2.5-flash
Input reference price
0.30 $ / 1M Token
Output reference price
2.50 $ / 1M Token
Recommended scenario
Best for multimodal understanding, real-time Q&A, long-context summaries, and fast prototype validation.
Prices shown here are reference examples for the website. Model availability, reference prices, and billing details are subject to the platform display.
Pay for what you use. Billing is based on actual token consumption, so occasional calls do not require a fixed package upfront. It fits testing, personal development, low-frequency calls, and temporary projects while keeping $ consumption flexible as usage changes.
Validate integration and model behavior first, then choose usage-based billing or subscriptions according to actual call volume.
Input tokens, output tokens, and model $ prices are visible, making per-call $ consumption easier to estimate.
Testing, personal development, low-frequency calls, and temporary projects can all start with usage-based billing.
Billing method
Token usage
18,420
Input tokens
12,480
Output tokens
5,940
Choose usage-based billing for lightweight use, or subscriptions for stable workloads.
Suitable for testing, personal development, temporary projects, and $ consumption-sensitive scenarios. Different models show separate input and output token $ reference prices, making consumption estimation easier by actual usage.
Recharge tiers are website examples. Actual model prices and billing details are subject to the platform display.
Monthly plans suit teams or projects with stable call volume that need fixed quotas and ongoing integration support.
Subscriptions
Subscriptions fit stable calls and fixed quota needs.
New users get this free plan with $7 weekly quota
Weekly quota: $7 / week
Personal plan
Monthly quota: $220 / month
Personal plan
Monthly quota: $600 / month
Choose usage-based billing for lightweight use and subscriptions for stable calls. Amount tiers are website examples only. Model prices and billing details are subject to the platform display.
Quickly understand api-zeno integration, billing, and support.
Usage-based billing is usually calculated by actual token usage and fits testing, low-frequency calls, and variable usage. Subscriptions fit stable calls and usually include fixed quotas and related benefits.
No. You can start with a free trial and then choose usage-based or token-based billing according to actual call volume. Subscriptions are better for long-term, stable, or higher-frequency usage.
Pricing is mainly calculated by model and token usage. Input token and output token unit prices may differ by model. The platform display is the final reference.
The model marketplace centralizes available models, capability tags, $ reference prices, and recommended scenarios, helping you choose models by price, capability, and use case.
Yes. In most cases, you only need to replace the Base URL and API Key to keep using your original OpenAI SDK call pattern.
Yes. Model prices can be affected by providers, model capabilities, and platform policies. Website prices are references only, and the platform display is the final source.
For lightweight chat and $ consumption-sensitive scenarios, start with lower-consumption models. For complex reasoning, code, multimodal, or long-text tasks, compare capability tags and prices in the model marketplace.
Contact support to learn about the model marketplace, token-based billing, subscriptions, and integration support.
Complete your first request first, then choose usage-based billing or subscriptions by capability tags, reference pricing, and call scale in the model marketplace.