presearch

Production-ready decentralized search for AI agents. Privacy-first, uncensored web search via distributed node infrastructure.

Security Scan

The skill's runtime instructions require an API key and call an external Presearch endpoint, but the registry metadata does not declare any required credentials or a source/homepage — those mismatches make the package internally inconsistent.

Purpose & Capability

The SKILL.md documents a Presearch HTTP API (Bearer token auth to https://na-us-1.presearch.com/v1/search). The skill description matches that purpose, but the registry metadata lists no required environment variables or primary credential and provides no source/homepage. A search-integration skill would reasonably need an API key declared; its absence is an incoherence.

Instruction Scope

The instructions themselves are narrowly scoped: how to call the GET /v1/search endpoint, parameters, responses, and example snippets. They do not ask the agent to read local files or other unrelated secrets. The notable issue is that the instructions assume an API key (Authorization: Bearer YOUR_API_KEY_HERE) while the skill metadata does not declare one.

Install Mechanism

This is an instruction-only skill with no install spec or code files, so nothing is written to disk or downloaded. That minimizes install-time risk.

Credentials

The runtime docs clearly require a bearer API key (the examples use api_key), but requires.env and primary credential are empty in the registry entry. This mismatch could lead to unclear handling of credentials (where should the key be provided?) and increases the risk of misconfiguration or accidental credential exposure if implementers improvise.

Persistence & Privilege

The skill is not marked always:true and uses default autonomous invocation settings. It does not request persistent system-wide privileges or modify other skills' configs according to the provided metadata.

What to consider before installing

This skill's documentation shows it needs a Presearch API key and calls a presearch.com endpoint, but the registry entry didn't declare any required credentials or a source URL. Before installing: 1) Ask the publisher for the source/homepage and confirm the official Presearch endpoint and auth model; 2) Confirm how/where the API key should be supplied (and that the skill will not try to read unrelated secrets); 3) Prefer skills that declare required.env/primary credential so you can safely manage tokens; 4) Because this is instruction-only, it won't install code, but the metadata mismatch is a red flag — treat it as untrusted until the author provides clarifying metadata or a verified source.

Presearch Search API

Endpoint: https://na-us-1.presearch.com/v1/search
Method: GET
Auth: Bearer Token
Rate Limit: 100 requests/minute

Authentication

Authorization: Bearer YOUR_API_KEY_HERE

Parameters

Parameter	Type	Required	Default	Description
q	string	✅	-	Search query
lang	string	❌	en-US	Language code
time	string	❌	any	any, day, week, month, year
page	string	❌	1	Page number
safe	string	❌	1	Safe search

Response

{
  "data": {
    "standardResults": [
      {
        "title": "string",
        "link": "string",
        "description": "string"
      }
    ],
    "pagination": {
      "current_page": 1,
      "has_next": true
    }
  }
}

Error Codes

• 401: Invalid API key
• 402: Payment required
• 422: Invalid parameters
• 429: Rate limit exceeded

Usage

# Python
with PresearchSkill(api_key) as skill:
    results = skill.search("AI agents")

// Node.js
const results = await skill.search({ query: "AI agents" });

Privacy Features

• No tracking or profiling
• Decentralized node network
• Encrypted traffic
• Uncensored results