OpenClaw

Coming soon

This package is not yet on the public npm registry. Contact the Telem team for early access.

@telem/openclaw-plugin adds telem_search and telem_fetch as agent tools in OpenClaw, both backed by the same POST /v1/interactions endpoint the rest of Telem uses. While the plugin is enabled it also blocks OpenClaw’s built-in web_search and web_fetch, redirecting the agent to the Telem tools instead — so every web search and page read in a conversation lands in one Telem trajectory.

Prerequisites

• Node.js 22+
• OpenClaw 2026.7.1 or newer — older hosts don’t expose the plugin API this plugin needs; see Troubleshooting.

Install

1. Get an API key. There’s no public dashboard yet — contact the Telem team for an API key. Some Telem deployments run open and don’t require one at all; see Authentication for details.

2. Install the plugin. This registers telem in OpenClaw’s plugin list and enables it.

3. Put your key in the Gateway environment. TELEM_API_KEY goes in ~/.openclaw/.env; skip this line if your deployment doesn’t need a key.

4. Restart the Gateway. This step is required, not optional — OpenClaw won’t load the plugin or pick up the key until the Gateway restarts.

openclaw plugins install npm:@telem/openclaw-plugin
echo "TELEM_API_KEY=${TELEM_API_KEY}" >> ~/.openclaw/.env
openclaw gateway restart

What you get

Two tools, both recorded into the same Telem trajectory:

• telem_search — runs one or more search queries as a single Telem interaction and returns normalized, provider-attributed results.
• telem_fetch — reads up to 5 whole web pages in one call, fetched as one interaction and rendered one section per URL.

Configuration

The plugin defaults to the hosted Telem service at https://router.telem.ai. Point it at another deployment with plugins.entries.telem.config.baseUrl or TELEM_BASE_URL.

Config key	Env fallback	Meaning
apiKey	TELEM_API_KEY	Optional bearer credential
baseUrl	TELEM_BASE_URL	Service endpoint override (default https://router.telem.ai)
tier	TELEM_TIER	Named result-field tier: minimalist, default, extended, or max
fields	TELEM_FIELDS (comma-separated)	Explicit normalized fields; mutually exclusive with tier
providersInclude	TELEM_PROVIDERS_INCLUDE (comma-separated)	Replace the deployment’s provider set
providersExclude	TELEM_PROVIDERS_EXCLUDE (comma-separated)	Subtract providers from the selected set
fullContent	TELEM_FULL_CONTENT (1 only)	Retrieve full content for the interaction; never rendered inline — use telem_fetch to read a page

Precedence: plugin config beats the environment, resolved per key on every tool call. If both tier and fields resolve, the more specific source wins; on a tie, fields wins and the plugin logs a warning.

{
  plugins: {
    entries: {
      telem: {
        enabled: true,
        config: {
          apiKey: "tlm_...",
          tier: "extended",
          providersInclude: ["exa", "tavily"],
        },
      },
    },
  },
}

Troubleshooting

Tools missing from the agent

A restrictive tool policy can hide telem_search/telem_fetch even though the plugin is installed and enabled. Check first:

npx --yes --package=@telem/openclaw-plugin telem-openclaw-setup --check

Then run the same command without --check to add the two tools to your tool policy. It preserves any explicit tools.deny and reports per-agent policies it can’t safely change.

Tools still missing after setup

The Gateway that’s actually serving your agents hasn’t restarted yet — plugin installs and config changes only take effect after a Gateway restart.

Plugin won’t load at all

Your OpenClaw host is older than 2026.7.1, the plugin’s version floor. Upgrade OpenClaw and reinstall.