taco

# Taco Trading Platform

## Setup

Config is stored at `~/.openclaw/workspace/taco/config.json`. Each exchange is bound to its own `trader_id`:

```json
{
  "user_id": "<taco user id>",
  "api_token": "<taco api key>",
  "trader_ids": {
    "StandX": "<trader id for StandX>",
    "Binance": "<trader id for Binance>",
    "Hyper": "<trader id for Hyper>",
    "Lighter": "<trader id for Lighter>",
    "Aster": "<trader id for Aster>",
    "Grvt": "<trader id for Grvt>"
  }
}
```

**Key concept:** Exchange and `trader_id` are bound 1:1. When operating on a specific exchange, the CLI automatically uses the corresponding `trader_id` from config. Only configure the exchanges you use.

**First-time setup:** If config does not exist, ask the user for their `user_id`, `api_token`, and each exchange's `trader_id`, then write the JSON file to `~/.openclaw/workspace/taco/config.json` (create parent directories as needed). Alternatively, run the interactive init command:

```bash
$PYTHON scripts/taco_client.py init
```

**Before any API call:** Check that `~/.openclaw/workspace/taco/config.json` exists. If not, guide the user through setup first.

## Python Requirement

Before running any command, detect the available Python 3 command:

```bash
command -v python3 || command -v python
```

- If `python3` is found, use `python3` (and `pip3` for package installs)
- If only `python` is found, verify it is Python 3 with `python --version`. If it reports Python 2.x, treat it as unavailable.
- If neither provides Python 3, ask the user to install Python 3 before proceeding.

Then check the `requests` package: `$PYTHON -c "import requests"`. If it fails, install with `pip3 install requests` (or `pip install requests` if only `pip` is available).

**In all examples below, `$PYTHON` represents the detected Python command.** Store the result once per session and reuse it for every subsequent call.

## Usage

Run the CLI client at `scripts/taco_client.py` (relative to this skill directory)....