Exposed endpoints

By default, the local Bridge is reachable only from localhost. That's the safe default — your harness on the same machine can reach it; nothing else can. But sometimes you want to share a single deployed model with another tool or a teammate. That's what exposed endpoints are for.

What an exposed endpoint is

An exposed endpoint is a deployment-scoped, OpenAI-compatible URL plus a bearer token. The bearer:

• Starts with sk-syntax- followed by a random suffix.
• Is shown to you exactly once when you issue it. After that, it's not retrievable from Syntax — only the masked form is shown.
• Is scoped to a single deployment. Other models on the same Syntax install are not reachable through this bearer.
• Can be revoked at any time. Revocation is immediate.

Two flavors of exposure

When you deploy a model, you can pick:

• Expose private — the endpoint is reachable from your other Syntax tools (e.g., a teammate's machine on the same internal network) but not from the public internet.
• Expose public — the endpoint is reachable from anywhere with the bearer. Use this when you want to share with a non-Syntax tool that can't reach your private network.

You can pick either, both, or neither. Most one-off sharing flows just use a private exposure; public exposure is for cases where you genuinely need a publicly reachable URL.

What an exposed bearer can do

A bearer can call the deployment's OpenAI- and Anthropic-compatible inference surface (chat, messages, and model listing for the scoped model — whichever apply to the model's modality).

It cannot:

• Call any other deployment.
• Issue or revoke other bearers.
• Modify deployments.
• Reach Syntax's settings or control plane.

Issuing and revoking

From the desktop app's Active Deployments view:

• Click Expose on a deployment to issue a bearer. The bearer is shown once with a "Copy" button. After you close the modal, you'll only see the masked form.
• Click Revoke to invalidate the bearer immediately. New requests fail; in-flight requests complete normally.

When this matters

• Sharing with a non-Syntax tool. Any tool that speaks an OpenAI-compatible API can use the exposed bearer.
• Multi-machine workflows. Run Syntax on one machine, run a bot or a backend on another, and let the backend reach a deployed model through a private exposure.
• Stable URLs for a project. Issue one bearer for a project, share it with the project's team, revoke when the project ends.

Where to go next

• Differentiators → First-class inter-compatibility — the Bridge behind the URL.
• Inference → Managed remote — managed deployments support both private and public exposures.