OpenClaw · Skill
Remix API Key Auth
Use this skill when a user needs to authenticate an external service/agent for Remix server APIs.
Web & Frontend Development
v0.1.0
VirusTotal: Benign
Install
Start with the primary install command. Alternate entrypoints are included below for ClawHub and OpenClaw CLI users.
Primary command
clawhub install chuckstock/remix-api-key-authClawHub installer
npx clawhub@latest install chuckstock/remix-api-key-authOpenClaw CLI
openclaw skills install chuckstock/remix-api-key-authDirect OpenClaw install
openclaw install chuckstock/remix-api-key-authWhat this skill does
Use this skill when a user needs to authenticate an external service/agent for Remix server APIs.
Why it matters
The built-in verification call catches misconfigured keys before they cause silent failures in production.
Typical use cases
- Connecting an agent service to a Remix project for the first time
- Rotating a compromised or expired Remix API key
- Debugging 401 errors when calling remix.gg endpoints
- Storing Remix credentials in a cloud runtime environment
- Verifying a new key works before deploying to production
Source instructions
Remix API Key Setup
Use this skill when a user needs to authenticate an external service/agent for Remix server APIs.
Steps
- Log in to your Remix account.
- Go to
https://remix.gg/api-keys. - Create a new API key.
- Store it as a secret in your service runtime.
- Send:
Authorization: Bearer <api_key>
- Use base URL
https://api.remix.gg.
Verification
Run a cheap authenticated call first (for example, POST /v1/agents/games in a test project) to verify the key works.
Troubleshooting Invalid API Key
- Check
Authorizationis formatted asBearer <api_key>. - Re-copy the key from
https://remix.gg/api-keysand rotate if needed. - Verify your service is reading the expected secret/env var in the current runtime.
- Confirm the request is server-side and not exposed through browser code.
- If behavior seems inconsistent with local docs, use
https://api.remix.gg/docsas source of truth.