> For the complete documentation index, see [llms.txt](https://docs.finchagentic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.finchagentic.com/configuration.md).

# Configuration

## Tool palettes

| `FINCH_TOOLS`    | Meaning                                        |
| ---------------- | ---------------------------------------------- |
| `core` (default) | Smaller palette — lower LLM context cost       |
| `all`            | Full registered set (**121** tools)            |
| `defi`           | DeFi-focused subset (Base + RH tools included) |

Set in MCP client `env`:

```json
"env": { "FINCH_TOOLS": "all" }
```

Banner / doctor report **exposed** count, not always the full registered total.

## Environment variables

### Account / backend

| Variable              | Required                    | Purpose                        |
| --------------------- | --------------------------- | ------------------------------ |
| `FINCH_SESSION_TOKEN` | Recommended for cloud tools | Session from Finch App / login |
| `FINCH_CONVEX_URL`    | Rarely                      | Override backend site URL      |

### Optional quality

| Variable            | Purpose                                     |
| ------------------- | ------------------------------------------- |
| `FIRECRAWL_API_KEY` | Better web crawl/search                     |
| `GITHUB_TOKEN`      | `github_search_code` and private GitHub ops |
| `ALCHEMY_API_KEY`   | Faster Base RPC (optional)                  |

### Host LLM keys (only when Finch *hosts* inference)

Tools themselves do **not** need an LLM key. Keys matter for:

* CLI agent loop (`finch run`)
* Cron / scheduled agents with no client model
* Some deep research report modes

| Variable            | Purpose                                                         |
| ------------------- | --------------------------------------------------------------- |
| `BANKR_API_KEY`     | Bankr gateway                                                   |
| `ANTHROPIC_API_KEY` | Claude                                                          |
| `OPENAI_API_KEY`    | OpenAI                                                          |
| `OPENAI_BASE_URL`   | OpenAI-compatible self-host (LiteLLM, vLLM, Ollama, OpenRouter) |
| `GROK_API_KEY`      | xAI Grok                                                        |
| `FINCH_PROVIDER`    | Force `bankr` \| `anthropic` \| `openai` \| `grok`              |

## Guided setup

```bash
npx -y -p @finchagentic/mcp@4.0.0 finch setup
```

Picks providers and can enable local vault/memory.

## App (Convex) env — operators only

Finch App backend uses Convex dashboard secrets (not Vite `VITE_*` for Alchemy):

| Secret                             | Role                                                                                 |
| ---------------------------------- | ------------------------------------------------------------------------------------ |
| `ALCHEMY_API_KEY`                  | RPC / balances via server routes                                                     |
| `CUSTOM_LLM_*` / `NINE_ROUTER_KEY` | Terminal / Build models                                                              |
| `BANKR_API_KEY`                    | Platform chat gateway                                                                |
| Wallet encryption keys             | Custodial execution wallets                                                          |
| `MARKET_SETTLEMENT_LIVE`           | API Market paid routing — **off** at soft-launch (free with key; USDG does not move) |

Frontend public env should stay minimal (`VITE_CONVEX_URL`, `VITE_CONVEX_SITE_URL`). Never put Alchemy secrets in `VITE_`.

## Version pin

Always pin `@finchagentic/mcp@4.0.0` in install docs and client configs. Bumping versions is a deliberate changelog event — not silent `@latest`.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.finchagentic.com/configuration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.