remix-api-reference
OpenAPI-first endpoint reference for Remix game publishing REST routes
Best use case
remix-api-reference is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
OpenAPI-first endpoint reference for Remix game publishing REST routes
Teams using remix-api-reference should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/remix-api-reference/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How remix-api-reference Compares
| Feature / Agent | remix-api-reference | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
OpenAPI-first endpoint reference for Remix game publishing REST routes
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
## OpenAPI-First Rule
Before generating or executing API calls, fetch:
- `https://api.remix.gg/docs/json`
Use OpenAPI as the contract source of truth for:
- methods (`GET`/`POST`/...)
- paths
- params/query/body schemas
- response shapes
Base headers:
```http
Authorization: Bearer <api_key>
Content-Type: application/json
```
Base URL: `https://api.remix.gg`
OpenAPI UI: `https://api.remix.gg/docs`
## Response Envelope
Success:
```json
{ "success": true, "data": { "...": "..." } }
```
Error:
```json
{ "success": false, "error": { "code": "SOME_CODE", "message": "...", "details": null } }
```
## Endpoint Families
Use OpenAPI for exact paths; these are the stable groups:
- Metadata: categories
- Games: list/detail/create/update
- Analytics: overview, shop, and leaderboard analytics for owned games
- Versions: list/detail/code/thread/status/validate/code-update
- Assets: list game assets, upload assets via `POST /v1/games/{gameId}/assets`
- Images: generate images via `POST /v1/games/{gameId}/images/generate`
- Shop images: generate shop icon art via `POST /v1/games/{gameId}/images/generate-shop-icon`
- Sprites: generate sprites via `POST /v1/games/{gameId}/sprites/generate`
- Items: manage shop items via `GET/POST /v1/games/{gameId}/items`, `POST/DELETE /v1/games/{gameId}/items/{itemId}`
- Readiness: launch readiness checks
## Not Exposed in Agent REST
- No delete route.
- No create-version route.
- No submit route.
## Asset Upload
Asset uploads are available via `POST /v1/games/{gameId}/assets`. You can upload binary files (icons, sprites, audio) directly through the API.
Assets can also be managed through the Remix app/Studio upload flow.
Canonical flow:
1. create game
2. upload/update version code
3. upload assets as needed via `POST /v1/games/{gameId}/assets`
4. optionally inspect analytics via the overview/shop/leaderboard endpoints
5. validate and/or launch-readiness
6. check status
## Common Error Codes
- `UNAUTHORIZED` - Missing/invalid API key.
- `ACCOUNT_INELIGIBLE` - User is banned/deleted.
- `FORBIDDEN` - User does not own the game/version.
- `GAME_NOT_FOUND` - Game missing.
- `VERSION_NOT_FOUND` - Game/version mismatch or missing.
- `MAX_IN_DEV_GAMES_EXCEEDED` - Creator reached cap.
- `VALIDATION_ERROR` - Body/query failed validation.
- `INVALID_JSON` - Body could not be parsed as JSON.
- `LIVE_VERSION_LOCKED` - Attempted to edit a live version.
- `VERSION_NOT_EDITABLE` - Version is submitted/approved/launched.
- `THREAD_CREATE_FAILED` - Failed to provision upload thread.
- `RATE_LIMITED` - API key rate limit exceeded.
- `INTERNAL_SERVER_ERROR` - Unexpected server failure.Related Skills
remix-upload-game
Upload and validate HTML game code for Remix. Use when creating or updating a draft version through the CLI, MCP tools, or direct REST calls.
remix-upload-asset
Upload images, audio, or 3D models as hosted game assets
remix-submission-rules
Validation and publish constraints for Remix game submissions
remix-shop-items
Create, update, delete, and integrate Remix shop items. Use when a game needs Bits items, consumables, one-time unlocks, tier unlocks, store icons, or purchase handling in @remix-gg/sdk code.
remix-save-game
Add save and load game state functionality via RemixSDK
remix-rest-snippets
REST client snippets for Remix agent publishing
remix-open-game
Open a game in the Remix Studio browser for preview and editing
remix-multiplayer
Enable multiplayer support for a Remix game
remix-game-sdk
Reference for the current @remix-gg/sdk runtime. Use when generating or repairing Remix game code, shop item integrations, save-state flows, multiplayer hooks, or host-safe mobile UI behavior.
remix-game-creation
Create a new game draft via the Remix API
remix-game-best-practices
Mobile-first game creation best practices for Remix
remix-cli
Use the official Remix CLI for authentication, config inspection, game creation, uploads, and analytics. Trigger this skill when a task involves `remix login`, `remix whoami`, `.remix-cli.json`, `REMIX_API_KEY`, or terminal-based game management on Remix.