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
LanoX docs for developersfor the AI models you need
The LanoX docs hub helps you connect OpenAI, Claude, Grok, DeepSeek, and other models to your app, Codex, or Claude Code. Add your API key and choose an exact model ID from the live catalog — everything you need is in one documentation hub.
LanoX docs: everything in one documentation hub
Our LanoX docs cover 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.
Client integration guides
Step-by-step setup docs for Codex, Claude Code, and CC Switch — with exact base URLs, model IDs, and configuration checks.
View Codex guideQuick start & verification
Verify your first API call in minutes. Check the requested model, actual result, usage record, and final charge in the console.
Create an API keyFAQ & troubleshooting
Answers to common questions about OpenAI compatibility, base URLs, model IDs, and how to validate your first request.
Contact supportImage API: lanox-image-2
Asynchronous text-to-image and single-image editing with lanox-image-2: create a task, then poll for the result.
View lanox-image-2 docsTutorials
Integration guides, cost-saving playbooks, model reviews, and creative workflows.
Browse tutorialsAPI reference for text, image, and video
Text 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 examplesAvailable models
gpt-5.6-solRequest parameters
No request parameters
Response 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. |
Response example
{
"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
}]
}Endpoint notes
- The response is filtered by API-key permissions and is not wrapped in a data/code/codeMsg business envelope.
Set up your preferred client
View full documentationUse CC Switch to connect Codex or Claude Code. Choose your client for the download link, endpoint, and model setup steps.
01 / CODEX
Download CC SwitchConnect Codex to LanoX
Use CC Switch to add LanoX, enter your endpoint and API key, and avoid editing configuration files.
- 01Download and openDownload and open Codex and CC Switch. In CC Switch, select Codex and click to add a configuration.
- 02Add and configure LanoXAdd LanoX, enter the API key and model ID, and use https://api.lanox.ai/v1. Select Responses (native) as the upstream format.
- 03Save, enable, and startSave and enable the configuration. Fully quit and reopen Codex, choose a model, and send the first request.
- Integration method
- CC Switch
- Base URL
https://api.lanox.ai/v1- Model ID
- Copy from the model catalog
- Configuration check
- Keep /v1 and select Responses (native) as the upstream format
Check your first response and its cost
Every API call remains clear and traceable.
Requested model
Confirm the model ID sent by the client.
Actual result
Check the returned model and result.
Usage record
Review tokens, images, or video duration.
Final charge
Match the charge to the model's real billing unit.
API and client setup FAQ
Find answers about client setup, model verification, API migration, and compatibility.
01Can I use LanoX with Codex or Claude Code?
Yes. For Codex, use https://api.lanox.ai/v1 and configure the Responses API as described in the documentation. For Claude Code, use https://api.lanox.ai without /v1. Both require a LanoX API key and a model ID that supports the client's API format; follow the LanoX CC Switch guide for setup instructions.
02How do I check my LanoX model settings and request logs?
Copy the exact model ID from the current catalog, then compare it with the model parameter sent by your client, the model information in the API response, and the request details in your dashboard. Similar names or different versions should not be treated as the same model. If the records do not match, contact support with the request time and request ID so the call can be investigated.
03What do I need to change when switching from a provider's API to LanoX?
If LanoX supports the API format your project uses, you can usually keep your SDK and update the base URL, API key, and model ID. Test the features your application relies on, including streaming, tool calls, and image inputs. Check compatibility separately for Chat Completions, Responses, and Claude Messages.
04What's the difference between a compatible API and a model's native API?
A model's native API is defined by its provider and may include provider-specific features and parameters. A compatible API matches the request and response format expected by existing clients, making those clients easier to reuse. Support for streaming, tool calls, structured output, and multimodal inputs can differ, so check each feature your application needs.
Ready to send your first request?
Create an API key, copy an exact model ID from the live catalog, and follow the guide for your client.