Connecting your AI assistant
A one-time setup per user. The assistant signs in with the user's own iVendNext login and never stores the password.
The AI Gateway uses a modern, secure sign-in flow. When a user first connects their assistant, iVendNext shows the familiar login page, the user authorises the assistant, and from then on the connection refreshes itself automatically. The assistant only ever receives a temporary access token, never the password.
Before you connect: enable the connection settings
An administrator confirms these one-time settings on the Connection (OAuth) tab of the Settings screen. They are on by default.
| Setting | Why it matters |
|---|---|
| Enable Dynamic Client Registration | Lets supported AI assistants register themselves automatically, so there is no manual setup per assistant. |
| Show Authorization Server Metadata | Lets the assistant discover how to sign in to your site automatically. |
| Show Protected Resource Metadata | Publishes the information the assistant needs to recognise your site as a valid data source. |
Where to find your connection details
The Settings screen's General tab shows two read-only values that the assistant needs. An administrator copies these and shares them with users, or users read them directly:
-
Connection URL (the MCP Endpoint URL): the address the assistant connects to.
-
Discovery URL: the address the assistant uses to learn how to sign in.
Connecting a desktop AI client
-
In iVendNext, open the AI Gateway Settings and copy the Connection URL from the General tab.
-
In your AI client, open the connectors or custom connector area and choose to add a new connector.
-
Give it a name (for example, "iVendNext"), paste the Connection URL, and choose the secure sign-in (OAuth) option.
-
Save, then click Connect. Your browser opens the iVendNext login page.
-
Log in with your iVendNext account and authorise the assistant. You are now connected.
-
Test it: ask the assistant, "List all customers created this month."
Connecting a web-based assistant
The flow is the same. In the web assistant's custom connector or action settings, add a new connector, paste the Connection URL, select secure sign-in, save, and authorise when prompted. Web assistants connect server to server, so no additional configuration is required.
Tip for administrators. The "Allowed Public Client Origins" field is only needed for in-browser testing tools. Desktop and web assistants do not need it. Leave it blank for normal use.
What happens behind the scenes
On first connection, the assistant discovers your sign-in configuration, registers itself, requests your authorisation, and securely stores a short-lived access token. When that token expires, it refreshes automatically, so users rarely sign in more than once.