403 error cant join arena

[CCC222HAXOR]

• Multiple agents tried
• 403 error on acp token launch despite matching API key/account
• stuck on tokenized even agent had token

[CCC222HAXOR]

REPORT: REGISTRATION DEADLOCK IN DGCLAW-SKILL CLI

--- AGENT DETAILS ---
Agent Name: Degen Trader
Wallet: 0x09Cxxxxxxxxxxxxxxxx
Status: Already Bonded on virtuals.io
Repo: Virtual-Protocol/dgclaw-skill

--- THE PROBLEM ---
There is a circular dependency (deadlock) between 'join' and 'token launch'.

1. I cannot 'join' because the CLI says the agent is not tokenized.
2. I cannot 'token launch' because the CLI says DGCLAW_API_KEY is not set.
3. DGCLAW_API_KEY is only generated AFTER a successful 'join'.

--- ERROR LOGS (COPY-PASTED) ---

root@server1:~/dgclaw-skill# bash scripts/dgclaw.sh join 0x09Cxxxxxxxxxxxxxxxx
Checking agent tokenization...
Error: Agent is not tokenized.
Tokenize your agent first:
acp token launch

root@server1:~/dgclaw-skill# bash scripts/dgclaw.sh token launch SYNX "SynxAIAgent"
Error: DGCLAW_API_KEY not set
Run 'dgclaw.sh join ' to register, or set it in .env

--- ATTEMPTED BYPASS ---

• Set VIRTUALS_API_KEY in .env (Still fails)
• Tried 'join_leaderboard' (Still fails)
• Tried direct 'npx tsx' calls (Module not found/Extension error)

--- REQUEST ---
How do I bypass the DGCLAW_API_KEY check for the initial 'token launch' command? Or how can I manually sync my already-bonded agent to the CLI?

[kahwaipd]

scripts/dgclaw.sh token launch SYNX "SynxAIAgent" is not a valid function. You should use acp token launch <SYMBOL> <DESCRIPTION> command instead.