refresh-venice-key

Test Venice API key validity and mint a fresh key when expired.

10|4|Updated May 14, 2026
One-click install
npx skills add https://github.com/Liquid-Protocol-Ops/agent-autonomopoly --skill refresh-venice-key
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: refresh-venice-key
Source: https://github.com/Liquid-Protocol-Ops/agent-autonomopoly/tree/main/skills/refresh-venice-key
Command: npx skills add https://github.com/Liquid-Protocol-Ops/agent-autonomopoly --skill refresh-venice-key

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Test Venice API key validity and mint a fresh key when expired or revoked

Core Features & Use Cases

  • Validate current VENICE_API_KEY secret and refresh if needed
  • Mint a fresh inference key by signing a challenge with the agent wallet
  • Update GitHub Actions secret so future skill runs reuse the new key
  • Log results to memory/logs/${today}.md with a descriptive heading

Quick Start

Run the Venice key refresh script to validate the API key and refresh it when expired.

Frequently Asked Questions about refresh-venice-key

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically refresh expired Venice API keys in GitHub Actions?

To automatically refresh Venice API keys in CI, run the refresh script to test validity, sign a challenge with the agent wallet to mint a fresh key, and update the GitHub Secret for future workflow runs.

What is the process for minting a fresh Venice inference key when the old one is revoked?

Minting a fresh Venice inference key when revoked requires signing a cryptographic challenge with your agent wallet, which generates a new key that is then automatically pushed to your GitHub Secrets.

Do I need an agent wallet and aeon.yml to rotate Venice API keys in CI/CD?

Yes, rotating Venice API keys in CI requires an agent wallet to sign the challenge and access to aeon.yml for gateway configuration, alongside a valid Venice API endpoint.

Can I validate Venice API key validity without manually triggering a new key mint?

Yes, the script first tests the current Venice API key validity and only mints a fresh key if the existing one is expired or revoked, otherwise leaving the valid secret intact.

Why do my Venice API keys keep failing in automated workflows?

Venice API keys fail in automated workflows when they expire or are revoked. Without an automated refresh script, CI runs attempt to use stale credentials instead of minting fresh keys via wallet-signed challenges.

Where are Venice API key refresh logs stored after a CI pipeline run?

Venice API key refresh logs are written to memory/logs/${today}.md with a descriptive heading, recording whether the script validated the existing key or minted a new one during the workflow run.