What authentication does the CurseForge API use?

The API uses an API key sent in the x-api-key request header. Through Jentic the key is held in the encrypted vault and injected at execution time, so the raw key never enters the agent's prompt.

Can I download mod files with the CurseForge API?

Yes. Call GET /v1/mods/{modId}/files/{fileId}/download-url to obtain the download URL for the file, then issue a standard HTTP GET to that URL to fetch the jar.

What are the rate limits for the CurseForge API?

CurseForge does not document a request rate limit, and neither its own document nor the spec behind this page declares one, so treat throttling as undefined rather than absent. The limits its documentation does publish are on paging: the maximum page size is 50 results per page, capped at 10,000 total results, with index plus pageSize required to stay within 10,000.

Is there a CurseForge MCP server?

You don't need an MCP server to give your agent CurseForge. Jentic connects it directly from the API Directory: import CurseForge, store your x-api-key once, and your agent can search mods, list a mod's files, and resolve download URLs, with no extra tool definitions loaded into its context.

How do I identify mods already installed in a folder?

Compute the CurseForge fingerprint for each jar file, then POST /v1/fingerprints with the fingerprint list. The response returns exactMatches and partialMatches, each carrying the matched mod id and the file record, and POST /v1/fingerprints/fuzzy is available for near matches by folder.

How do I list supported Minecraft versions through Jentic?

Install Jentic One on its own machine, run `jentic register` on the machine your agent runs on, then import the CurseForge API from the API Directory and store your x-api-key once. Your agent searches by intent for 'list minecraft versions', loads the schema for GET /v1/minecraft/version, and executes it. The response is the version catalogue you can pass as the gameVersion query filter on GET /v1/mods/{modId}/files.

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

Yes. Because you run Jentic One yourself, your own rules decide which CurseForge operations and credentials the agent may use. CurseForge puts the mod id in the URL path (/v1/mods/{modId}/files/...), so you can pin the agent to a single mod and let it read only that mod's details and files. You also choose the operations it may call, so a corpus-wide lookup like POST /v1/mods/featured stays out of reach unless you explicitly add it. Every one of the 22 operations in this spec reads data; none of them writes to CurseForge.