Product

How Jentic Works

From API assessment to production deployment in four simple steps.

Product Overview

PLATFORM

Jentic OneSelf-hosted, open-source control plane between your agents and any APIAPI DirectoryBrowse 10,000+ APIs ready for AI agent integrationAPI ScorecardAssess your APIs for AI-readiness with automated scoringAgentic SandboxSafely simulate AI agents with your production APIsJenticSign in to the Jentic web app

CAPABILITIES

IntegrationConnect AI agents to your existing systemsWorkflowsDiscover and capture successful agent workflowsGovernanceDefine, observe, and enforce AI policies

TOOLS

Arazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually
Pricing
Developers

GET STARTED

DocumentationGuides and API referenceQuickstartGet up and running in minutes

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
Resources
Company
About UsOur mission and teamCareersJoin our teamContactGet in touch
Install Jentic OneBook a Demo
How Jentic WorksJentic OneAPI DirectoryAPI ScorecardAgentic SandboxJenticIntegrationWorkflowsGovernanceArazzo UIArazzo Editor
Pricing
DocumentationQuickstartGitHubOpen Standards
Resources
About UsCareersContact
Request a demoInstall Jentic One
Jentic
For Enterprises
  • Product Overview
  • Agentic Sandbox
  • Book a Demo
For Developers
  • Jentic One
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

Terms & Conditions•Privacy Policy•
© 2026 Jentic. All rights reserved.
APIs / Media / RAWG Video Games Database API
RAWG Video Games Database API logo

RAWG Video Games Database API

✓ Official Vendor SpecMediaContent DeliveryapiKey30 EndpointsREST

For Agents

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

Use for: I need to search for video games by platform, genre and release date, I want to get the details of a specific game, I need the screenshots and trailers for a game, I want to find which stores sell a game

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

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.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the RAWG Video Games Database API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the RAWG Video Games Database 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.

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Frawg.io%2Frawg" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Frawg.io%2Frawg" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with RAWG Video Games Database API.

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

Patterns agents use RAWG Video Games Database API for, with concrete tasks.

★ 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.

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.

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.

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

Key Endpoints

30 endpoints — 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.

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.

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.

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

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

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 management

Credential isolation

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.

Intent-based discovery

Intent-based discovery

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

Alternatives and complements available in the Jentic catalogue.

Alternative

IGDB

→

Alternative video game metadata API

Choose IGDB when you need game metadata under a different licence and access model

Alternative

Giant Bomb

→

Alternative video game database API

Choose Giant Bomb when you need its editorial game, character and franchise records

FAQs

Specific to using RAWG Video Games Database API through Jentic.

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.

GET STARTED

Start building with RAWG Video Games Database API

Explore with Jentic One
View OpenAPI Document