Install Jentic One Beta

Connect the mod.io API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the mod.io 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmod.io%2Fmod-io" | sh

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%2Fmod.io%2Fmod-io" | 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 mod.io API.

List games and fetch a single game by its id

List the mods published for a game and fetch one mod with its details

Read a mod's uploaded files and its comments

Add a mod to a game and upload files to it with an OAuth2 token

Subscribe to or unsubscribe from a mod and post a rating

GET STARTED

Start building with mod.io API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use mod.io API for, with concrete tasks.

★ Agent Mod Discovery

An in-game assistant can find and describe mods for a title without the player leaving the game. The agent lists the mods for a game, reads back their names and details, and can fetch a single mod's files, so a request like 'show me popular mods for this game' is answered from the live mod.io catalog rather than a cached list.

List the mods for a game and return the top ones with their descriptions and file details

Managed Mod Publishing

A studio tool can publish and update mods on behalf of a creator using an OAuth2 token. The agent adds a mod to a game, uploads its files, and can post comments, so a submission pipeline runs through the API while the studio keeps the token on its own infrastructure and reviews what the agent is allowed to touch.

Add a mod to a game and upload its files using the studio's OAuth2 token

Personal Library Sync

A launcher agent can keep a player's installed mods in sync with their mod.io library. It reads the /me subscriptions and mods, compares them with what is installed, and subscribes or unsubscribes as the player asks, so the library stays current without the player managing subscriptions on the website.

Read the current user's subscriptions and reconcile them with the installed mod set

Key Endpoints

27 endpoints — the mod.

METHOD

PATH

DESCRIPTION

GET

/games

List games

GET

/games/{game_id}/mods

List the mods for a game

GET

/games/{game_id}/mods/{mod_id}

Get a single mod

POST

/games/{game_id}/mods

Add a mod to a game

POST

/games/{game_id}/mods/{mod_id}/subscribe

Subscribe to a mod

GET

/me/subscriptions

List the current user's subscriptions

GET

/games

List games

GET

/games/{game_id}/mods

List the mods for a game

GET

/games/{game_id}/mods/{mod_id}

Get a single mod

POST

/games/{game_id}/mods

Add a mod to a game

POST

/games/{game_id}/mods/{mod_id}/subscribe

Subscribe to a mod

GET

/me/subscriptions

List the current user's subscriptions

Why Jentic?

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

Setup

Wiring the mod.io API by hand means handling two auth schemes at once: an api_key on the query for reads and an OAuth2 token for writes and per-user calls. Through Jentic you install once, import it from the API Directory, store both credentials once, and your agent calls the games, mods, and me operations.

Permission scoping

mod.io puts the game id in the URL path (/games/{game_id}/mods), so a rule can pin your agent to one game and to the read operations you choose, keeping mod deletion, file uploads, and comment posts out of scope until you add them. You decide which operations are in scope, and every call is logged.

Credential isolation

Your mod.io api_key and OAuth2 token are stored once, encrypted, by your own Jentic One instance and applied to the right calls at execution time. Neither enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list mods for a game' or 'subscribe to a mod', and Jentic returns the matching mod.io operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using mod.io API through Jentic.

What authentication does the mod.io API use?

The mod.io API uses two schemes, per its OpenAPI spec: read endpoints accept an api_key query parameter, and write and per-user endpoints use an OAuth2 access token. Through Jentic both are held by your own self-hosted instance and applied to the right calls at execution time, so neither lands in the agent's prompt or logs.

Can I list the mods for a game and read one with the mod.io API?

Yes. Call the mods list endpoint for a game id to get its mods, then call the single-mod endpoint with a mod id to read that mod, including its files and comments. Listing games and mods needs only the api_key, while adding or subscribing needs an OAuth2 token.

What are the rate limits for the mod.io API?

The OpenAPI spec for the mod.io API does not define rate limits. mod.io documents per-key request allowances, so check its current developer documentation before running high-volume browsing or uploads.

Is there a mod.io API MCP server?

You don't need an MCP server to give your agent the mod.io API. Jentic connects it directly from the API Directory: import it, store the api_key and OAuth2 token once, and your agent calls the games, mods, and me operations without another server's tool definitions loaded into its context.

Can I limit what my agent is allowed to do with the mod.io API?

Yes. mod.io puts the game id in the URL path (/games/{game_id}/mods), so a rule can pin your agent to one game and to the read operations you pick, leaving mod deletion and file uploads out of scope until you add them. Every request the agent makes against mod.io is logged.

How do I list mods for a game with the mod.io API through Jentic?

Search Jentic with an intent like 'list mods for a game', and it returns the mods list operation with its input schema so the agent submits the game id and reads back the mods. To run it on your own infrastructure, install Jentic One from its GitHub repo.

mod.io API

Name: mod.io API
Brand: mod.io
Availability: InStock

Agent-ready OpenAPI document · curated by JenticMediaContent DeliveryapiKey, oauth227 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Browse games and their mods on mod.io, read a mod's files and comments, and, when authorized, add mods, upload files, subscribe, rate, and read the current user's library.

Use for: List the mods available for a game, Get the details of a specific mod, Show the files uploaded for a mod, Subscribe the current user to a mod

Not supported: Covers games, mods, files, comments, subscriptions, and ratings on mod.io. Does not host game binaries, process payments, or manage the game titles themselves.

The mod.io API is the backend for user-generated game mods. It lists games and the mods published for each one, returns a single mod with its files and comments, and lets authorized callers add mods, upload files, post comments, subscribe, and rate. A set of /me endpoints returns the authenticated user's subscriptions and mods, and external auth endpoints exchange console tokens for a mod.io session. Read calls accept an api_key query parameter, while write and per-user calls use an OAuth2 access token.

Jentic One on Github View OpenAPI Document

Connect the mod.io API to your agent

Capabilities

Start building with mod.io API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

mod.io API