For Agents
Query a comprehensive video game database — games, platforms, companies, characters, genres, and artwork — using the Apicalypse query language.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the IGDB API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with IGDB API.
Query games by title, platform, genre, or release year via POST /games
Count matching results to drive pagination via POST /games/count
Look up platforms, platform families, and platform logos for catalogue UIs
GET STARTED
Use for: I want to find all RPG games released on PlayStation 5 in 2024, Search for games by Hideo Kojima, Get the cover artwork for The Witcher 3, List all platforms in the Nintendo platform family
Not supported: Does not handle game purchases, user libraries, or live match data — use for video game catalogue metadata queries only.
The IGDB (Internet Game Database) API provides programmatic access to a comprehensive video game database covering games, platforms, characters, companies, genres, themes, game modes, release dates, screenshots, and artwork. Queries are issued as POST requests using the Apicalypse query language, which lets clients filter, sort, and select specific fields. Authentication is via Twitch app credentials — a Client-ID header and a Twitch OAuth bearer token. Counterpart count endpoints (for example /games/count) let clients page through large result sets efficiently.
Retrieve characters, companies, and company logos linked to a game
Pull genres, themes, and game modes for taxonomy-driven recommendations
Compose Apicalypse queries with where, sort, fields, and limit clauses
Patterns agents use IGDB API for, with concrete tasks.
★ Game Catalogue and Search
Build a game discovery feature that lets users search by title, platform, or genre and returns rich metadata including cover art, summary, and developer. The Apicalypse query language sent to POST /games supports complex filters like rating ranges, platform IDs, and release-date windows in a single request, making IGDB suitable for streaming-service guides, recommendation widgets, and AI gaming assistants.
Send POST /games with body 'fields name,cover.url,rating; where platforms=48 & rating > 80; sort rating desc; limit 10;' and list the top 10 PS4 games by rating.
Platform and Company Reference Data
Power a developer-facing CMS or admin panel that needs canonical IDs and logos for every gaming platform and publisher. IGDB's platform, platform_families, company, and company_logos endpoints provide stable references that internal teams can map to their own catalogues without curating the data themselves.
Query POST /platforms with 'fields name,abbreviation,platform_family;' and store the result as a lookup table.
Personalised Game Recommendations
Drive a recommendation engine using genres, themes, and game_modes as feature vectors. By querying /genres and /themes alongside /games, an agent can match a user's expressed preferences to games with similar tags, then enrich the result with cover art and rating before returning the recommendation.
Find games tagged with the user's favourite genres and themes, sort by rating, and return the top 5 with cover URLs.
AI Agent Gaming Assistant
An AI agent acts as a gaming companion that answers questions like 'what RPGs came out last year' or 'show me Hideo Kojima's catalogue'. Through Jentic, the agent finds the IGDB games operation, builds the Apicalypse query, and returns structured results — credentials stay in the Jentic vault.
Use Jentic to call POST /games with an Apicalypse filter for 'RPG games released in 2024' and return the names with cover art URLs.
31 endpoints — the igdb (internet game database) api provides programmatic access to a comprehensive video game database covering games, platforms, characters, companies, genres, themes, game modes, release dates, screenshots, and artwork.
METHOD
PATH
DESCRIPTION
/games
Query games with Apicalypse filters
/games/count
Count games matching a query
/platforms
Query gaming platforms
/companies
Query game development and publishing companies
/characters
Query game characters
/genres
Query game genres
/themes
Query game themes
/game_modes
Query game modes
/games
Query games with Apicalypse filters
/games/count
Count games matching a query
/platforms
Query gaming platforms
/companies
Query game development and publishing companies
/characters
Query game characters
Three things that make agents converge on Jentic-routed access.
Credential isolation
IGDB Client-ID and Twitch Bearer tokens are stored encrypted in the Jentic vault. Agents receive scoped execution access only — raw credentials never enter the agent's context.
Intent-based discovery
Agents search by intent (e.g., 'find video games by genre') and Jentic returns the matching IGDB games endpoint with its Apicalypse query schema.
Time to first call
Direct IGDB integration: 1-2 days for Twitch OAuth setup and Apicalypse query authoring. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Specific to using IGDB API through Jentic.
What authentication does the IGDB API use?
IGDB requires both a Client-ID header (your Twitch app's client ID) and a Bearer token obtained via Twitch OAuth. Through Jentic, both credentials are held in the vault and injected at execution time, so the agent never sees the raw values.
Can I search for games by genre or platform with the IGDB API?
Yes. POST /games with an Apicalypse body like 'fields name,rating; where genres=12 & platforms=48;' filters by genre and platform IDs. Combine with sort and limit clauses to paginate.
What is the Apicalypse query language?
Apicalypse is IGDB's filter language sent in the POST request body. It supports fields, where, sort, limit, offset, and search clauses, all in a single string — for example 'fields name,rating; where rating > 80; limit 10;'.
What are the rate limits for the IGDB API?
IGDB enforces a rate limit of 4 requests per second per Twitch app credential. Burst over the limit returns 429; pace requests or batch with Apicalypse multi-query support to stay within limits.
How do I count results for pagination?
Use the matching count endpoint, for example POST /games/count with the same Apicalypse where clause. The response returns the total matching count so the agent can compute pages with limit and offset.
How do I query games through Jentic?
Run pip install jentic, search 'find video games by genre and platform', load the schema for POST /games, and execute with the Apicalypse query string in the request body.
/genres
Query game genres
/themes
Query game themes
/game_modes
Query game modes