RAWG Video Games Database API

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.