ForgeCode
MarkdownTerminal agent · OpenAI Chat
Full guide
| Format | Where to set it up |
|---|---|
| OpenAI Chat | forge provider login → OpenAI-compatible (recommended); the deprecated option uses .env with OPENAI_URL and OPENAI_API_KEY, plus model in forge.yaml |
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, then use that ID in the configuration. For agents, also check tool support and the features required by your client version.
# recommended:
forge provider login # select OpenAI-compatible, enter https://api.ailoot.ai/v1 and sk-...
# legacy method (.env):
OPENAI_API_KEY=sk-...
OPENAI_URL=https://api.ailoot.ai/v1
# forge.yaml
model: claude-sonnet-5-5Example model: claude-sonnet-5-5. Choose any other model from the catalog — check that it supports the format you need.
Good to know
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). - 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/tailcallhq/forgecode
Still have questions? Send your Request ID and a description — we'll help you troubleshoot.Contact support