Skip to content

TextCortex API · Models and routing

One API. The right model for each request.

Route requests to proprietary and open-weight models through TextCortex. Use one OpenAI-compatible integration with EU-hosted model options.

One API. Every model family.
GPTOpenAI
ClaudeAnthropic
GeminiGoogle
GLM5.3
DeepSeek
KimiK3
MiMo
TextCortex
GPT, Claude, Gemini and open-weight models. Routed through TextCortex.

Why TextCortex

Model choice belongs in your application.

Give each feature the model it needs without building a new provider integration. TextCortex combines broad model access with a common API for model selection and inference.

01

Route by task

Choose a model for each request in your application. Keep one integration while matching response quality, cost and latency to the workload.

02

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.

03

EU-hosted model options

Use EU-hosted routes for European inference requirements. Hosting depends on the selected model and route; the wider catalog also includes other deployments.

Choose models by task

Route a short classification task to a model that meets your cost and latency target. Choose another for complex analysis or code generation. Store these choices in server-side configuration so you can update them without changing the user interface.

Include GPT, Claude and Gemini in the same evaluation as Kimi, GLM, DeepSeek and MiMo. The useful comparison is the result on your workload, not whether a model has open weights.

Keep routing rules explicit

Use the model field to select a supported identifier for each call. Make a small mapping from application tasks to model identifiers, then log which model served each request.

A common endpoint does not require identical settings for every model. Keep model-specific capabilities and reasoning parameters with the routing configuration. Avoid forwarding unvalidated model names from public clients.

Keep regional rules in the routing decision

For a workload that requires EU inference, select the EU-hosted routes enabled for it. Restrict the eligible models before comparing performance. A fallback should remain within the same processing requirements.

Use the data residency guide to document the route and the systems around it. The general model catalog and the EU-eligible list serve different purposes.

Make your first API request

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)

Questions

Your next questions, answered.

How does model routing work?

Your application selects an available model in each API request, and TextCortex routes the request through its API. You can choose different models for different tasks. Automatic selection and fallback behavior should only be used where documented for your configuration.

Is TextCortex limited to open-source models?

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.

Are all models in the catalog EU-hosted?

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.

What changes when I migrate an existing integration?

Update the base URL, API key and model identifiers. Review provider-specific parameters and test streaming, tools, structured output and error handling used by your application. Keep your original configuration available during the rollout.

TextCortex AI

One integration. Your choice of models.

Sign up for TextCortex, create an API key and start building with the models your application needs.

Sources and documentation

Product documentation and provider references used for this guide. Reviewed on 5 October 2026.