refresh-venice-key
Test Venice API key validity and mint a fresh key if expired or revoked
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Test Venice API key validity and mint a fresh key if expired or revoked
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Launch a Liquid Protocol token with a LiquidPresaleVault presale. STAKE MODE ONLY (policy 2026-06-12) — depositors lock DIEM and always get it back; allocation is lock-to-earn. One vault per launch, 10% of supply, 60d default lock.
Weekly audit of memory/goals.json — recompute milestone ETAs, self-funding ratio, mode consistency; report deltas and one recommendation to the creator
Proactive ambient check — surface anything worth attention
Analyze AUTONO's own performance and implement one high-impact improvement today
Safety net for Venice inference credits — if sDIEM is below stake_min_diem, queue a stake-diem intent for the gated executor
Run one AUTONOMOPOLY agent tick — claim fees, LP DIEM, LP range check + reposition, maintenance inference
| name | refresh-venice-key |
| description | Test Venice API key validity and mint a fresh key if expired or revoked |
| tags | ["ops","venice","self-heal"] |
Test whether the current VENICE_API_KEY secret is still valid. If it returns 401 (expired or revoked), mint a fresh inference key by signing a challenge with the agent wallet, then update the GitHub Actions secret so all future skill runs use the new key automatically.
Run:
node --import tsx scripts/refresh-venice-key.ts
The script exits 0 in all non-error cases. Read its stdout to determine what happened:
"Key is valid — no action needed" → key is fine; nothing to do"Done — fresh key written" → key was stale; secret updatedLog the result to memory/logs/${today}.md under a ### refresh-venice-key heading:
refresh-venice-key: key valid — no action needed
or:
refresh-venice-key: key expired — fresh key minted and GitHub secret updated
If the script fails (non-zero exit), log the error and send a Telegram notification via the notify skill:
After a successful key refresh, also verify the gateway in aeon.yml is set to provider: venice (not direct). If it was switched to direct as a workaround, switch it back:
grep "provider:" aeon.yml
If the output shows provider: direct, update aeon.yml:
gateway:
provider: venice # primary: sDIEM-gated inference
Then commit and push the change.