Tavily Key Generator Proxy
Pool many Tavily search API keys behind one FastAPI proxy after automated bulk registration so agent apps get higher monthly query quota from a single endpoint.
Overview
tavily-key-generator-proxy is an agent skill for the Build phase that automates bulk Tavily API key registration and fronts pooled keys with a unified FastAPI proxy gateway.
Install
npx skills add https://github.com/aradotso/trending-skills --skill tavily-key-generator-proxyWhat is this skill?
- Key generator uses Playwright headless Firefox plus CapSolver for Cloudflare Turnstile during Tavily signup flows
- FastAPI proxy in proxy/ exposes /api/search and /api/extract with round-robin rotation, usage tracking, and /console web
- Free Tavily accounts contribute about 1,000 API calls per month each; pooling multiplies quota through one endpoint
- Documented install path: clone skernelx/tavily-key-generator, pip requirements, Playwright browsers
- Designed as ara.so Daily 2026 Skills automation for operators who self-host the generator and proxy stack
- About 1,000 API calls per month per free Tavily account
- Example aggregation: 10 pooled keys ≈ 10,000 calls per month through one proxy endpoint
Adoption & trust: 1.3k installs on skills.sh; 31 GitHub stars; 1/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your agent app exhausts a single free Tavily key and you want one stable endpoint with aggregated monthly search and extract quota.
Who is it for?
Advanced indie builders self-hosting experimental agent search stacks who accept running Playwright, CapSolver, and FastAPI infrastructure.
Skip if: Production apps that should use official Tavily billing, teams unwilling to run browser-based bulk registration, or environments where automating signups violates provider or legal policies.
When should I use this skill?
When triggers mention Tavily API key generator, batch registration, key pool proxy, CapSolver automation, bulk keys, or rotating Tavily credentials behind one gateway.
What do I get? / Deliverables
You operate a self-hosted key pool and proxy that rotates Tavily keys, tracks usage, and exposes search and extract routes plus a web console.
- Registered Tavily API keys stored in the operator’s pool
- Running FastAPI proxy with /api/search, /api/extract, and /console management UI
Recommended Skills
Journey fit
Bulk key farming and proxy deployment are integration infrastructure built while wiring search into an agent product, not a launch or growth marketing task. The skill combines Playwright registration automation with a round-robin API gateway—classic third-party API integration work for coding agents.
How it compares
Self-hosted key-pool automation with a proxy gateway—not the same as installing a single Tavily MCP server or using one documented API key in your agent.
Common Questions / FAQ
Who is tavily-key-generator-proxy for?
It is for advanced solo builders wiring Tavily search into agents who will self-host the skernelx key generator and FastAPI proxy rather than buying centralized quota.
When should I use tavily-key-generator-proxy?
Use it during Build/integrations while standing up agent retrieval infrastructure that needs rotated Tavily keys and a single /api/search and /api/extract base URL—not for casual one-key experiments.
Is tavily-key-generator-proxy safe to install?
It involves browser automation, third-party CAPTCHA services, and stored API secrets; review the Security Audits panel on this Prism page and assess Tavily terms of service and your compliance obligations before deploying.
SKILL.md
READMESKILL.md - Tavily Key Generator Proxy
# Tavily Key Generator + API Proxy > Skill by [ara.so](https://ara.so) — Daily 2026 Skills collection Automates bulk Tavily account registration using Playwright + CapSolver (Cloudflare Turnstile), then pools the resulting API keys behind a unified proxy gateway with round-robin rotation, usage tracking, token management, and a web console. --- ## What It Does | Component | Location | Purpose | |-----------|----------|---------| | **Key Generator** | root `/` | Playwright-driven headless Firefox registers Tavily accounts, solves Turnstile CAPTCHAs, verifies email, extracts API key | | **API Proxy** | `proxy/` | FastAPI service that round-robins requests across pooled keys, exposes `/api/search` and `/api/extract`, serves web console at `/console` | Each free Tavily account yields **1,000 API calls/month**. The proxy aggregates quota: 10 keys = 10,000 calls/month via one endpoint. --- ## Installation ### Key Generator ```bash git clone https://github.com/skernelx/tavily-key-generator.git cd tavily-key-generator pip install -r requirements.txt playwright install firefox cp config.example.py config.py # Edit config.py with your CapSolver key and email backend python main.py ``` ### API Proxy (Docker — recommended) ```bash cd proxy/ cp .env.example .env # Set ADMIN_PASSWORD in .env docker compose up -d # Console at http://localhost:9874/console ``` --- ## Configuration (`config.py`) ### CAPTCHA Solver (required) ```python # CapSolver — recommended (~$0.001/solve, high success rate) CAPTCHA_SOLVER = "capsolver" CAPSOLVER_API_KEY = "CAP-..." # from capsolver.com # Browser click fallback — free but low success rate CAPTCHA_SOLVER = "browser" ``` ### Email Backend (required — pick one) **Option A: Cloudflare Email Worker (self-hosted, free)** ```python EMAIL_BACKEND = "cloudflare" EMAIL_DOMAIN = "mail.yourdomain.com" EMAIL_API_URL = "https://mail.yourdomain.com" EMAIL_API_TOKEN = "your-worker-token" ``` **Option B: DuckMail (third-party temporary email)** ```python EMAIL_BACKEND = "duckmail" DUCKMAIL_API_BASE = "https://api.duckmail.sbs" DUCKMAIL_BEARER = "dk_..." DUCKMAIL_DOMAIN = "duckmail.sbs" ``` If both backends are configured, the CLI prompts you to choose at runtime. ### Registration Throttle (anti-ban) ```python THREADS = 2 # Max 3 — more = higher ban risk COOLDOWN_BASE = 45 # Seconds between registrations COOLDOWN_JITTER = 15 # Random additional seconds BATCH_LIMIT = 20 # Pause after this many registrations ``` ### Auto-upload to Proxy (optional) ```python PROXY_AUTO_UPLOAD = True PROXY_URL = "http://localhost:9874" PROXY_ADMIN_PASSWORD = "your-admin-password" ``` --- ## Running the Key Generator ```bash python main.py # Prompts: how many keys to generate, which email backend # Output: api_keys.md with all generated keys # If PROXY_AUTO_UPLOAD=True, keys are pushed to proxy automatically ``` Generated `api_keys.md` format (used for bulk import into proxy): ``` tvly-abc123... tvly-def456... tvly-ghi789... ``` --- ## API Proxy Usage ### Calling the Proxy (drop-in Tavily replacement) ```bash # Search — replace base URL only curl -X POST http://your-server:9874/api/search \ -H "Authorization: Bearer tvly-YOUR_PROXY_TOKEN" \ -H "Content-Type: application/json" \ -d '{"query": "latest AI news", "search_depth": "basic"}' # Extract curl -X POST http://your-server:9874/api/extract \ -H "Authorization: Bearer tvly-YOUR_PROXY_TOKEN" \ -H "Content-Type: application/json" \ -d '{"urls": ["https://example.com/article"]}' ``` Tok