Skip to main content

Introduction

This is the documentation for Blazium Games. Blazium Games is the platform for playing and publishing games, applications, mods, and assets.

The platform​

Players browse the catalog, keep a library, and use the desktop app on Windows and Linux. Publishers host a profile and a page for each project, with a press kit and lists of mods and tools.

The files crawlers and agents read — robots.txt, sitemaps, security.txt, the API catalog, and llms.txt — are listed in Discovery files.

Start here​

  • MCP: connect Cursor, VS Code, Claude Code, or any MCP client so an AI agent can manage your store pages, builds, channels, analytics, crash reports, bug tickets, reviews, and game keys.
  • Player MCP: let an agent act for you as a player: recommendations, catalog search, reviews, bug reports, friends, and purchases within your spending limits.
  • Cursor plugin: the official plugin bundles the MCP server with skills for common workflows.
  • Deploy builds: upload builds, symbols, and store images with the chauffeur CLI, the API, or GitHub Actions.
  • Crash reporting: send crashes and events from your game.
  • Payments: sell games or take donations, buy games, top up your balance, cash out, refunds, and agent purchases.
  • Linked accounts and sign-in: link GitHub, X, or Discord, log in with them, and unlink them.
  • Graphical assets guidelines: image sizes for your store page.
  • Editor asset library: paste one repository URL into Godot or Blazium so the AssetLib can list and install packages from Blazium Games.
  • Anonymous downloads: let anyone download a free project without an account, and what that gives up.
  • Download analytics: where downloads come from, how players had access, and refused attempts.
  • Public API reference: the OpenAPI description, authentication, error codes, and rate limits of the public API.

Help​