Gate Exchange Autoinvest

Resolving gate-cli (binary path)

Resolve gate-cli in order: (1) command -v gate-cli and gate-cli --version succeeds; (2) ${HOME}/.local/bin/gate-cli if executable; (3) ${HOME}/.openclaw/skills/bin/gate-cli if executable. Canonical rules: exchange-runtime-rules.md §4 (or gate-runtime-rules.md §4).

gate-exchange-autoinvest

The fast auto-invest (DCA) function of Gate Exchange Earn, supporting create, update, stop plans, and query related information.

General Rules

⚠️ STOP — You MUST read and strictly follow the shared runtime rules before proceeding. Do NOT select or call any tool until all rules are read. These rules have the highest priority. → Read exchange-runtime-rules.md first (mirror: exchange-runtime-rules.md on GitHub).

• Only use the gate-cli commands explicitly listed in this skill. Commands not documented here must NOT be run for these workflows, even if other interfaces expose them.

Skill Dependencies

Authentication

• Interactive file setup: when GATE_API_KEY and GATE_API_SECRET are not both set on the host, run gate-cli config init to complete the wizard for API key, secret, profiles, and defaults (see gate-cli).
• Env / flags: gate-cli config init is not required when credentials are already supplied — e.g. both GATE_API_KEY and GATE_API_SECRET set on the host, or --api-key / --api-secret where supported — never ask the user to paste secrets into chat.
• Permissions: Earn (auto-invest) access as required by your API key and deployment.
• Portal: create or rotate keys outside the chat: https://www.gate.com/myaccount/profile/api-key/manage

Installation Check

• Required: gate-cli (install from gate-cli releases or via your environment’s Gate MCP / skills installer).
• Add the directory containing gate-cli to PATH when invoking by name.
• Credentials: When GATE_API_KEY and GATE_API_SECRET are both set (non-empty) for the host, do not require gate-cli config init. When both are unset or empty, remind the operator to run gate-cli config init or to configure GATE_API_KEY / GATE_API_SECRET in the matching skill from the skill library (never ask the user to paste secrets into chat).
• Sanity check: Confirm the CLI works (e.g. gate-cli --version or a read-only earn/auto-invest query from this skill) before plan mutations.

Risk Disclaimer

Digital Asset Trading Risk Statement: Digital asset trading carries significant risks. Prices are subject to high volatility and market manipulation. Past performance is not indicative of future results. This skill provides informational tools only and does not constitute investment advice. Users are solely responsible for their investment decisions. Only invest what you can afford to lose. For full risk disclosure, please visit Gate's official website.

AI Interaction Data Flow

Data Handling Notice: When you use this skill, your queries and account data are processed through AI systems to provide trading assistance. This includes:

• Your trading instructions and preferences
• Account balance and position information (read-only access)
• Historical trading records for context

Important:

• All data transmission is encrypted and follows Gate's privacy policy
• AI processes data in real-time; no long-term storage of your trading data by the AI
• You retain full control; AI only executes trades after your explicit confirmation
• For privacy details, see Gate's Privacy Policy

Feature Modules

Business Rules

Investment Currency Restrictions

• Only USDT or BTC supported as investment currency (the currency deducted each period)
• Target coins can be other assets

Create Plan Constraints

Required Parameters:

• Target coins to invest (asset list)
• Investment amount per period

Optional Parameters (with defaults):

• Investment time: Defaults to daily at 10:00 (can be customized)
• Fund source: Defaults to spot (spot account)
• Fund flow: Defaults to auto_invest (purchased assets remain in Spot account)

Execution Time Restriction:

• Auto-invest only supports execution on the hour (0-23 o'clock)
• plan_period_hour must be an integer from 0 to 23
• Minutes and seconds are not supported; all executions occur at :00
• ⚠️ CRITICAL - Time Zone: plan_period_hour uses UTC time zone
  • When user specifies local time (e.g., "10:00 AM Beijing time"), convert to UTC before passing to API
  • Example: Beijing 10:00 (UTC+8) → UTC 02:00 → set plan_period_hour: 2
  • Fallback: If system time zone cannot be detected, use user's specified hour directly
  • Always show both UTC and local time in confirmation (or note if time zone detection failed)
  • See references/autoinvest-plans.md → Time Zone Handling section for detailed conversion rules

plan_period_day (create plans only):

• Required on create; value must not be 0. Full workflow: references/autoinvest-plans.md → Workflow step 6.
• By plan_period_type:
  • monthly: Day of month 1–30
  • weekly or biweekly: Weekday 1–7 (1 = Monday, 7 = Sunday)
  • daily, hourly, or 4-hourly: Use 1

Investment Amount Limits:

• Minimum amount: Must be ≥ the value returned by gate-cli cex earn auto-invest min-amount
• Maximum amount: Must be ≤ the value returned by gate-cli cex earn auto-invest config
• Before creating a plan:
  1. Call gate-cli cex earn auto-invest min-amount to query the minimum amount
  2. Call gate-cli cex earn auto-invest config to query the maximum amount
  3. Validate that the user's input amount is within the valid range

Target Coins Constraints (for multi-target plans):

• Maximum target coins: A plan can have at most 10 target coins
• Minimum allocation per coin: Each target coin must have at least 10% allocation (ratio ≥ 10)
• Before creating a multi-target plan:
  1. Check that the number of target coins ≤ 10
  2. Check that each coin's ratio ≥ 10
  3. If validation fails, reject immediately with clear explanation

Fund Flow (where purchased assets go): After creating a plan, purchased assets will flow to one of two destinations based on the fund_flow parameter (API field: post-purchase destination):

• fund_flow: "earn" → Assets automatically transfer to Simple Earn to earn interest
• fund_flow: "auto_invest" → Assets remain in Spot account for manual management (default)

Important:

• User should choose fund flow based on their investment strategy
• earn is recommended for passive income on accumulated assets
• auto_invest is recommended if user plans to trade or withdraw assets frequently
• When users refer to Simple Earn (flexible earn) or spot account in any language, map to earn or auto_invest respectively when calling MCP create/update
• Do not use angle brackets (< or >) in user-facing replies.

After Stopping a Plan

• After stopping a plan, automatic deductions will cease
• Purchased assets typically remain in the spot account

Next Purchase Time

• This function does not provide specific query for the next automatic purchase time
• For this information, please visit Gate App or website

gate-cli command index

Auto-Invest Related Tools (11 tools)

Supporting Tools

Query Function Usage

Tool Mapping

Common Query Scenarios

Scenario 1: Query Supported Coins

Example Questions:

• "Which coins can I auto-invest in?"
• "What target coins does auto-invest support?"

Operation: Use the gate-cli cex earn auto-invest coins tool to query, which will return a list of all coins that support auto-invest.

Scenario 2: Query Minimum Investment Amount

Example Questions:

• "What's the minimum amount per period for USDT auto-invest?"
• "What's the minimum amount when BTC is the investment currency?"

Operation: Use the gate-cli cex earn auto-invest min-amount tool, need to specify the investment currency (USDT or BTC) and target coins.

Scenario 3: View Execution History

Example Questions:

• "How many times has my BTC auto-invest been executed recently?"
• "View the recent execution status of this plan"

Operation: Use gate-cli cex earn auto-invest records to view execution records, use gate-cli cex earn auto-invest orders to view specific order details.

Return Information Example:

📋 Auto-Invest Execution Records

- Plan: {Plan name or ID}
- Execution count: {count}
- Latest execution: {amount} {currency} → {target coin}

Scenario 4: Plan Not Found

Situation: No matching auto-invest plan found during query.

Prompt: No matching auto-invest plan found. You can create a new auto-invest plan.

Other Query Functions

• List all plans: Use gate-cli cex earn auto-invest plans to view all your auto-invest plans
• Query configuration: Use gate-cli cex earn auto-invest config to view available auto-invest settings and preset options

Sub-Modules

Routing Rules

Execution

1. Intent Detection: Analyze user request to determine operation type (create/update/stop/top-up/query/compliance)
2. Route Selection:
   • Plan lifecycle operations (create/update/stop/top-up) → Load references/autoinvest-plans.md and follow workflows
   • Query operations → Use Tool Mapping table and call corresponding MCP tools directly
   • Compliance questions → Load references/autoinvest-compliance.md for rules and restrictions
3. Parameter Validation:
   • For write operations: Validate investment currency (USDT/BTC only), amount range, execution time, and for creates plan_period_day per Create Plan Constraints
   • For queries: Extract required parameters from user request
4. Balance Check (for write operations):
   • Call gate-cli cex spot account get to verify sufficient funds
   • For Simple Earn fund source: Call gate-cli cex earn uni lends if applicable
5. Confirmation (for write operations):
   • Display operation summary (Action Draft)
   • Wait for explicit user confirmation
   • Stop plan (gate-cli cex earn auto-invest stop): Show Action Draft and stop — do not call the tool in that same assistant turn. Call stop only after the user's next message contains explicit confirmation (references/autoinvest-plans.md → Scenario 9).
6. MCP Tool Call:
   • Execute the corresponding tool from the MCP tools section (Auto-Invest Related Tools or Supporting Tools tables) only
   • Pass validated parameters
7. Response Formatting:
   • Use Response Template from sub-module documents
   • Include key information: plan ID, amount, currency, targets, cadence

Domain Knowledge

What is Auto-Invest (DCA)?

Dollar-Cost Averaging (DCA) is an investment strategy where you invest a fixed amount at regular intervals, regardless of market conditions. This approach:

• Reduces timing risk by spreading purchases over time
• Averages out entry prices across market volatility
• Removes emotional decision-making from investing
• Suitable for long-term accumulation strategies

Auto-Invest vs Manual Trading

Investment Currency

• Investment currency: The currency deducted from your account each period (USDT or BTC only)
• Target coins: The cryptocurrencies you want to buy (can be any supported coin)
• Example: Invest 100 USDT (investment currency) → Buy BTC (target coin)

Cadence Options

Fund Flow Options

After creating a plan, purchased assets flow to one of two destinations:

Important Notes:

• This setting determines where purchased coins go after each auto-invest execution (post-purchase destination)
• earn maps to Simple Earn; auto_invest maps to spot account. API values align with localized app strings; if docs and the app disagree, follow the in-app wording.
• earn option provides additional passive income on accumulated assets
• auto_invest option gives you full control to trade, withdraw, or transfer at any time
• Default is auto_invest if not specified

Safety Rules

Default: no write without confirmation

Until the user has given explicit confirmation for the current Action Draft, do not call any write tool (gate-cli cex earn auto-invest create, gate-cli cex earn auto-invest update, gate-cli cex earn auto-invest stop, gate-cli cex earn auto-invest add-position). Only read/query operations are allowed—for example: list/detail plans, supported coins, min/max config, execution records and orders, and supporting balance reads (gate-cli cex spot account get, gate-cli cex earn uni lends).

Mandatory Confirmation for Write Operations

All write operations (create, update, stop, add position) MUST follow this confirmation workflow:

1. Display Action Draft: Show complete operation details before execution
2. Wait for Confirmation: Explicitly ask user "Please confirm to proceed"
3. Execute Only After Confirmation: Do not proceed without user's explicit agreement

Stop plan (gate-cli cex earn auto-invest stop): Show Action Draft (plan ID, name, effect: future deductions stop) and end the turn asking for confirmation. Call MCP only after the user's following message explicitly confirms — never call stop in the same assistant response as the first draft, even if the user already named a plan ID.

Stale confirmation

If the user changes any material detail after seeing an Action Draft (amount, targets, cadence, plan ID, fund flow, plan_period_hour, plan_period_day, etc.), treat earlier confirmation as void. Show an updated Action Draft and obtain a fresh explicit confirmation before any write tool call.

Add Position Safety (Critical)

⚠️ The gate-cli cex earn auto-invest add-position tool is extremely sensitive:

• Call EXACTLY ONCE per user confirmation
• NEVER call multiple times for the same request (causes duplicate deductions)
• Always confirm amount with user before calling
• Check balance before calling

Bad practice ❌:

User: "Add more to my plan"
Assistant: [Calls add_position multiple times to show different amounts]

Good practice ✅:

User: "Add more to my plan"
Assistant: "How much would you like to add? Your current plan is 100 USDT per period."
User: "Add 50 USDT"
Assistant: [Shows draft] "Confirm to add 50 USDT?"
User: "Yes"
Assistant: [Calls add_position ONCE]

Parameter Validation

Before calling any write tool:

No Speculation on Next Purchase Time

• Do not calculate or display the next automatic purchase time
• If user asks, direct them to Gate App or website for real-time schedule
• The system does not provide this information via API

Error Handling

Parameter Hygiene

• If a tool parameter is required and the schema provides no default, prompt the user for the value
• Never guess or invent parameter values
• Always validate parameters against Business Rules before calling tools

Judgment Logic Summary

Report Template

Plan Creation Success

✅ Auto-invest plan created

- Invest currency: {USDT|BTC}
- Amount per period: {amount}
- Cadence: {cadence description}
- Target(s): {target coin(s) with ratios if multi-target}
- Fund source: {spot|earn}
- Fund flow: {auto_invest|earn} (spot account|Simple Earn)

Plan Update Success

✅ Auto-invest plan updated

- Plan: {id or name}
- Updated: {changed fields and new values}

Plan Stop Success

✅ Auto-invest plan stopped

- Plan: {id or name}
- Status: Automatic deductions ceased
- Note: Purchased assets remain in {account type}

Top-up Success

✅ Top-up executed

- Plan: {id or name}
- Amount: {amount} {invest_currency}
- Target allocation: {per Business Rules}

Query Response (Plans List)

📋 Your Auto-Invest Plans

{For each plan:}
**Plan {N}: {plan_name}**
- Investment: {amount} {currency} per {cadence}
- Target(s): {coin(s)}
- Execution count: {period} times
- Status: Active

{If no plans:}
You have no active auto-invest plans. Create one to start DCA investing.

Query Response (Supported Coins)

📋 Supported Auto-Invest Coins

{List coins returned by `gate-cli cex earn auto-invest coins`}

You can use any of these coins as targets in your auto-invest plan.

Query Response (Minimum Amount)

📋 Minimum Investment Amount

- Investment currency: {USDT|BTC}
- Target(s): {coin(s)}
- Minimum per period: {min_amount} {currency}

Error Response

❌ {Error type}

{Explanation of what went wrong}

{Actionable suggestion to resolve}

Reference Documentation