mirror of https://github.com/moltbot/moltbot.git synced 2026-03-09 15:35:17 +00:00

Files

Kesku 3d7bc5958d feat(onboarding): add web search to onboarding flow (#34009 )

* add web search to onboarding flow

* remove post onboarding step (now redundant)

* post-onboarding nudge if no web search set up

* address comments

* fix test mocking

* add enabled: false assertion to the no-key test

* --skip-search cli flag

* use provider that a user has a key for

* add assertions, replace the duplicated switch blocks

* test for quickstart fast-path with existing config key

* address comments

* cover quickstart falls through to key test

* bring back key source

* normalize secret inputs instead of direct string trimming

* preserve enabled: false if it's already set

* handle missing API keys in flow

* doc updates

* hasExistingKey to detect both plaintext strings and SecretRef objects

* preserve enabled state only on the "keep current" paths

* add test for preserving

* better gate flows

* guard against invalid provider values in config

* Update src/commands/configure.wizard.ts

Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>

* format fix

* only mentions env var when it's actually available

* search apiKey fields now typed as SecretInput

* if no provider check if any search provider key is detectable

* handle both kimi keys

* remove .filter(Boolean)

* do not disable web_search after user enables it

* update resolveSearchProvider

* fix(onboarding): skip search key prompt in ref mode

* fix: add onboarding web search step (#34009) (thanks @kesku)

---------

Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
Co-authored-by: Shadow <hi@shadowing.dev>

2026-03-06 13:09:00 -06:00

4.6 KiB

Raw Blame History

summary, read_when, title

summary

read_when

title

Audit what can spend money, which keys are used, and how to view usage

You want to understand which features may call paid APIs

You need to audit keys, costs, and usage visibility

You’re explaining /status or /usage cost reporting

API Usage and Costs

API usage & costs

This doc lists features that can invoke API keys and where their costs show up. It focuses on OpenClaw features that can generate provider usage or paid API calls.

Where costs show up (chat + CLI)

Per-session cost snapshot

/status shows the current session model, context usage, and last response tokens.
If the model uses API-key auth, /status also shows estimated cost for the last reply.

Per-message cost footer

/usage full appends a usage footer to every reply, including estimated cost (API-key only).
/usage tokens shows tokens only; OAuth flows hide dollar cost.

CLI usage windows (provider quotas)

openclaw status --usage and openclaw channels list show provider usage windows (quota snapshots, not per-message costs).

See Token use & costs for details and examples.

How keys are discovered

OpenClaw can pick up credentials from:

Auth profiles (per-agent, stored in auth-profiles.json).
Environment variables (e.g. OPENAI_API_KEY, BRAVE_API_KEY, FIRECRAWL_API_KEY).
Config (models.providers.*.apiKey, tools.web.search.*, tools.web.fetch.firecrawl.*, memorySearch.*, talk.apiKey).
Skills (skills.entries.<name>.apiKey) which may export keys to the skill process env.

Features that can spend keys

1) Core model responses (chat + tools)

Every reply or tool call uses the current model provider (OpenAI, Anthropic, etc). This is the primary source of usage and cost.

See Models for pricing config and Token use & costs for display.

2) Media understanding (audio/image/video)

Inbound media can be summarized/transcribed before the reply runs. This uses model/provider APIs.

Audio: OpenAI / Groq / Deepgram (now auto-enabled when keys exist).
Image: OpenAI / Anthropic / Google.
Video: Google.

See Media understanding.

3) Memory embeddings + semantic search

Semantic memory search uses embedding APIs when configured for remote providers:

memorySearch.provider = "openai" → OpenAI embeddings
memorySearch.provider = "gemini" → Gemini embeddings
memorySearch.provider = "voyage" → Voyage embeddings
memorySearch.provider = "mistral" → Mistral embeddings
memorySearch.provider = "ollama" → Ollama embeddings (local/self-hosted; typically no hosted API billing)
Optional fallback to a remote provider if local embeddings fail

You can keep it local with memorySearch.provider = "local" (no API usage).

See Memory.

4) Web search tool

web_search uses API keys and may incur usage charges depending on your provider:

Perplexity Search API: PERPLEXITY_API_KEY
Brave Search API: BRAVE_API_KEY or tools.web.search.apiKey
Gemini (Google Search): GEMINI_API_KEY
Grok (xAI): XAI_API_KEY
Kimi (Moonshot): KIMI_API_KEY or MOONSHOT_API_KEY

See Web tools.

5) Web fetch tool (Firecrawl)

web_fetch can call Firecrawl when an API key is present:

FIRECRAWL_API_KEY or tools.web.fetch.firecrawl.apiKey

If Firecrawl isn’t configured, the tool falls back to direct fetch + readability (no paid API).

See Web tools.

6) Provider usage snapshots (status/health)

Some status commands call provider usage endpoints to display quota windows or auth health. These are typically low-volume calls but still hit provider APIs:

openclaw status --usage
openclaw models status --json

See Models CLI.

7) Compaction safeguard summarization

The compaction safeguard can summarize session history using the current model, which invokes provider APIs when it runs.

See Session management + compaction.

8) Model scan / probe

openclaw models scan can probe OpenRouter models and uses OPENROUTER_API_KEY when probing is enabled.

See Models CLI.

9) Talk (speech)

Talk mode can invoke ElevenLabs when configured:

ELEVENLABS_API_KEY or talk.apiKey

See Talk mode.

10) Skills (third-party APIs)

Skills can store apiKey in skills.entries.<name>.apiKey. If a skill uses that key for external APIs, it can incur costs according to the skill’s provider.

See Skills.

4.6 KiB Raw Blame History Unescape Escape