Open Video Game Metadata & REST API
HELIX Gaming DB
An open, community-extensible REST metadata API and gaming database for PC, indie, Patreon, and emulation games.
01
Overview
What is HELIX Gaming DB?
HELIX Gaming DB is an open-source, community-extensible gaming metadata database and REST API hosted directly via GitHub Pages CDN. It was created to solve a widespread problem in desktop game launchers and frontend media managers: obscure, indie, Patreon, itch.io, and emulated console titles are frequently absent from or mismatched by mainstream storefront APIs.
By combining authoritative developer catalogs, strict disambiguation rules, and hand-verified artwork from official CDN sources (Steam Akamai, itch.zone, and verified publisher distribution), HELIX Gaming DB guarantees accurate titles, detailed synopses, genres, release dates, and high-resolution artwork without false cross-studio collisions.
100% Verified Metadata
Zero AI hallucinations and zero broken 404 links. Every title and developer profile is rigorously checked against strict JSON schemas.
High-Speed Static REST API
Endpoints are served directly as static JSON files under /api/v1/ with CDN edge caching, zero rate limits, and sub-50ms latency worldwide.
Open Community Curation
Maintained as a public open-source repository. Anyone can propose new game additions, developer profiles, or metadata corrections via GitHub Pull Requests.
02
REST Endpoints
Live API v1 Endpoints
All API endpoints follow a predictable, RESTful static hierarchy under /api/v1/.
They can be queried with standard HTTP GET requests using any programming language or HTTP client.
| Endpoint | Description | Payload Format | Live Resource |
|---|---|---|---|
GET /api/v1/manifest.json |
Database version, total counts, updated timestamp, and endpoint directory. | JSON Object | manifest.json |
GET /api/v1/search/index.json |
Lightweight search index mapping normalized query keys and aliases to game slugs. | JSON Object (entries array) | search/index.json |
GET /api/v1/games/{slug}.json |
Comprehensive metadata, descriptions, genres, release date, and artwork for a game. | JSON Object | crossdressing-in-camelot.json |
GET /api/v1/developers/{slug}.json |
Developer studio profile, aliases, websites, and associated game slugs. | JSON Object | neyor.json |
03
Integration
Client Integration Example
Here is how you can search and fetch game metadata in JavaScript / TypeScript using native fetch:
// 1. Fetch the lightweight search index
const searchRes = await fetch("https://api.helix-origin.club/helix-gaming-db/api/v1/search/index.json");
const searchIndex = await searchRes.json();
// 2. Normalize user query and find matching game slug
const query = "camelot".toLowerCase().replace(/[^a-z0-9]/g, "");
const match = searchIndex.entries.find(entry => entry.keys.includes(query));
if (match) {
// 3. Fetch comprehensive metadata for the matched game
const gameRes = await fetch(`https://api.helix-origin.club/helix-gaming-db/api/v1/games/${match.slug}.json`);
const gameData = await gameRes.json();
console.log(`Title: ${gameData.title}`);
console.log(`Developer: ${gameData.developers.join(", ")}`);
console.log(`Capsule Cover: ${gameData.capsuleImage}`);
}
04
Community
How to Contribute
Adding a new game or developer to HELIX Gaming DB takes just a few minutes:
- Fork the Repository: Fork HELIX-Origin/helix-gaming-db on GitHub.
- Create Game Payload: Add a new JSON file to
api/v1/games/{slug}.jsonfollowing the Game Schema. - Create Developer Profile: If the developer is not yet registered, add their profile to
api/v1/developers/{slug}.json. - Validate & Build Index: Run
npm run build:indexandnpm run test:schemalocally to verify that all JSON files pass validation. - Submit Pull Request: Open a PR with your additions. Automated CI tests will validate your changes instantly!