What problem does it solve? Standing up a private SearXNG metasearch instance for programmatic agent search involves non-obvious configuration: stock SearXNG serves HTML only, settings are baked into the Docker image at build time, and engine names differ between components. This Skill documents the exact settings, Dockerfiles, and failure modes so the instance works as a JSON search backend. ## Core Features & Use Cases - Settings guidance: Explains searxng-settings.yml essentials including JSON output format, secret key generation, limiter behavior, and Redis/valkey caching. - Deployment recipes: Covers the dev Dockerfile, the Redis-backed Dockerfile.redis variant, local docker run commands, and Render.com deployment. - Agent integration: Clarifies how chat-agent-toolkit's searchSearxng consumes the instance and why MetaSearchAgent engine names use spaces instead of underscores. - Troubleshooting table: Maps symptoms like 403 on format=json, ignored settings edits, and rate limiting to concrete fixes. - Use Case: Your agent's SearXNG endpoint returns 403 instead of JSON; use this Skill to identify that json is missing from search.formats and redeploy with the correct settings file. ## Quick Start Ask the assistant to explain why your SearXNG instance returns 403 on JSON requests and how to fix the settings file.
