Source: https://ailoot.ai/docs/integrations/amp/
Canonical: https://ailoot.ai/docs/en/integrations/amp/
Language: en

[Terminal agents](https://ailoot.ai/docs/en/integrations/#agents) 

# Amp

[Markdown](https://ailoot.ai/docs/en/integrations/amp/index.md)

Terminal agent · OpenAI Chat, OpenAI Responses, Anthropic Messages, Gemini

| Format | Where to set it up |
| --- | --- |
| OpenAI Chat, OpenAI Responses, Anthropic Messages, Gemini | Settings → Model Routing → Add → Custom URL (or workspace Model Routing for a team); from the terminal — amp config model-providers (list, test, set-priority, edit-router…) |

## [](https://ailoot.ai/docs/integrations/amp/#setup)Setup

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/responses, 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.

```text
Model Routing → Add → Custom URL
  Format:   anthropic-messages
  Base URL: https://api.ailoot.ai
  API key:  sk-...
  Model mapping:
    anthropic/claude-fable-5 -> anthropic/claude-fable-5

Second connection for GPT:
  Format:   responses
  Base URL: https://api.ailoot.ai/v1
  API key:  sk-...
  Model mapping:
    openai/gpt-5.6-sol -> gpt-5.6-sol

Check: amp config model-providers check-access --provider-model anthropic/claude-fable-5
```

Example model: `claude-fable-5`. Choose any other model from the [catalog](https://ailoot.ai/models/en/) — check that it supports the format you need.

## [](https://ailoot.ai/docs/integrations/amp/#notes)Good to know

Custom URL formats: chat-completions (\<base\>/chat/completions), responses (\<base\>/responses), anthropic-messages (\<base\>/v1/messages; /v1 is not duplicated), google-genai (\<base\>/models/\<model\>:streamGenerateContent). The key is sent as Authorization: Bearer. Mappings use canonical Amp IDs in the provider/model form; the arrow specifies the ID sent to us. Amp handles models not covered by the connection itself, using its own credits. The documentation requires the custom host to be accessible from Amp — our URL is public, so this requirement is met.

## [](https://ailoot.ai/docs/integrations/amp/#check)Test

- 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 format, the URL is `https://api.ailoot.ai` without `/v1`.
- For the Gemini format, the URL is `https://api.ailoot.ai` — the API origin. The example above does not show the full setup for this format; consult the client’s documentation for the path to use in the relevant field. The API route prefix is `/v1beta`.
- Ask a short question. If you get an error, check the code and Request ID, then consult [Errors and limits](https://ailoot.ai/docs/en/errors/).
- 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](https://ailoot.ai/docs/en/billing/reserve/).

Application documentation: [https://ampcode.com/docs/markdown/customize/model-routing](https://ampcode.com/docs/markdown/customize/model-routing)

Still have questions? Send your Request ID and a description — we'll help you troubleshoot.[Contact support](mailto:support@ailoot.ai)

## Ailoot · The company and its project portfolio





Ailoot combines established operating experience, a large client base, stable service and ongoing KPI control.





The company and its project portfolio: millions of customers; monthly sales in the billions.





Ailoot brings that operating experience to API access for AI features in customer products, agents, applications and automations.