Connection info

GET /v1/connection-info returns the public coordinates a client needs to connect — the MCP endpoint, the REST base, the workspace header name, and SDK package info. It contains no secrets, so it’s safe to call from the browser or a setup script.

This is the same endpoint the console’s Simple Mode reads to render the connect-and-go surface.

Request

Terminal

curl https://api.wexa.ai/v1/connection-info

Response (shape)

The payload provides the coordinates that drive the connect surface:

Field	Meaning	Example
mcpServerUrl	MCP Streamable HTTP endpoint	https://mcp.wexa.ai/v1/sse
mcpSseUrl	MCP SSE-compat endpoint	https://mcp.wexa.ai/v1/sse
apiBaseUrl	REST base URL	https://api.wexa.ai/v1
workspaceHeader	Header that carries the workspace ID	X-Wexa-Workspace
sdk.python	Python package + install command	wexa / pip install wexa
sdk.node	Node package + install command	@wexa/sdk / npm install @wexa/sdk

Tip

Use this endpoint instead of hardcoding URLs. In on-prem and air-gapped deployments the host names differ from the managed-cloud examples above — connection-info always returns the right values for the install you’re talking to.

Why it matters for portability

Because every client (console, MCP, REST, SDK) reads its coordinates from one endpoint, the same agent configuration works across managed cloud, private cloud, and air-gapped installs — only connection-info changes.