TachiBot
← Back to Home

Getting Started

  • Introduction
  • Installation
  • Quick Start
  • Examples

Core Features

  • Tools Overview
  • Workflows
  • PingPong Debates

Configuration

  • Tool Profiles
  • Tools Config
  • Themes
  • Usage Stats
  • API Keys

Legal

  • Terms & Conditions
  • Cookie Policy

Loading documentation...

API Keys Setup

Configure API keys for external AI providers. Only add keys for the tools you want to use - many powerful tools require no keys at all.

⚠️ Important Disclaimer

TachiBot is provided as-is under open source license. The author is not responsible for:

  • API costs incurred from using third-party AI services
  • Incorrect or harmful outputs from AI models
  • Service interruptions or API changes from providers
  • Data privacy or security issues with external APIs
  • Any damages resulting from use or misuse of this tool

You are solely responsible for: monitoring your usage, managing costs, reviewing outputs, and ensuring compliance with provider terms of service. Use at your own risk.

See Terms & Conditions for full legal disclaimers.

📋 API Keys by Profile

Different profiles require different API keys. Choose a profile that matches your available keys.

Core Tools (No Keys Required)

These tools work without any API keys:

  • think - Structured reasoning scratchpad (54% improvement per Anthropic research)
  • focus - Multi-model orchestration (requires keys for models used)
  • nextThought - Sequential thinking

Advanced/Workflow Tools (Require API Keys for Models)

These tools use multiple AI models and require corresponding API keys:

  • verifier - Multi-model verification (needs OpenRouter + Google + OpenAI)
  • challenger - Counter-arguments (needs OpenRouter + Google + OpenAI + optionally Perplexity/Grok)
  • scout - Information gathering (needs OpenRouter + Google + OpenAI + optionally Perplexity/Grok for search)
  • pingpong - Model debates (needs API keys for models: default = Grok + Gemini + OpenAI + Qwen)
  • workflow - YAML/JSON workflows (needs API keys for tools called in workflow)

Configuration Options

There are two ways to configure API keys. Pick the one that works best for you:

Option 1: User Config File (Recommended)

Create ~/.tachibot/.env - this works across all projects:

Option 2: Claude Code MCP Config

Add API keys directly in your Claude Code settings (~/.claude.json):

~/.claude.json

Config Priority (v2.8.0+)

When the same key is set in multiple places, this is the priority order (highest wins):

  1. Claude Code MCP config (~/.claude.json env section)
  2. User config (~/.tachibot/.env)
  3. Project .env (development only)

This means you can set defaults in ~/.tachibot/.env and override specific keys per-project in Claude Code.

🚀

NEW: OpenRouter Gateway Mode

v2.1.0

One API key for multiple providers! Enable Gateway Mode to route GPT-5.1, Gemini, and Grok through your OpenRouter account - unified billing, simpler setup.

.env (Gateway Mode)

Benefits

  • 2 API keys instead of 5+
  • Unified billing dashboard
  • Automatic fallbacks

Limitations

  • Perplexity requires direct API
  • Some features may vary
  • Slight latency overhead

Provider Setup Guides

Perplexity API

Required for: perplexity_ask, perplexity_reason, perplexity_research, scout

  1. Sign up at perplexity.ai
  2. Navigate to API settings
  3. Generate an API key
  4. Add to .env: PERPLEXITY_API_KEY=pplx-...

xAI (Grok) API

Required for: grok_reason, grok_code, grok_debug, grok_architect, grok_brainstorm, grok_search

  1. Sign up at console.x.ai
  2. Access API console
  3. Create API key
  4. Add to .env: XAI_API_KEY=xai-...

OpenAI API

Required for: openai_compare, openai_brainstorm

  1. Sign up at platform.openai.com
  2. Navigate to API keys
  3. Create new secret key
  4. Add to .env: OPENAI_API_KEY=sk-...

Google Gemini API

Required for: gemini_brainstorm, gemini_analyze_code, gemini_analyze_text

  1. Visit Google AI Studio
  2. Create API key
  3. Add to .env: GEMINI_API_KEY=AIza...

OpenRouter API

Required for: qwen_coder, kimi_thinking

  1. Sign up at openrouter.ai
  2. Generate API key
  3. Add to .env: OPENROUTER_API_KEY=sk-or-...

Verification

Check which tools are available based on your configured API keys:

Cost Management

Monitor Usage

  • Check provider dashboards regularly
  • Set up billing alerts on each platform
  • Track API calls in workflow logs

Reduce Costs

  • Use tools.config.json to disable expensive tools
  • Limit PingPong rounds (each round = N model calls)
  • Use free tools first (think, focus, challenger)
  • Choose cheaper models (gpt-5.1-codex-mini vs gpt-5.1)

🚨 Cost Warning

Multi-model workflows can be expensive. A 20-round PingPong with 4 models = 80 API calls. Always test with fewer rounds first. You are fully responsible for managing your API costs.

Security Best Practices

  • Never commit .env files to git
  • Use .gitignore to exclude API keys
  • Rotate keys regularly
  • Use separate keys for development and production
  • Review provider security guidelines
.gitignore

Troubleshooting

Tool Not Working

Invalid API Key

  • Check for typos in ~/.tachibot/.env or Claude Code config
  • Verify key hasn't expired
  • Confirm billing is active on provider dashboard
  • Regenerate key if necessary

Config Not Taking Effect

  • Run /mcp in Claude Code to reload MCP servers
  • Check priority order: Claude Code env > ~/.tachibot/.env > project .env
  • Ensure you're using the correct env var name (e.g., GOOGLE_API_KEY not GEMINI_API_KEY)

Rate Limiting

  • Reduce PingPong rounds
  • Add delays between workflow steps
  • Upgrade to higher tier on provider platform

Next Steps

Start using TachiBot with your API keys

Configure Tools
Control costs and token usage
Explore Tools
See what each tool can do
Quick Start
Run your first workflow