canonical: https://jentic.com/apis/rawg.io/rawg

# RAWG Video Games Database API

RAWG is a video game database and discovery service, and this API is its read-only query surface over games, platforms, genres, developers, publishers, stores, tags and individual creators. A games query filters by platform, store, genre, tag, developer, publisher, release date window and Metacritic score, and per-game routes return screenshots, trailers, achievements, store links, DLC and parent titles, series entries and the development team. RAWG covers 500,000+ games across 50 platforms. Every call must carry an API key as the `key` query parameter, and the free plan is metered at 20,000 requests per month for non-commercial use, with visually similar games and the Twitch and YouTube video routes reserved for paid plans.

## For AI agents

Programmatically search RAWG's video game database and read game, platform, genre, developer, publisher, store, tag and creator metadata. Covers 30 operations.

## Scope

Read-only video game metadata: does not handle payments, communications, or user accounts, and cannot create or update any RAWG record.

## Capabilities

- Search and filter the game database by platform, store, genre, tag, developer, publisher, release date and Metacritic score
- Retrieve a game's details, screenshots, trailers, achievements, store links, DLC and parent titles, series entries and development team
- Query RAWG Video Games Database API endpoints with structured JSON responses
- Authenticate requests with the RAWG API key, injected at call time by your own Jentic One instance
- Access RAWG Video Games Database API resources programmatically via REST

## Use cases

### Game Data Lookup and Filtering

Query RAWG for game metadata programmatically: filter GET /games by platform, store, genre, tag, release date window or Metacritic score, then follow a game id to its screenshots, trailers, achievements, store links and development team.

Example prompt: Call GET /games with platform and date filters, then GET /games/{id}/screenshots for each result

### Automated Creator Roles Management

Automate creator lookups by combining multiple RAWG Video Games Database API endpoints. Agents can list game creators with GET /creators and then read a specific creator's record with GET /creators/{id} in a single workflow.

Example prompt: Call GET /creators to list game creators, then GET /creators/{id} for each result

### AI Agent Integration via Jentic

AI agents discover and call RAWG Video Games Database API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or paste the RAWG API key into the agent's own configuration.

Example prompt: Search Jentic for 'search for games by platform and release date', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /creator-roles | Get a list of creator positions (jobs). |
| GET | /creators | Get a list of game creators. |
| GET | /creators/{id} | Get details of the creator. |
| GET | /developers | Get a list of game developers. |
| GET | /developers/{id} | Get details of the developer. |
| GET | /games | Get a list of games. |
| GET | /games/{game_pk}/additions | Get a list of DLC's for the game, GOTY and other editions, companion apps, etc. |
| GET | /games/{game_pk}/development-team | Get a list of individual creators that were part of the development team. |

## Key resources

- **Creator Roles** — Operations for creator roles
- **Creators** — Operations for creators
- **Developers** — Operations for developers
- **Games** — Operations for games
- **Genres** — Operations for genres

## Why Jentic

- **Setup:** Wiring the RAWG Video Games Database API by hand means constructing its query parameters for games, creators, and developers, paging through large result sets, and appending your API key to every call yourself. Through Jentic you install once, import the RAWG Video Games Database API from the API Directory, and your agent calls it.
- **Permission scoping:** Every RAWG Video Games Database API operation is a GET, so an agent cannot change anything on RAWG's side, and you still limit it to the operations it needs, such as searching games or listing developers. It only calls the operations you allow, so it looks up game data rather than reaching any other service.
- **Credential handling:** The RAWG Video Games Database API requires an API key on every request. Your own Jentic One instance stores it encrypted and injects it at execution time, so it never enters the agent's prompt, logs, or context and is not written into an agent config file.
- **Discovery method:** Agents search Jentic by intent such as 'find games by a developer' or 'get a list of creator roles', and Jentic returns the matching RAWG Video Games Database API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **IGDB** — Alternative video game metadata API
- **Giant Bomb** — Alternative video game database API

## FAQ

### What authentication does the RAWG Video Games Database API use?

RAWG requires an API key on every request, passed as the `key` query parameter, and you get one from the RAWG developer page. The specification RAWG publishes declares no security scheme even though its own description states that a key is mandatory, so tooling that infers authentication from the specification alone will treat the routes as open. Through Jentic, the key is stored encrypted in your own Jentic One instance and injected at execution time, so the raw secret never enters the agent context.

### Can I search for games with the RAWG Video Games Database API?

Yes. Use the GET /games endpoint, filtering by platform, store, genre, tag, developer, publisher, release date window or Metacritic score. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the RAWG Video Games Database API?

RAWG meters access by monthly request allowance rather than a per-second ceiling. The free plan allows up to 20,000 requests per month and is limited to non-commercial projects that link back to RAWG; the Business plan raises that to 50,000 requests per month and Enterprise to 1,000,000. Three routes are reserved for paid plans: GET /games/{id}/suggested, GET /games/{id}/twitch and GET /games/{id}/youtube. RAWG publishes no burst figure, so plan against the monthly allowance.

### How do I search RAWG games through Jentic?

Install Jentic One on the machine that will host it, then run `jentic register` on the machine where your agent runs to connect the two. Import the RAWG Video Games Database API from the Jentic API Directory, store your RAWG API key once, and search by intent for 'search for games by platform and release date'. Jentic returns the matching operation with its input schema; load it and execute, and the key is injected at call time.

### How many endpoints does the RAWG Video Games Database API have?

The RAWG Video Games Database API exposes 30 endpoints covering games, platforms, genres, developers, publishers, stores, tags and creators. All 30 are GET operations, so the API is read-only.

### Is there a RAWG Video Games Database API MCP server?

You do not need an MCP server to give your agent RAWG. Jentic connects it directly from the API Directory: import the API, store the RAWG API key once in your own Jentic One instance, and your agent calls the 30 GET operations on demand, without another server's tool definitions sitting in its context.

### Can I limit what my agent is allowed to do with the RAWG Video Games Database API?

Yes. Jentic One is self-hosted by you, so your own rules decide which RAWG operations the agent may call and which credentials it may use. Every RAWG operation is a GET, so nothing the agent calls can change data on RAWG's side, and the API key stays with your instance rather than the agent. You can still restrict the agent to just the operations it needs, such as GET /games to search games or GET /developers to list developers, while withholding others like listing creators or fetching a game's development team. Because it only calls the operations you allow, the agent looks up game data and cannot reach any other service.