How do I install the Cdcx Auth Setup skill?

Run npx skillmds@latest add crypto-com/cdcx-auth-setup in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Cdcx Auth Setup safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Cdcx Auth Setup?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Cdcx Auth Setup free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Cdcx Auth Setup?

crypto-com (@crypto-com) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Cdcx Auth Setup by crypto-com — Agent Skill

Name: Cdcx Auth Setup
Author: crypto-com

File contents

Auth & Profile Setup

When to Use

First-time cdcx setup
Configure multiple profiles (e.g. production + UAT)
Verify credentials work
Troubleshoot authentication errors

Resolution Order

cdcx resolves credentials in this order (first match wins):

--api-key / --api-secret command-line flags
CDCX_API_KEY / CDCX_API_SECRET environment variables (preferred prefix)
CDC_API_KEY / CDC_API_SECRET environment variables (legacy prefix)
~/.config/cdcx/config.toml profile (default profile, or --profile <name>)

Setup Methods

Interactive Wizard (recommended)

cdcx setup

Prompts for API key, secret, and profile name. Writes ~/.config/cdcx/config.toml with mode 600. Handles migration from the legacy CDC_ variables.

Environment Variables

export CDCX_API_KEY="your-key"
export CDCX_API_SECRET="your-secret"
cdcx account summary -o json

Prefer this for CI or containers where you don't want a config file on disk.

Config File (manual)

~/.config/cdcx/config.toml:

[profiles.default]
api_key = "your-key"
api_secret = "your-secret"

[profiles.uat]
api_key = "uat-key"
api_secret = "uat-secret"
env = "uat"

Must be mode 600 — cdcx refuses to read world-readable credential files.

Profiles

cdcx --profile uat account summary         # Use UAT profile
cdcx --profile default account summary     # Explicit default

CDCX_PROFILE=uat cdcx account summary      # Env var alternative

Environment Selection

Valid --env values: production (default), uat.

cdcx --env uat market ticker BTC_USDT
cdcx --env production account summary

--env is independent of --profile. You can override either or both per call.

Verify

# Public call (no auth)
cdcx market ticker BTC_USDT -o json

# Auth check
cdcx account summary -o json

# Verbose — shows which profile / env resolved
cdcx --verbose account summary

Troubleshooting

Symptom	Cause	Fix
"No credentials found"	No flags, env vars, or config profile	Run `cdcx setup` or export `CDCX_API_KEY`/`CDCX_API_SECRET`
HTTP 401 / signature invalid	Wrong key/secret or clock skew	Re-run `cdcx setup`; ensure system clock is within a few seconds of UTC
"Permission denied" on config	File mode not 600	`chmod 600 ~/.config/cdcx/config.toml` or re-run `cdcx setup` (auto-fixes)
UAT calls hitting production	`--env` not set on the profile	Add `env = "uat"` to the profile or pass `--env uat`
"Withdrawal not enabled"	API key lacks withdrawal permission	Re-issue the key with withdrawal permission in the Exchange web GUI

Notes

Credentials never appear in cdcx output or logs. Verbose mode only confirms which profile was resolved
Do not commit ~/.config/cdcx/config.toml to version control; it is explicitly not git-tracked
UAT has its own keypair — production keys do not work against UAT and vice versa

---name: cdcx-auth-setupdescription: Credential and profile management — configure API keys via the setup wizard, environment variables, or config file. Resolution order and troubleshooting.---# Auth & Profile Setup## When to Use- First-time cdcx setup- Configure multiple profiles (e.g. production + UAT)- Verify credentials work- Troubleshoot authentication errors## Resolution Ordercdcx resolves credentials in this order (first match wins):1. `--api-key` / `--api-secret` command-line flags2. `CDCX_API_KEY` / `CDCX_API_SECRET` environment variables (preferred prefix)3. `CDC_API_KEY` / `CDC_API_SECRET` environment variables (legacy prefix)4. `~/.config/cdcx/config.toml` profile (default profile, or `--profile <name>`)## Setup Methods### Interactive Wizard (recommended)```cdcx setup```Prompts for API key, secret, and profile name. Writes `~/.config/cdcx/config.toml` with mode 600. Handles migration from the legacy `CDC_` variables.### Environment Variables```export CDCX_API_KEY="your-key"export CDCX_API_SECRET="your-secret"cdcx account summary -o json```Prefer this for CI or containers where you don't want a config file on disk.### Config File (manual)`~/.config/cdcx/config.toml`:```toml[profiles.default]api_key = "your-key"api_secret = "your-secret"[profiles.uat]api_key = "uat-key"api_secret = "uat-secret"env = "uat"```Must be mode 600 — cdcx refuses to read world-readable credential files.## Profiles```cdcx --profile uat account summary # Use UAT profilecdcx --profile default account summary # Explicit defaultCDCX_PROFILE=uat cdcx account summary # Env var alternative```## Environment SelectionValid `--env` values: `production` (default), `uat`.```cdcx --env uat market ticker BTC_USDTcdcx --env production account summary````--env` is independent of `--profile`. You can override either or both per call.## Verify```# Public call (no auth)cdcx market ticker BTC_USDT -o json# Auth checkcdcx account summary -o json# Verbose — shows which profile / env resolvedcdcx --verbose account summary```## Troubleshooting| Symptom | Cause | Fix ||---------|-------|-----|| "No credentials found" | No flags, env vars, or config profile | Run `cdcx setup` or export `CDCX_API_KEY`/`CDCX_API_SECRET` || HTTP 401 / signature invalid | Wrong key/secret or clock skew | Re-run `cdcx setup`; ensure system clock is within a few seconds of UTC || "Permission denied" on config | File mode not 600 | `chmod 600 ~/.config/cdcx/config.toml` or re-run `cdcx setup` (auto-fixes) || UAT calls hitting production | `--env` not set on the profile | Add `env = "uat"` to the profile or pass `--env uat` || "Withdrawal not enabled" | API key lacks withdrawal permission | Re-issue the key with withdrawal permission in the Exchange web GUI |## Notes- Credentials never appear in `cdcx` output or logs. Verbose mode only confirms *which* profile was resolved- Do not commit `~/.config/cdcx/config.toml` to version control; it is explicitly not git-tracked- UAT has its own keypair — production keys do not work against UAT and vice versa

Frequently asked questions

Cdcx Auth Setup