What authentication does the Modrinth API use?

Modrinth uses HTTP token authentication under the tokenAuth bearer scheme. Generate a personal access token from your Modrinth profile and pass it as a bearer token. Through Jentic, the token is stored encrypted in your Jentic One instance and the agent receives only a scoped session at execution time.

Can I look up a Modrinth version by file hash?

Yes. GET /version_file/{hash} resolves a SHA-1 or SHA-512 hash to the version that owns the file. This is the standard way for mod launchers to detect installed mods and check for available updates.

What are the rate limits for the Modrinth API?

Modrinth applies a 300 requests per minute rate limit on its public API. Authenticated requests share that pool; if you exceed it, the API returns 429 with a Retry-After header. Cache aggressively when paginating large result sets.

How do I publish a new mod version with the Modrinth API through Jentic?

Run pip install jentic, then search for 'create a new mod version'. Jentic returns the POST /version operation schema. Execute it with the project_id, version_number, game_versions, loader, and primary file payload, then verify with GET /version/{id}.

Does the Modrinth API support project search with facets?

Yes. GET /search accepts the query parameter for free text plus facets for project_type, categories, versions, loaders, and license. This is the same engine that powers the modrinth.com search experience.

Can I limit what my agent is allowed to do with the Modrinth API?

Yes. Because you self-host Jentic One, your own rules decide which Modrinth operations and credentials the agent may use. You can pin it to read-only lookups like GET /project/{idOrSlug} and GET /version_file/{hash}, since Modrinth takes the project id, slug, or file hash in the URL path, so a rule can scope the agent to reading a single project. Write operations such as POST /project or POST /version are not available to the agent unless you explicitly add them.