AISBF

Base URL and authentication

export CODERAI_URL="http://127.0.0.1:8776"
export CODERAI_TOKEN="your-api-token"

curl -s "$CODERAI_URL/v1/models" \
  -H "Authorization: Bearer $CODERAI_TOKEN" | jq

CoderAI supports web sessions and API bearer tokens. Token management is available in the admin UI and via GET /admin/api/tokens and POST /admin/api/tokens. Interactive OpenAPI docs are served by a running instance at /docs, with raw schema at /openapi.json.

Core endpoints

OpenAI-style text

curl -s "$CODERAI_URL/v1/chat/completions" \
  -H "Authorization: Bearer $CODERAI_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"model":"Qwen/Qwen3-8B","messages":[{"role":"user","content":"Explain VRAM offloading."}],"temperature":0.4,"max_tokens":300}' | jq

• POST /v1/chat/completions supports common OpenAI fields, streaming, tools, tool_choice, repeat penalty, and thinking templates where supported.
• POST /v1/completions supports legacy text completion clients.
• POST /v1/embeddings serves embeddings where a configured model supports them.

Multimodal routes

Data conventions

Media inputs generally accept HTTP URLs, CoderAI file URLs, raw base64, or data URLs such as data:image/png;base64,.... Generated media usually returns a data array with a url, or base64 keys such as b64_json, b64_mp4, b64_wav, or b64_mp3 when requested.

{"created":1781090000,"data":[{"url":"/v1/files/generated.png"}]}