# Use it from your stack


# Use AxForge with your stack

    AxForge speaks the OpenAI API shape, so the tools you already
    use work here. In almost every case the whole integration is three changes:
    the base URL, your
    key, and a
    model name.

## The one pattern behind every guide

Whatever the tool, you are telling it to send OpenAI-style requests to us
    instead of OpenAI:

        | Set this | To |  |

        | Base URL | https://api.axforge.ai/v1 |  |

        | API key | your AxForge key (orx_live_…) — from the console |  |

        | Model | chat · embeddings · or an exact version |  |

The fastest check that it is wired correctly, from any shell:

```
$ curl https://api.axforge.ai/v1/chat/completions \
    -H "Authorization: Bearer $AXFORGE_API_KEY" \
    -H "Content-Type: application/json" \
    -d '{"model":"chat","messages":[{"role":"user","content":"ping"}]}'
```

A JSON reply with a `choices` array means you are connected. From
    there, pick your tool.

## SDKs

        **OpenAI SDK**Python & Node. Change `base_url`, keep the rest of your code.drop-in

        **Vercel AI SDK**The standard TypeScript AI toolkit, via its OpenAI-compatible provider.drop-in

## Coding assistants

        **aider**Terminal pair-programmer. One env var and a model prefix.drop-in

        **Continue**VS Code & JetBrains. An `openai` provider in `config.yaml`.drop-in

        **Cline**VS Code agent. The "OpenAI Compatible" provider.drop-in

        **Kimi Code CLI**Moonshot's terminal agent, pointed at an `openai` provider.drop-in

        **Codex & Claude Code**Speak the Responses / Messages APIs — both served natively, point straight at us.direct

## Chat UIs & terminals

        **Open WebUI**Self-hosted chat UI. One OpenAI connection; models auto-list.drop-in

        **LibreChat**Multi-model chat app. A custom endpoint in `librechat.yaml`.drop-in

        **llm (Datasette CLI)**Simon Willison's terminal LLM CLI. One YAML entry.drop-in

## Gateways & proxies

        **LiteLLM**Put AxForge behind one endpoint; re-expose Chat, Messages & Responses.proxy

    **A note on API shapes.** Nearly everything speaks the
    Chat Completions API, which
    AxForge serves. Two popular tools speak a different shape — OpenAI's
    **Codex CLI** uses the
    Responses API and
    **Claude Code** the Anthropic
    Messages API — and AxForge serves both
    of those natively too (`/v1/responses`, `/v1/messages`), so
    they point straight at us. See the Codex
    & Claude Code guide.

## Anything else

If a tool can point at a custom OpenAI base URL — another CLI, a workflow node, a
    no-code builder, a gateway such as the Vercel
    AI Gateway — it works the same way: base URL, key, model. When in doubt, use the
    `curl` check above with your tool's base-URL and key fields, then
    fill them into the tool. Stuck? Talk to an
    engineer.

      ← Glossary
      OpenAI SDK →



Source: https://axforge.ai/docs/connect/