AIChat

Copy the configuration and replace sk-... with your key from the Ailoot Dashboard. Prefer storing the key in the environment variable AILOOT_API_KEY, if the application supports it.

Before starting, request GET /v1/models with your Ailoot key. Choose an exact model ID whose methods include POST /v1/chat/completions, POST /v1/messages, POST /v1beta/models/{model}:generateContent, then use that ID in the configuration. For agents, also check tool support and the features required by your client version.

clients:
  - type: openai-compatible
    name: ailoot
    api_base: https://api.ailoot.ai/v1
    api_key: sk-...
    models:
      - name: deepseek-v4-pro
        max_input_tokens: 1000000
        supports_function_calling: true
  - type: claude
    api_base: https://api.ailoot.ai/v1
    api_key: sk-...
  - type: gemini
    api_base: https://api.ailoot.ai/v1beta
    api_key: sk-...

aichat -m ailoot:deepseek-v4-pro 'Hello'

Example model: deepseek-v4-pro. Choose any other model from the catalog — check that it supports the format you need.

• For the OpenAI format, the URL is https://api.ailoot.ai/v1 (or the full path if the application asks for a full URL).
• For the Anthropic SDK, the base URL is https://api.ailoot.ai without /v1.
• For the Google GenAI SDK, the base URL is https://api.ailoot.ai without /v1beta.
• Ask a short question. If you get an error, check the code and Request ID, then consult Errors and limits.
• 404 immediately after setup almost always means the URL is wrong: an extra or missing /v1.
• 402 — insufficient balance for the reserve. Agents reserve more than chat: why.

Application documentation: https://github.com/sigoden/aichat/blob/main/config.example.yaml