Watch a dependency

Use direct setup when you already know the concrete source Lucim should monitor.

Console workflow

Choose Watch dependency

Open Monitors and expand Watch dependency.

Select a capability

Choose a category and source type. The form is generated from GET /api/monitor-capabilities, including locator fields and authentication-reference support.

Enter the locator

Provide the requested URL, package name, repository, or structured locator. Direct MCP sources accept only HTTPS Streamable HTTP endpoints.

Create the monitor

Lucim validates the locator, creates the entity/source/watch set through tenant-aware services, and requests a first capture for active sources.

REST example

Create an OpenAPI monitor with a key that has the write scope:

curl --request POST "$LUCIM_API_URL/v1/watches" \
  --header "Authorization: Bearer $LUCIM_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
    "canonical_name": "Payments API",
    "entity_type": "api_provider",
    "source_type": "openapi_spec",
    "locator": {"url": "https://api.example.com/openapi.json"},
    "fetch_interval": "1 hour",
    "active": true
  }'

The response includes the new watch ID, entity_id, and source_id.

Authenticated MCP sources

Store only an auth_ref in the locator. A deployment-owned reference uses an allowlisted environment variable such as env://LUCIM_MCP_AUTH_PAYMENTS; tenant-managed credentials use an encrypted reference. Workers resolve the secret at capture time and persist only non-secret auth metadata.

Never place a bearer token or API key in a source URL, locator, console field, or committed configuration.

Connect a codebase Review changes

Getting started

Core concepts

Guides

Integrations

Watch a dependency

Console workflow

REST example

Authenticated MCP sources

​Console workflow

​REST example

​Authenticated MCP sources

Console workflow

REST example

Authenticated MCP sources