canonical: https://jentic.com/apis/igdb.com/main # IGDB API IGDB, the Internet Game Database, provides access to a comprehensive video game dataset covering games, platforms, characters, companies, genres, and release dates. Queries use the Apicalypse language sent in POST request bodies to filter, sort, and select exactly the fields an application needs. Endpoints also return media such as covers, screenshots, artworks, and videos, plus a search endpoint and a multiquery endpoint for batching several requests. ## For AI agents Lets an AI agent query the IGDB video game dataset for games, platforms, companies, release dates, and media such as covers and screenshots. ## Scope Does not handle game purchases, downloads, or user accounts. Use it for querying video game reference data only. ## Capabilities - Query games and their metadata with Apicalypse filters - Search across games, characters, companies, and collections - Retrieve platforms, genres, themes, and game modes - Fetch media such as covers, screenshots, artworks, and videos - Look up release dates, age ratings, and involved companies - Batch several queries into one multiquery request ## Use cases ### Game catalog enrichment A gaming site or app needs rich metadata for the titles it lists. IGDB returns games with their genres, platforms, companies, release dates, and artwork through Apicalypse queries, so a product can populate detail pages from a single authoritative source. Field selection keeps each response scoped to exactly what the page renders. Example prompt: Query a game by name and return its genres, platforms, release date, and cover image ### Release calendar and discovery A discovery feature needs upcoming and recent releases filtered by platform or genre. IGDB exposes release dates, platforms, and search across resources, letting a feature assemble a release calendar or recommend titles that match a player's interests. Apicalypse sorting and filtering do the selection server-side. Example prompt: Query release dates for a platform in a date window and sort them chronologically ### AI agent game research An AI agent answering questions about video games can ground its answers in IGDB rather than free text. The agent searches for a title, pulls the involved companies, platforms, and ratings, and returns citable fields, keeping game facts sourced from the structured dataset. Multiquery lets the agent gather several resources in one round trip. Example prompt: Given a title, run a multiquery for the game, its cover, and its release dates and return the combined result ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/games` | Query games with Apicalypse filters | | POST | `/search` | Search across resources | | POST | `/platforms` | Query platforms | | POST | `/companies` | Query companies | | POST | `/covers` | Query cover images | | POST | `/release_dates` | Query release dates | | POST | `/multiquery` | Run multiple queries in one request | ## Key resources - **Games** — Query games and count matches with Apicalypse filters - **Search** — Search across games, characters, companies, and collections - **Media** — Retrieve covers, screenshots, artworks, and videos for titles - **Companies and platforms** — Look up companies, platforms, genres, and release dates - **Multiquery** — Batch several resource queries into one request ## Why Jentic - **Setup:** Wiring IGDB by hand means obtaining both a Client-ID and a bearer token, learning the Apicalypse query language, and threading both credentials through every POST. Install Jentic One once, import the API from the Jentic API Directory, and store both credentials once for your agent to reuse. - **Permission scoping:** Scope your agent to the query and search operations you need, since every IGDB request is a read against a resource endpoint. You decide which operations are callable, so an agent can read games and covers without touching the rest. - **Credential handling:** Your IGDB Client-ID and bearer token are stored once, encrypted, by your own Jentic One instance and injected only at execution time. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents find IGDB through Jentic's intent search: a query such as 'look up video game data' matches the game, search, and media operations, which the agent then calls with your stored credentials. ## Related APIs - **RAWG** — Large video game database with metadata, screenshots, and ratings - **Giant Bomb** — Editorial video game database with games, characters, and companies - **Steam** — Storefront and player data for games on Steam - **Riot Games** — Live game and player data for Riot titles ## FAQ ### What can an AI agent do with the IGDB API? An agent can query games, platforms, companies, genres, and release dates, run a search across resources, fetch media such as covers and screenshots, and batch several queries with multiquery. It is a read-only video game reference dataset. ### How does the IGDB API authenticate? IGDB requires two credentials on each request: a Client-ID header and a bearer token obtained through Twitch. Both are sent together, and Jentic injects them at execution time. ### Can I limit what my agent is allowed to do with the IGDB API? Yes. Your Jentic One instance controls which operations an agent may call. Because every IGDB operation is a read query, you can allow just the game and media lookups your workflow needs and withhold the rest. ### What query language does the IGDB API use? IGDB uses Apicalypse, a compact query language sent in the POST request body to filter, sort, and select fields. It lets an agent request exactly the fields it needs in a single call. ### How do I connect the IGDB API to my AI agent with Jentic? Install Jentic One with its setup script, import the IGDB API from the Jentic API Directory, and store your Client-ID and bearer token once. Your agent can then run the query and search operations you allow.