Warp

Warp is an agent development environment in the terminal. It supports custom inference endpoints: as long as the other side implements the OpenAI Chat Completions interface, Warp Agent's model calls can be routed there. Point the endpoint at aicentos and the models under your own account can drive Warp's Agent.

PrerequisitesCopy anchor link

• Update Warp to a version that includes custom inference endpoints (older versions only have BYOK and cannot change the Base URL).
• Create a dedicated key in the aicentos console (naming it warp-terminal is a good idea).
• Confirm the models you plan to use support function calling, which Warp Agent relies on to read and write files and run commands.

Configuration to fill inCopy anchor link

Setup stepsCopy anchor link

• Open Warp's settings, search for inference endpoint, or go to Settings → AI.
• In the Custom inference area, click Add custom model / Add destination.
• In the dialog, fill in the Endpoint name, Endpoint URL (https://aicentos.com/v1) and API Key.
• Enter the model ID under Model name and click Add model to add more; an alias can be set for easier identification.
• After saving, the custom models appear in Warp's model picker, labeled with your endpoint name.

TestCopy anchor link

Select the newly added model in Warp and send a simple question (e.g. "List the files in the current directory and explain the project structure") to confirm it returns normally. Custom endpoint models show up in the agent mode, toolbar and ambient agent pickers.

NotesCopy anchor link

• The Endpoint URL takes the OpenAI-compatible root path (from which /v1/chat/completions can be formed); do not write the full /v1/chat/completions.
• The endpoint must be reachable from the public internet: Warp's requests are relayed through its servers, and localhost or intranet addresses are rejected. aicentos.com is a public HTTPS address and works as is.
• The API Key and endpoint information are stored in the secure storage of the local device; Warp's servers only use them at request time and do not retain them.
• Requests through a custom endpoint do not consume Warp's AI credits; costs are billed on the aicentos side by usage. However, under Business / Enterprise plans, running local agents still consumes platform credits.
• If you get 400 invalid model format, your gateway expects the provider/model_id form; follow the model ID given in the console and add the prefix in that format if necessary.
• Custom endpoints cannot currently declare a context window separately, so very long sessions may be compacted early.
• Official documentation: https://docs.warp.dev/agent-platform/inference/custom-inference-endpoint/