API reference
Complete endpoint documentation for text, image, and video models with request examples, response fields, and parameter descriptions.
Browse model catalogOPENAI-COMPATIBLE API & CLIENT SETUP
Connect your app, Codex, or Claude Code to LanoX with our comprehensive API docs. Add your API key and choose an exact model ID from the live catalog — everything you need to integrate multi-model AI is in one documentation hub.
Our API documentation covers everything from the first request to production-ready integration. Browse the reference, follow step-by-step client guides, and find answers in the FAQ — all built to help you ship faster with LanoX's multi-model AI API.
Complete endpoint documentation for text, image, and video models with request examples, response fields, and parameter descriptions.
Browse model catalogStep-by-step setup docs for Codex, Claude Code, and CC Switch — with exact base URLs, model IDs, and configuration checks.
View Codex guideVerify your first API call in minutes. Check the requested model, actual result, usage record, and final charge in the console.
Create an API keyAnswers to common questions about OpenAI compatibility, base URLs, model IDs, and how to validate your first request.
Contact supportText supports OpenAI Compatible and Claude Messages. Image and video APIs are grouped by provider and task type.
Lists the models available to the current API key. A successful response uses the native OpenAI list shape without a business response envelope.
Jump to examplesgpt-5.6-solNo request parameters
| Field | Type | Required | Description |
|---|---|---|---|
object | "list" | Required | The model-list object type. Always list. |
data | object[] | Required | The array of models available to the current API key. |
data[].id | string | Required | The model identifier to send to model endpoints, such as gpt-5.6-sol. |
data[].object | "model" | Required | The item object type. Always model. |
data[].created | integer | Required | The model creation time as a Unix timestamp in seconds. The server uses the current time when a legacy configuration has no timestamp. |
data[].owned_by | string | Required | The model provider or owner. Defaults to api-transfer-server when provider is not configured. |
data[].supported_endpoint_types | string[] | Required | Compatible endpoint identifiers: chat.completions, responses, and messages. |
data[].provider | string | Optional | The provider identifier. Omitted when it is not present in the model configuration. |
{
"object": "list",
"data": [{
"id": "gpt-5.6-sol",
"object": "model",
"created": 1785196800,
"owned_by": "OpenAI",
"supported_endpoint_types": ["chat.completions", "responses", "messages"],
"provider": "OpenAI",
"display_name": "GPT-5.6 Sol",
"pricing_mode": "token",
"input_mode": "multimodal",
"rpm_limit": 60,
"tpm_limit": 100000
}]
}Use CC Switch to connect Codex or Claude Code. Choose your client for the download link, endpoint, and model setup steps.
Add LanoX through CC Switch, choose a supported Claude model, and keep working in Claude Code.
https://api.lanox.aiConfirm the model ID sent by the client.
Check the returned model and result.
Review tokens, images, or video duration.
Match the charge to the model's real billing unit.
Find the right base URL, model ID, and settings for your client.
It means the service supports one or more request and response formats used by the OpenAI API, often by changing the base URL and API key. Compatibility is endpoint-specific, so verify Chat Completions, Responses, images, and other APIs separately.
Use https://api.lanox.ai/v1 with an API key from your LanoX console. Claude Code uses a different URL format, so follow its client-specific guide.
Use the live model directory or call GET /v1/models with your API key. Copy the exact model ID returned by the catalog into your client configuration.
The current Codex setup guide uses https://api.lanox.ai/v1. Confirm the API mode and model ID in the matching client guide and live model directory.
The current Claude Code guide uses https://api.lanox.ai with no /v1 path and no trailing slash. It follows a different API convention from Codex.
Check the requested model ID, returned result, token or media usage, and final charge. Then review the request-level record in the console usage details.
Create an API key, copy an exact model ID from the live catalog, and follow the guide for your client.