Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
What This Skill Does
Covers API key creation and bearer token setup for authenticating external services against Remix's server APIs. Includes a verification step and troubleshooting guidance for common auth failures.
The built-in verification call catches misconfigured keys before they cause silent failures in production.
When to use it
- 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
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: How do I authenticate my service to call the Remix API?
- 1Directs user to remix.gg/api-keys to create a new API key
- 2Instructs user to store the key as a secret in their service runtime
- 3Formats the Authorization header as 'Bearer <api_key>' targeting base URL https://api.remix.gg
- 4Runs a test POST to /v1/agents/games to confirm the key is accepted
- 5Points user to https://api.remix.gg/docs if behavior differs from local documentation
Service is authenticated and making valid calls to the Remix API
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.