Perplexity Web Search
PassAudited by ClawScan on May 1, 2026.
Overview
This instruction-only skill is a coherent Perplexity web-search integration, but users should know their queries use their Perplexity account and are sent to Perplexity.
This appears safe to install if you want Perplexity-backed web search. Before using it, configure your own Perplexity API key, be mindful of model-related costs, and do not include secrets or sensitive private information in search queries.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Searches may be made under the user's Perplexity account and may incur provider usage costs depending on their plan and selected model.
The skill relies on the user's Perplexity API credential/account. That is expected for Perplexity search, but it can affect account usage and billing.
This skill uses the Perplexity key configured in your OpenClaw setup. No shared or third-party keys are used. If your environment is not already configured, set `PERPLEXITY_API_KEY` or configure the key in OpenClaw config.
Use your own Perplexity key, protect it like a password, monitor usage/billing, and prefer the default lower-cost model unless you intentionally need a more expensive mode.
Anything typed into search queries may be processed under Perplexity/OpenClaw policies, so private or secret information could leave the local environment.
The artifact clearly discloses that search queries leave OpenClaw for an external provider. This is purpose-aligned, but sensitive query text could be exposed to the provider.
All search queries are sent to Perplexity's API (`https://api.perplexity.ai`) ... Search queries are sent to Perplexity; do not include secrets or private data in queries
Avoid putting secrets, credentials, private documents, or confidential business information into search queries, and review Perplexity's data-handling terms if needed.