TexAPI documentation

Use with every family on sale; Kimi needs the native Messages endpoint.

1. 1
   Open or create the settings.json file (comments allowed — JSONC).
2. 2
   Set env.ANTHROPIC_BASE_URL to TexAPI and env.ANTHROPIC_AUTH_TOKEN to your API key.
3. 3
   If env.ANTHROPIC_API_KEY has a value, REMOVE it — Claude Code may prefer that variable and keep calling the old upstream instead of TexAPI.
4. 4
   Restart Claude Code. Call any model to check.

{
  "env": {
    "ANTHROPIC_BASE_URL": "https://texapi.dev",
    "ANTHROPIC_AUTH_TOKEN": "sk-texapi-..."
  }
}

Use with the families on sale over the Responses interface.

1. 1
   Open or create config.toml. Put model_provider = "texapi" at the top, outside any [table] block.
2. 2
   Add the [model_providers.texapi] block from the snippet — base_url ends with /v1.
3. 3
   Write the key into auth.json: OPENAI_API_KEY is your TexAPI key, auth_mode is "apikey".
4. 4
   Restart Codex. If you had signed in with another account, the new auth_mode overwrites it — the connector's disconnect restores it; by hand, back it up first.

model_provider = "texapi"

[model_providers.texapi]
name = "TexAPI"
base_url = "https://texapi.dev/v1"
wire_api = "responses"
requires_openai_auth = true

{
  "OPENAI_API_KEY": "sk-texapi-...",
  "auth_mode": "apikey"
}

Use with the families on sale over the Google generateContent interface.

1. 1
   Open or create ~/.gemini/.env (the CLI loads this file itself — no export needed).
2. 2
   Set GOOGLE_GEMINI_BASE_URL to the bare origin WITHOUT /v1beta — the SDK appends /v1beta/models/… itself.
3. 3
   Set GEMINI_API_KEY to your TexAPI key.
4. 4
   If you had signed in with Google (OAuth): open settings.json and set security.auth.selectedType to "gemini-api-key", or the new base URL is ignored.

GOOGLE_GEMINI_BASE_URL=https://texapi.dev
GEMINI_API_KEY=sk-texapi-...

{
  "security": {
    "auth": {
      "selectedType": "gemini-api-key"
    }
  }
}

Use with every family on sale over the OpenAI-compatible surface.

1. 1
   Open or create ~/.aider.conf.yml.
2. 2
   Set openai-api-base to https://texapi.dev/v1 and openai-api-key to your key.
3. 3
   The model MUST carry the openai/ prefix — e.g. openai/glm-5.2. Without it, aider resolves the model against its own provider table and hits the wrong endpoint.

openai-api-base: https://texapi.dev/v1
openai-api-key: sk-texapi-...
model: openai/glm-5.2

Use with every family on sale over the OpenAI-compatible surface.

1. 1
   Open VS Code Settings (Ctrl+,), search for “Cline: OpenAI Compatible Settings” (Roo Code is similar).
2. 2
   Base URL: https://texapi.dev/v1 — API Key: your sk-texapi-…
3. 3
   Model ID: pick a TexAPI model that serves chat (see the matrix).

Use with every family on sale over the OpenAI-compatible surface.

1. 1
   Open ~/.continue/config.yaml.
2. 2
   In the models list, add an entry: model is the TexAPI id, apiBase is https://texapi.dev/v1, apiKey is your key, provider is openai.
3. 3
   Select that model in Continue. Continue creates the file itself when empty — add to the models list, never overwrite the whole file.

Use with every family on sale over the OpenAI-compatible surface.

1. 1
   Open Zed's settings.json (Zed: Open Settings).
2. 2
   Add a language_models.openai block: api_url = "https://texapi.dev/v1".
3. 3
   The API key does NOT go in settings.json — Zed prompts for it and stores it in the OS keychain on your first request.