Feature Request: Add xAI / Grok support (and general OpenAI-compatible custom endpoints)

[Cain]

Hello PDF-XChange Team,

I’ve only been using PDF-XChange Editor for a couple of weeks, but I’m already impressed with it and have switched to it as my primary PDF tool for professional work. I’m an environmental consultant who regularly handles confidential regulatory documents, expert reports, and client materials, so privacy is a high priority.

The new AI Assistant is a useful addition. I would like to request support for **xAI’s Grok models** (via their API at `https://api.x.ai/v1`).

Key points:

- Grok’s API is already fully **OpenAI-compatible**. Once the Editor supports configurable base URLs / OpenAI-compatible endpoints, adding Grok should be straightforward.
- xAI does not train on API data, which makes it particularly suitable for confidential professional work.
- I am a SuperGrok subscriber and already rely on Grok heavily. I would strongly prefer to keep document analysis inside the same model rather than switching to OpenAI, Anthropic, or Google.

I also support the existing requests for a general “Custom API Provider” / OpenAI-compatible endpoint option (base URL + API key + model name). That single capability would cover Grok, local models (Ollama, LM Studio, vLLM, etc.), and private enterprise endpoints.

I understand from earlier forum replies that custom endpoints are already on the roadmap and that you prefer to stabilize the three current providers first. That’s reasonable. I’m simply adding a clear request for OpenAI-compatible custom endpoints, with explicit support for xAI/Grok once that feature is available.

Thank you for the excellent software and for considering this request.

Best regards,

-- Cain

[Daniel - PDF-XChange]

Hello, Cain

Thank you for the post! This has come up a few times here on the forums in recent months. Additional/Custom Endpoints is something we are looking into and hope to be able to offer in the future, but they are notably more complex to so and assure a consistent experience which minimizes platform specific bugs or API errors.

As such, we do have an ongoing item for it, and I will add your voice, but I cannot promise anything resembling a swift implementation at this time.

Kind regards,