ZapBot is the agent that interprets your prompt, picks tools, and executes intents. It powers the CLI, the SDK-AI runtime, and the MCP server.Documentation Index
Fetch the complete documentation index at: https://docs.dzap.io/llms.txt
Use this file to discover all available pages before exploring further.
What it is
In code:CLIAgent in DZapAI. A tool-calling LLM agent built on the Vercel AI SDK with auto-retry and timeout handling.
In production: the brain behind:
- The
dzapaiCLI shell DZapSDK.ask()calls- MCP-exposed actions in Claude Desktop / Cursor
What it can do
| Category | Examples |
|---|---|
| Read | Get balance, price, pool data, news, sentiment |
| Plan | Build a swap/zap path with fees and slippage |
| Execute | Sign + send via session-scoped key (with confirmation) |
| Schedule | Persist recurring actions via the scheduler |
Default configuration
| Setting | Default | Override |
|---|---|---|
| Model | gpt-4o-mini | DZAP_OPENAI_MODEL=gpt-4o |
| Max retries | 2 | DZAP_MODEL_MAX_RETRIES |
| Timeout | 30s | DZAP_MODEL_TIMEOUT_MS |
| Provider | OpenAI | (other providers via Vercel AI SDK) |
Three things to know
- Confirmations matter. For execution paths (swap, zap), ZapBot surfaces a plan and waits for confirmation. Configure in Safety.
- Session-scoped keys. Never load a wallet key into long-lived process memory. ZapBot uses session keys that die with the process.
- Tool calls are auditable. Every call is logged with inputs and outputs in
result.toolCalls.
Next
How it works
Reasoning → tools → intent → execute.
Safety
Session keys, confirmations, limits.