Connections

Five areas on one page, each with its own tab. They have nothing technically in common — they are together because they are all answers to “how does this reach something outside Syncanix”, and that is the question somebody has when they come looking.

Where the widget may load

The widget loads only on a site you have listed here. This is what stops your publishable key being useful to somebody who copies it onto their own page.

• An entry is a scheme and a host and nothing more — listing https://shop.example.com covers every page on it.
• Add your staging and preview hosts too, or the widget will not load while you are testing.
• Removing an origin takes effect immediately and stops the widget on that site.

Getting events into your own systems

A webhook destination is a URL on your side that Syncanix posts events to — a conversation handed to a human, a compliance finding, a proposal waiting for review. It is how something that happens here shows up in your own alerting, your ticket queue, or your data warehouse.

1. 1
   Give it a reachable URLSyncanix posts to it, so it has to be reachable from the internet over HTTPS. A URL behind a VPN will simply never receive anything.
2. 2
   Pick the events, narrowlyStart with only what you will act on and add more later. A destination subscribed to everything becomes noise that somebody eventually mutes, which is worse than not having it.
3. 3
   Copy the signing secretIt is shown exactly once, and you verify every delivery against it so your endpoint can tell a real event from anything else that finds the URL. Rotating it takes effect immediately — your endpoint rejects deliveries until you redeploy with the new one.

Serving from your own domain

You can serve the widget from a hostname of your own so visitors never see a Syncanix URL. Enter the hostname, add the DNS record shown, and verification runs on its own — DNS changes take a while to reach us, so the page keeps checking rather than asking you to. The HTTPS certificate is issued and renewed for you once the record verifies.

Your MCP server URL

Every workspace gets its own URL for connecting an AI client. The tab holds it plus ready-made setup cards for the common clients, and it is also where you register an MCP server you already run so its tools appear alongside your own.

Using your own AI provider

Add your own provider key, or point Syncanix at a deployment you run yourself. Either way requests go under your own agreement with that provider and never through a Syncanix account, your provider bills you for inference, and we stop charging for those tokens. If your provider rejects the key the status here says so — conversations do not quietly fall back to ours.

Next steps