Coinbase Smart DCA Bot

For Claude: How to Use This Skill

Skill instructions are preloaded in context when this skill is active. Do not perform filesystem searches or tool-driven exploration to rediscover them; use the guidance below directly.

AI-assisted dollar-cost averaging (DCA) bot for Coinbase Advanced Trade with three modes:

• single_asset
• portfolio
• opportunity_scanner

All trades execute locally and directly against Coinbase APIs.

When to Use

• run smart dca on coinbase
• optimize recurring crypto buys
• rebalance dca portfolio allocations
• scan for dca opportunities with approval controls

What This Skill Provides

• Mode 1 (single_asset) with execution strategies:
  • vwap_optimized
  • momentum_dip
  • spread_optimized
  • time_weighted
  • simple
• Mode 2 (portfolio) with target allocations and drift-aware DCA
• Mode 3 (opportunity_scanner) with signals:
  • oversold_rsi
  • volume_spike
  • mean_reversion
  • new_listing
  • learn_earn
• Coinbase-specific route selection (ASSET-USD vs ASSET-USDC)
• Optional staking context and post-buy staking hints
• First-run Seren API key auto-registration (SEREN_API_KEY)
• Optional SerenDB persistence (SERENDB_URL)
• JSONL audit logs in logs/
• Cost-basis lot tracking in state/cost_basis_lots.json
• Dry-run default, explicit live opt-in

Setup

1. Copy .env.example to .env and set credentials.
2. Copy config.example.json to config.json.
3. Install dependencies:
   • pip install -r requirements.txt
4. (Optional) initialize SerenDB schema:
   • python scripts/setup_serendb.py
5. Run dry mode:
   • python scripts/agent.py --config config.json --accept-risk-disclaimer
6. Run live mode (explicit opt-in only):
   • set "dry_run": false in config.json
   • python scripts/agent.py --config config.json --allow-live --accept-risk-disclaimer

Workflow Summary

1. Validate config and risk policy caps.
2. Ensure SEREN_API_KEY (validate existing or auto-register).
3. Build market snapshots and select execution route (USD vs USDC).
4. Compute strategy decision and risk-gate execution.
5. Execute locally to Coinbase (or simulate in dry-run).
6. Persist runs, snapshots, signals, and cost-basis lots.
7. Emit structured audit logs.

Required Disclaimers

IMPORTANT DISCLAIMERS — READ BEFORE USING

1. NOT FINANCIAL ADVICE: This skill is automation software, not an advisor.
2. RISK OF LOSS: Crypto trading can lose principal and more in volatile markets.
3. NO GUARANTEES: Optimization logic may not outperform naive scheduled DCA.
4. LOCAL EXECUTION ONLY: Trades run locally and directly against Coinbase.
5. API KEY SECURITY: Coinbase credentials remain local and are never sent to Seren.
6. STAKING RISK: APY varies and staking may involve lockup/slashing risk.
7. REGULATORY/TAX: You are responsible for legal/tax compliance in your jurisdiction.
8. NO AFFILIATION: This skill is not affiliated with or endorsed by Coinbase.

Seren-Cron Integration

Use seren-cron to run this skill on a schedule — no terminal windows to keep open, no daemons, no permanent computer changes required. Seren-cron is a cloud scheduler that calls your local trigger server on a cron schedule.

Requirements: Seren Desktop login or a valid SEREN_API_KEY.

Step 1 — Check seren-cron is available

Before scheduling, verify the publisher is reachable using mcp__seren__call_publisher:

publisher: seren-cron
path:      /health
method:    GET

If this call fails, stop here and tell the user:

"The seren-cron service could not be reached. Please send this error to hello@serendb.com for support."

Step 2 — Review active cron jobs (always do this first)

Always check for existing scheduled jobs before creating a new one. A user may have forgotten a live job is already running.

publisher: seren-cron
path:      /jobs
method:    GET

If jobs for this skill already exist, show them to the user and ask:

"You have [N] active cron job(s) for this skill. Would you like to:

1. Keep them running (recommended if intentional)
2. Stop all and create a new schedule
3. Cancel"

Do not create a duplicate cron job without explicit user confirmation.

Step 3 — Start the local trigger server

Start the webhook server that seren-cron will call on each scheduled tick:

SEREN_API_KEY="$SEREN_API_KEY" python3 scripts/run_agent_server.py --config config.json --port 8080

This process runs in your terminal session. When you close the terminal, it stops — that is expected and correct. Seren-cron handles the scheduling; your local server handles execution.

Step 4 — Create the cron schedule

With the server running, create the scheduled job:

publisher: seren-cron
path:      /jobs
method:    POST
body: {
  "name":            "coinbase-smart-dca-live",
  "url":             "http://localhost:8080/run",
  "method":          "POST",
  "cron_expression": "0 */6 * * *",
  "timezone":        "UTC",
  "enabled":         true,
  "timeout_seconds": 60
}

Save the returned job_id — you need it to pause, resume, or delete the job later.

Step 5 — Manage the schedule

List all active jobs:

publisher: seren-cron, path: /jobs, method: GET

Pause:

publisher: seren-cron, path: /jobs/{job_id}/pause, method: POST

Resume:

publisher: seren-cron, path: /jobs/{job_id}/resume, method: POST

Stop permanently:

publisher: seren-cron, path: /jobs/{job_id}, method: DELETE

Insufficient Funds Guard

If a live trade or cycle fails because the trading balance or SerenBucks balance is too low to execute, immediately pause the cron job:

publisher: seren-cron, path: /jobs/{job_id}/pause, method: POST

Then tell the user:

"Automated trading has been paused: insufficient funds detected. Please top up your balance before resuming the schedule."

Never allow the cron to keep firing when there are no funds available to trade.