The IQX AI Gateway is the single front door for every AI feature in IQX. Instead of each part of the product talking to an AI provider directly, everything — the IQXAssist chat your consultants use, the wiki help assistant, CV reformatting, document and photo reading, audio transcription — calls one internal service. That service picks a model, routes the request, retries elsewhere if something is down, meters the spend, logs the usage, and hands the answer back.
In short, it is an AI router and control plane: the clever bits (which model, failover, cost caps, encryption) live in one place, so every IQX feature behaves the same way and we can add or swap models without touching the apps.
/v1 and it just works.—-
IQXAssist is the assistant your consultants talk to inside IQX. Unlike a standard “question and answer” bot, it is context-aware: it knows which candidate or contact record you are viewing and can pull live data specific to them.
The chat works in two modes depending on what you ask:
Every session is tied to the record you are viewing. Navigate to a different candidate and a new chat begins, so data can't cross over between records.
IQXAssist has strictly defined tools that let it read specific parts of a record. These are read-only and never change anything.
| Data type | What it can see | Best way to ask |
|---|---|---|
| Timesheets / records | Pay status, hours, rates, notes, placements | “Show timesheets from 1 Jan to 1 Feb” |
| Shifts | Open shifts the candidate is suitable and available for | “What shifts are open for them next week?” |
| Availability | Holidays and unavailability blocks | “Are they available in March?” |
| Compliance | Licence details, training, medicals, right to work | “Compliance-check them for the Friday night shift” |
IQXAssist can also do things on your say-so — propose a shift booking or record an availability change.
One of the handiest features is drafting communications:
—-
Every capability is also a single HTTP call, so any IQX service or script can use it. Authenticate with a Bearer key — the optional user id after the dot attributes usage to a person:
Authorization: Bearer YOUR_KEY.USER_ID
Here is what each endpoint takes in and gives back.
Send an image plus a prompt. Ask a plain question and get an answer, or ask for the fields and they come back parsed in response.json. Driving licences, passports, DBS certificates, timesheets, whiteboards — all fair game.
Finds the portrait on a licence, passport or ID card and crops it out — ready to save straight to the candidate's record as their profile picture.
Upload a candidate's CV (PDF or Word) plus your template and logo; get back a consistent, branded CV. Personal contact details are automatically redacted in the process.
Send a record (or any document) plus a prompt and get a tidy answer back — great for summaries embedded in other IQX screens.
Point any OpenAI SDK at /v1 and it just works — streaming and tools included. The gateway picks the model and handles failover underneath. GET /v1/models returns a friendly model list for a picker.
—-
—-
| Endpoint | Method | Purpose |
|---|---|---|
/api/query | POST | One-shot text: prompt (+ optional context), returns the completion. |
/api/cv-rewrite | POST | Rewrite / tidy CV text to a prompt. |
/api/cv/reformat | POST | Reformat an uploaded CV (PDF/DOCX) into an HTML template, optional logo. |
/api/image | POST | Vision — ask a question about an image, or extract its fields as JSON. |
/api/extract-photo | POST | Vision — crop the portrait photo out of an ID image. |
/api/transcribe | POST | Audio — transcribe an uploaded audio file. |
/v1/chat/completions | POST | OpenAI-compatible chat. Streaming and tools supported. |
/v1/models | GET | List the available models (friendly labels) for a model picker. |
/api/model-config | GET | The preferred default model for the key (so UIs don't hard-code it). |
/api/capabilities | GET | The calling key's effective tool capabilities. |
/api/chat/… | — | Stateful chat sessions (new, list, send, stream, rate, export, delete). |
—-
Keys, capabilities and spend caps are managed by IQX in the gateway admin. If you need a key for a new service or client, or want a capability enabled, contact the IQX development team.