Proprietary and open-weight models
Access GPT, Claude, Gemini, Kimi, GLM, DeepSeek, MiMo and more through TextCortex. Choose models from the catalog available to your account.
TextCortex API · Models and routing
Access GPT, Claude, Gemini, Kimi, GLM, DeepSeek and MiMo through one OpenAI-compatible API. Route your requests with TextCortex, including EU-hosted options.
Why TextCortex
TextCortex gives your application a single API for proprietary and open-weight models. Keep a common client, route different tasks to different models, and use EU-hosted deployments where your workload requires them.
Access GPT, Claude, Gemini, Kimi, GLM, DeepSeek, MiMo and more through TextCortex. Choose models from the catalog available to your account.
Use a familiar client, one TextCortex API key and a common base URL. Change the model identifier to switch between supported models.
Use EU-hosted routes for European inference requirements. Hosting depends on the selected model and route; the wider catalog also includes other deployments.
Use GPT, Claude and Gemini alongside Kimi K3, GLM-5.3, DeepSeek, MiMo and other supported models. Your application connects to TextCortex instead of maintaining a separate integration for every model family.
Change the model identifier for a request to compare answers, power a different feature or introduce a new model into your product. Your account catalog is available through GET /models.
A support response, a code review and a classification step can use different models. Define the selection in your application and send each request through the same API. Measure quality, latency and token usage against the task.
Start with explicit model choices so behavior is predictable. If you need automatic selection or failover, use only the routing controls documented for your configuration.
Use the deployment that matches your processing requirements. The EU model pages cover European hosting; other models in the wider catalog can have different processing arrangements.
Create a TextCortex account and generate an API key in account settings. Install the OpenAI Python package on your server. Store the key in TEXTCORTEX_API_KEY and set TEXTCORTEX_MODEL to an identifier returned by GET /models.
This example keeps credentials in environment variables. The same client configuration works when you choose another supported model. Read the API reference for endpoint-specific parameters.
import os
from openai import OpenAI
client = OpenAI(
api_key=os.environ["TEXTCORTEX_API_KEY"],
base_url="https://api.textcortex.com/v1",
)
for model in client.models.list():
print(model.id)
response = client.chat.completions.create(
model=os.environ["TEXTCORTEX_MODEL"],
messages=[{"role": "user", "content": "Hello"}],
)
print(response.choices[0].message.content)
Use the OpenAI-compatible API guide to connect your application. Then define the model choices, request limits and error handling your product needs.
Compare costs with the API cost calculator and use the routing guide to organize a multi-model integration.
Questions
No. The API provides access to proprietary model families such as GPT, Claude and Gemini alongside open-weight families such as Kimi, GLM, DeepSeek and MiMo. Use GET /models to list the identifiers available to your account.
Yes. Configure the client with the TextCortex base URL and API key. Use a TextCortex model identifier and the parameters supported by that model. Model discovery, chat completions and responses are documented in the API reference.
TextCortex offers EU-hosted model routes and a broader multi-provider catalog. Select the EU-hosted deployment required by your application; catalog membership alone does not establish where a particular request is processed.
Sign up for TextCortex, create an API key in your account settings, and use https://api.textcortex.com/v1 as the base URL. Retrieve the model catalog, select a model identifier and send a chat-completion request.
TextCortex AI
Sign up for TextCortex, create an API key and start building with the models your application needs.
Product documentation and provider references used for this guide. Reviewed on 5 October 2026.