Skip to main content

Entry

Settings → Services Intro copy: “Configure custom endpoints for Starcat backend services.” Each service card includes:

Rules

  1. URL is the service root only — no business path, no trailing slash noise.
    • Good: http://127.0.0.1:5002 or https://trending.example.com
    • Bad: http://127.0.0.1:5002/api/v1 or a legacy …/api suffix (Sharing’s old /api form is stripped on save)
  2. API Key must be one entry from the instance’s API_KEYS allowlist.
    Client priority: custom key on this page → baked-in production key → none (requests omit Authorization, usually 401).
  3. Test connection succeeds when the host is reachable, the key is accepted, and data.service matches the card (catches wrong ports).
  4. You may override only some services (e.g. self-host Discovery, keep official Trending).

Local wiring example

If all APIs are running per Deploy: Paste matching keys and test each card.

How it takes effect

Saving hot-updates the client baseURL / key (full app restart usually unnecessary; refresh the Explore pane if a list looks stale). Status-bar availability uses /healthz (no key), which is different from Test connection:

Troubleshooting

Last modified on July 22, 2026