remix-api-key-auth
by chuckstock
Web & Frontend DevelopmentBrief
Configure and verify bearer API key authentication for Remix agent publishing workflows.
Description
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
User asks: How do I authenticate my service to call the Remix API?
- 1
Directs user to remix.gg/api-keys to create a new API key
- 2
Instructs user to store the key as a secret in their service runtime
- 3
Formats the Authorization header as 'Bearer <api_key>' targeting base URL https://api.remix.gg
- 4
Runs a test POST to /v1/agents/games to confirm the key is accepted
- 5
Points 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
- Remix account at remix.gg
- Remix API key generated from remix.gg/api-keys
Installation
clawhub install chuckstock/remix-api-key-authRun the CLI command, or paste the prompt into Claude Code, Cursor, Codex or whichever coding agent you use.