version: "1.0.0" name: crypto-com-app description: "Execute crypto trades (buy, sell, swap, exchange), manage cash deposits and withdrawals, and query account balances, market prices, and transaction history via the Crypto.com APP API. View weekly trading limits, portfolio positions, bank accounts, and payment networks. Use when the user wants to trade cryptocurrency, deposit or withdraw cash, check bank account details, view deposit instructions, or manage fiat wallet operations. Supports BTC, ETH, CRO, and 200+ tokens across fiat and crypto wallets." user-invocable: true metadata: author: "Crypto.com" version: "1.0.2" homepage: "https://crypto.com" license: "Apache-2.0" tags: ["crypto", "trading", "api"]

Skill: crypto-com-app

Agent Capability Requirements

This skill requires your agent platform to support the following capabilities. If your platform lacks any required capability, the skill will not function.

CRITICAL: How This Skill Works

You MUST use the TypeScript scripts for ALL API interactions. NEVER call the API directly with `curl`, `fetch`, or any other HTTP method.

The scripts handle request signing, error handling, and response formatting. If you bypass them:

• The request will fail (missing HMAC signature)
• The response won't be filtered or structured

For every user request, find the matching command below and run it via `npx tsx`. Read the JSON output. Act on it.

Configurations

• BASE_URL: https://wapi.crypto.com
• CDC_API_KEY: {{env.CDC_API_KEY}}
• CDC_API_SECRET: {{env.CDC_API_SECRET}}
• CONFIRMATION_REQUIRED: {{memory.confirmation_required}} (Default: true)
• SKILL_DIR: The directory containing this SKILL.md file. Resolve it from the path you loaded this file from (e.g. if you read /home/user/skills/crypto-com-app/SKILL.md, then SKILL_DIR is /home/user/skills/crypto-com-app).

Environment Setup

• Both CDC_API_KEY and CDC_API_SECRET must be set as environment variables before use.
• Before running any script, check whether both variables are set by running:

``bash echo "CDC_API_KEY=${CDC_API_KEY:+set}" "CDC_API_SECRET=${CDC_API_SECRET:+set}" ` If either prints empty instead of set, prompt the user: > "Your API credentials are not configured. Please set them in your terminal before I can proceed: > ` > export CDC_API_KEY="your-api-key" > export CDC_API_SECRET="your-api-secret" > `` > You can generate an API key at https://help.crypto.com/en/articles/13843786-api-key-management. > Let me know once you've set them."

Then stop and wait for the user to confirm before retrying.

• If a script returns a MISSING_ENV error, treat it the same way: prompt the user to set the variables and wait.

Script Commands

ALL API interactions MUST go through these scripts. They handle signing, execution, filtering, and error formatting. Run the appropriate command below via shell, then parse the JSON output.

Prerequisite: npx tsx (Node.js 18+ required; tsx is fetched automatically by npx).

Important: All script paths below use $SKILL_DIR as a placeholder for this skill's root directory. Resolve it from the path you loaded this SKILL.md from, or cd into the skill directory and use ./scripts/... as the path. Either approach works.

Account Commands

# Filtered non-zero balances (scope: fiat | crypto | all)
npx tsx $SKILL_DIR/scripts/account.ts balances [fiat|crypto|all]
 
# Single token balance lookup
npx tsx $SKILL_DIR/scripts/account.ts balance <SYMBOL>
 
# Weekly trading limit
npx tsx $SKILL_DIR/scripts/account.ts trading-limit
 
# Find funded source wallets for a trade type
npx tsx $SKILL_DIR/scripts/account.ts resolve-source <purchase|sale|exchange>
 
# Kill switch — revoke API key
npx tsx $SKILL_DIR/scripts/account.ts revoke-key

Trade Commands

Trading follows a two-step flow: get a quotation first, then confirm the order.

# Step 1 — Get quotation (type: purchase | sale | exchange)
npx tsx $SKILL_DIR/scripts/trade.ts quote <type> '<json-params>'
# Returns: {"ok": true, "data": {"id": "<quotation-id>", "from_amount": {...}, "to_amount": {...}, "countdown": 15, ...}}
 
# Step 2 — Confirm order: pass the data.id from Step 1 as <quotation-id>
npx tsx $SKILL_DIR/scripts/trade.ts confirm <type> <quotation-id>
 
# View recent transactions
npx tsx $SKILL_DIR/scripts/trade.ts history

How to map user intent to trade type:

Quotation JSON params by trade type:

Example — "Buy CRO with 100 USD":

1. Run: npx tsx $SKILL_DIR/scripts/trade.ts quote purchase '{"from_currency":"USD","to_currency":"CRO","from_amount":"100"}'
2. Read data.id, data.from_amount, data.to_amount, data.countdown from the response.
3. If confirmation required (default): Ask user "Confirm: 100 USD for X CRO? Valid for {countdown}s. Reply 'YES' to proceed."

• If user says YES (within countdown): npx tsx $SKILL_DIR/scripts/trade.ts confirm purchase <data.id>

1. If confirmation opted out (memory.confirmation_required is false): Skip asking and immediately run npx tsx $SKILL_DIR/scripts/trade.ts confirm purchase <data.id>

Opt-in / Opt-out: Users can say "stop asking for confirmation" to auto-execute trades, or "require confirmation" to re-enable the prompt. See Section 3 below.

Coin Discovery Commands

# Search coins
npx tsx $SKILL_DIR/scripts/coins.ts search '{"keyword":"BTC","sort_by":"rank","sort_direction":"asc","native_currency":"USD","page_size":10}'

Required JSON parameters:

Optional: page_token — opaque token for fetching the next page (see pagination below).

Pagination: The response includes a pagination object with has_more (boolean) and next_page_token (string). When has_more is true, pass next_page_token as page_token in the next request to fetch the next page.

Key response fields per coin: rails_id (identical to currency_id / currency in trade and account APIs — use this to cross-reference), price_native, price_usd, percent_change_*_native (price performance over past timeframes, e.g. percent_change_24h_native).

Cash (Fiat) Commands

Cash commands handle deposits, withdrawals, and bank account management.

# Cash overview — balances + available payment networks per currency
npx tsx $SKILL_DIR/scripts/fiat.ts discover
 
# Payment networks for a currency
npx tsx $SKILL_DIR/scripts/fiat.ts payment-networks <CURRENCY>
 
# Deposit method details (bank routing info)
npx tsx $SKILL_DIR/scripts/fiat.ts deposit-methods <CURRENCY> <DEPOSIT_METHOD>
 
# Email deposit instructions to user
npx tsx $SKILL_DIR/scripts/fiat.ts email-deposit-info <CURRENCY> <VIBAN_TYPE>
 
# Withdrawal details (quotas, fees, minimums)
npx tsx $SKILL_DIR/scripts/fiat.ts withdrawal-details <CURRENCY> <VIBAN_TYPE>
 
# Create withdrawal order (returns order with fees + receivable amount)
npx tsx $SKILL_DIR/scripts/fiat.ts create-withdrawal-order '<json-params>'
 
# Execute withdrawal (may prompt for TOTP authenticator code)
npx tsx $SKILL_DIR/scripts/fiat.ts create-withdrawal <ORDER_ID>
 
# List linked bank accounts
npx tsx $SKILL_DIR/scripts/fiat.ts bank-accounts [CURRENCY]

Key parameters:

Withdrawal order JSON params:

Example — "How do I deposit USD?":

1. Run: npx tsx $SKILL_DIR/scripts/fiat.ts payment-networks USD
2. Read data array — each entry has deposit_push_payment_networks (e.g. ["us_ach", "us_wire_transfer"])
3. For details: npx tsx $SKILL_DIR/scripts/fiat.ts deposit-methods USD us_ach
4. Read data array — contains bank_details with routing number, account number, etc.

Example — "Withdraw 500 USD via ACH":

1. Run: npx tsx $SKILL_DIR/scripts/fiat.ts withdrawal-details USD us_ach — check quotas and fees
2. Run: npx tsx $SKILL_DIR/scripts/fiat.ts create-withdrawal-order '{"currency":"USD","amount":"500","viban_type":"us_ach"}'
3. Read data.id (order ID), data.fee, data.receivable_amount from response
4. Confirm with user: "Withdraw 500 USD via ACH. Fee: {fee}. You'll receive: {receivable_amount}. Confirm?"
5. If YES: npx tsx $SKILL_DIR/scripts/fiat.ts create-withdrawal <order-id>
6. If TOTP required, the script will prompt for a 6-digit authenticator code on stderr

Output Format

Every script prints structured JSON to stdout:

Success:

{"ok": true, "data": { ... }}

Error:

{"ok": false, "error": "ERROR_CODE", "error_message": "Human-readable message"}

Constraints

• Validation: Success requires ok: true in the script output.
• Confirmation Window: Quote validity is defined by the countdown field in the quotation data.
• Execution Warning: If order confirmation takes > 5s, notify: "Order submitted but taking longer than expected. Check order status with 'Show recent trades'".
• Rate Limits:
• Max 10 trades per minute.
• Max 100 API calls per minute.
• On HTTP 429 (RATE_LIMITED error): wait 60 seconds before retrying the same request. Inform the user: "Rate limit reached — please wait 60 seconds before trying again."

Error Handling

All scripts return structured errors. Parse the error field to determine the appropriate response.

Script Error Codes

These are the error values in the script's JSON output. They tell you what category of failure occurred.

Rule: When ok is false in the output, stop the current operation and report the error to the user using the guidance above. Never proceed to the next step after a failure.

Common API Errors (Quick Reference)

These are the specific API error codes that appear inside the error_message of QUOTATION_FAILED, EXECUTION_FAILED, or API_ERROR responses. They tell you why the API rejected the request.

For dynamic errors (limit exceeded, currency disabled, cooling-off, etc.), report the error and error_message directly to the user. For full details, see references/errors.md.

Logic & Rules

1. Asset & Source Disambiguation

Determine the trade type first:

• Purchase — fiat → crypto
• Sale — crypto → fiat
• Exchange — crypto → crypto

Then resolve the source wallet:

• For purchase: run npx tsx $SKILL_DIR/scripts/account.ts resolve-source purchase. The script returns only funded fiat entries.
• For sale or exchange: run npx tsx $SKILL_DIR/scripts/account.ts resolve-source sale (or exchange). The script returns only funded crypto entries.

Result (from `data.status`):

• `SELECTED` → auto-select data.currency.
• `AMBIGUOUS` → prompt user to choose from data.options.
• `EMPTY` → inform user "No funded wallets found" and stop.

"Sell All" Scenario: If user says "Sell all [TOKEN]", run npx tsx $SKILL_DIR/scripts/account.ts balance [TOKEN]. Use the data.available amount (or data.balance) as from_amount for the quotation.

2. Trading Process (Quotation → Confirmation → Execution)

When the user asks to buy, sell, or swap crypto, always follow this three-step flow:

• Step A — Get Quotation: Build the JSON params from the user's request (see the "Quotation JSON params" table in Trade Commands) and run:

npx tsx $SKILL_DIR/scripts/trade.ts quote <type> '<json-params>' Read data.id, data.from_amount, data.to_amount, and data.countdown from the response.

• Step B — Ask User to Confirm:
• IF memory.confirmation_required is true (or unset):
• Prompt: "Confirm: {from_amount} for {to_amount}? Valid for {countdown}s. Reply 'YES' to proceed."
• Expiration Logic: If the user replies "YES" after countdown seconds have elapsed, reject: "Transaction rejected: The quotation rate has expired. Please request a new quote."
• Execute Step C ONLY if user replies "YES" within the valid window.
• ELSE (Opted Out):
• Notify: "Quotation received. Proceeding to execution automatically..."
• Immediately proceed to Step C.

• Step C — Execute Order: Run: npx tsx $SKILL_DIR/scripts/trade.ts confirm <type> <data.id> using the id from Step A.

3. Memory Management (Opt-in/Out)

• To Opt-out: If user says "stop asking for confirmation" or "enable auto-trade", update memory.confirmation_required to false.
• To Opt-in: If user says "require confirmation" or "enable manual trade", update memory.confirmation_required to true.
• Platforms without persistent memory: If your platform does not support {{memory.*}}, treat confirmation_required as always true (safest default).

4. Error Handling

• All script outputs include an ok field. Success is defined ONLY as ok: true.
• If ok is false, read error and respond per the Error Handling table above.
• Never proceed to the next step after a failed command.

5. Account & History

• History: Run npx tsx $SKILL_DIR/scripts/trade.ts history — display the entries from data.
• Weekly Trading Limit: Run npx tsx $SKILL_DIR/scripts/account.ts trading-limit — display as: "📊 Weekly Trading Limit: {data.used} / {data.limit} USD (Remaining: {data.remaining} USD)".
• Fiat vs Crypto balance routing: When the user asks about a specific currency balance, determine whether it is a fiat currency (USD, EUR, GBP, AUD, SGD, CAD, BRL, etc.) or a crypto token (BTC, ETH, CRO, etc.).
• Fiat currency → run npx tsx $SKILL_DIR/scripts/account.ts balances fiat (shows all fiat balances) or npx tsx $SKILL_DIR/scripts/fiat.ts discover (shows balances + payment networks). Never use balance <SYMBOL> for fiat currencies — it queries the crypto wallet and will always return 0.
• Crypto token → run npx tsx $SKILL_DIR/scripts/account.ts balance <SYMBOL>.
• Unsure → run npx tsx $SKILL_DIR/scripts/account.ts balances all to show both fiat and crypto.
• Balances (Categorized):
• If "List Fiat": run npx tsx $SKILL_DIR/scripts/account.ts balances fiat.
• If "List Crypto": run npx tsx $SKILL_DIR/scripts/account.ts balances crypto.
• If "List All": run npx tsx $SKILL_DIR/scripts/account.ts balances all. Crucial: Display Fiat category first, followed by Crypto balances below.
• The scripts automatically filter out zero-balance entries. If a category has no entries in the output, display "No holdings" under that header.
• Crypto balances (data.crypto) contain a note field ("available for trading") and a wallets array. Always clarify to the user that these amounts are what's available for trading — total holdings across all products may be higher.
• Portfolio Allocation: When crypto balances are queried, the output may include a portfolio_allocation array — each entry has a product name and price_native (USD value). Display this as a summary of the user's asset distribution across products (e.g. Crypto Wallet, Exchange, Earn, Staking, etc.).
• Single token balance (balance <SYMBOL>) output may include a product_allocation object — keys are product names (e.g. crypto_earn, staking, supercharger, crypto_basket, airdrop_arena) and values are the token amounts held in each. Only non-zero products are included. Summarize these allocations to the user alongside the available-for-trading amount so they see the full picture of where their tokens are held.

6. Kill Switch

• Trigger: User says "STOP ALL TRADING", "kill switch", or similar emergency stop command.
• ALWAYS require explicit confirmation regardless of memory.confirmation_required:
• Prompt: "⚠️ WARNING: This will immediately revoke your API key and disable all trading. A new API key must be generated to resume. Type 'CONFIRM KILL SWITCH' to proceed."
• Execute ONLY if user replies with the exact phrase.
• Execution: Run npx tsx $SKILL_DIR/scripts/account.ts revoke-key.
• On success (`ok: true`): Notify: "🛑 Kill switch activated. API key has been revoked. All trading is disabled. Generate a new API key and update your environment variables to resume."
• On `API_KEY_NOT_FOUND` error: Notify: "API key not found — it may have already been revoked or does not exist."
• Idempotency: Revoking an already-revoked key is not an error; treat it the same as a successful revocation.

7. Balance Display Format

• Fiat Header: "🏦 Fiat Balances"
• Crypto Header: "🪙 Crypto Balances"
• Always list Fiat section before Crypto section when both are requested.
• Never display zero-balance assets. Only show assets with a balance greater than 0. If all assets in a category are zero, show "No holdings" under that header.

8. Cash Deposit & Withdrawal

Terminology: Use "cash" (not "fiat") in user-facing messages. Say "your cash balance" not "your fiat balance".

Currency disambiguation: If the user doesn't specify a currency, run discover first.

• One currency with balance → auto-select it and proceed.
• Multiple currencies with balances → present the list and ask the user to choose before proceeding.
• No balances → inform: "You don't have any cash balances yet." and stop.

Deposit flow:

1. Run discover to show the user their cash currencies and available networks
2. User picks a currency and network — run deposit-methods to get bank details
3. Present the bank details (routing number, account number, bank name, reference)
4. Optionally run email-deposit-info to email instructions to the user
5. Rate limit: email-deposit-info is limited to 5 requests per 30 minutes. On cooldown error, inform user and show the cooldown_in_seconds value.

Withdrawal flow:

1. Run bank-accounts <currency> to list eligible accounts (filter to status: "completed" only)

• One eligible account → auto-select it
• Multiple eligible accounts → present the list (bank name, account identifier, networks) and ask user to choose
• No eligible accounts → inform: "No eligible bank accounts found for {currency}. You need to link a bank account first." and stop

1. Run withdrawal-details to check quotas, fees, and minimums
2. Run create-withdrawal-order with amount, network, and bank_account_id from step 1 — returns order with fees
3. ALWAYS confirm with user before executing (regardless of memory.confirmation_required):

• Show: amount, fee, receivable amount, network, destination bank account, processing time
• Require explicit "YES" to proceed

1. Run create-withdrawal with the order ID
2. TOTP handling: If the API returns totp_required, the script prompts for a 6-digit authenticator code on stderr. The agent should tell the user: "Please enter your 6-digit authenticator code when prompted." Never try to generate or bypass the TOTP.

Bank accounts:

• Run bank-accounts to list linked accounts. Filter by currency if specified.
• Only accounts with status: "completed" are eligible for withdrawals.
• Each account shows withdrawal_payment_networks — use these as valid viban_type values.

Deposit methods — vendor selection:

• deposit-methods returns a vendor_list array. Each vendor has a status field.
• Only show vendors with status: "created" (active). Ignore "uncreated" vendors.
• If multiple created vendors exist, default to the first one in the list.

Cash commands quick reference: