#154
Issues/baarai/ARTEX/#154

[Feature Request] Support custom User-Agent and fixed full API endpoint URL

Openp091opened 3d ago

Request two new configuration options:

  1. Allow custom User-Agent header. If left blank, use the built-in default UA.
  2. Add a fixed-full-url mode for API BASEURL. Users can input a complete endpoint like example.com/v2/messages, and the request will be sent exactly to this address without extra path concatenation.

Motivation

Many third-party LLM relays use versioned routes such as v2 instead of the default v1 path. The current base-url style that auto appends fixed suffix cannot work with these relays. A raw fixed endpoint mode will greatly improve compatibility.

Expected behavior

  • User-Agent field: optional. User-provided value takes priority; fallback to default UA when empty.
  • API endpoint selector with two modes:
    • Legacy mode: base domain + auto appended paths (keep for backward compatibility)
    • Fixed full URL mode: use the input string as the final request URL directly.

Thanks for your work.

Activity

5
github-actions[bot]3d ago

Feature request: add two configuration options — an optional custom User-Agent header (falling back to the built-in default when blank) and a selectable API endpoint mode where providers can either keep the legacy base-domain-plus-appended-path behavior or specify a full fixed URL (e.g. example.com/v2/messages) used verbatim, so versioned third-party LLM relays work without forced path concatenation.

🤖 automated reply from the repo bot. A human maintainer reads everything. Ping me in any comment with @artex-bot.

BaaRai3d ago

Thanks for the detailed request. We will add the optional custom User-Agent in a PR shortly. The fixed full-URL mode needs more design care, because a saved API key must stay bound to the exact endpoint it was saved for, so we will follow up on it separately. Could you share which provider and which exact endpoint path you need?

BaaRai3d ago

Thanks again. The optional custom User-Agent is now on main via #155. Leaving this issue open for the fixed full-URL mode, which needs a design decision (a saved API key must stay bound to the exact endpoint it was saved for). Still interested in which provider and exact endpoint path you need.

p0912d ago

Thanks for your hard work on the custom User-Agent feature! I tested today and it seems I don’t need the fixed full URL feature for the moment. Yesterday I had a problem: when I entered xxx.com/v1, ARTEX requested xxx.com/v1/v4 and failed. However, the same configuration works normally today. I suspect this was caused by a misconfiguration of my third-party relay instead of an issue with ARTEX.

BaaRai2d ago

Thanks for testing and for the follow-up. We checked the code: ARTEX joins the base URL with a fixed suffix (/chat/completions, /responses or /v1/messages) and never inserts a version segment like /v4, so a base of xxx.com/v1 should go to xxx.com/v1/chat/completions (OpenAI format). If it happens again, could you check whether the relay answered with a redirect (a Location header) toward /v1/v4? That would confirm it came from the relay side.

One note for the Anthropic format: enter the base without /v1, since /v1/messages is appended; with /v1 the request goes to /v1/v1/messages.

We are keeping this issue open for the fixed full-URL mode, in case you or someone else needs it later.