resourcepack.ai
DOCS

API overview

The ResourcePack AI API is an HTTP API for doing from your own code what you do in Studio: create a pack, generate assets into it, and get the finished pack out. Use it for scripts, bots and tools of your own. To let an AI agent such as Claude do the work instead, use the MCP server.

What it covers:

  • Packs: create, rename, duplicate, delete, set the icon and style guide, invite collaborators, organise assets into folders.
  • Generating: Blocks, 3D Models, Items, GUIs, HUDs, Dialogs, Icons, Rank Tags, armour, Sounds, Shaders, VFX, Emotes, player Skins and Custom GUI pages. Then change any of them with a sentence (Edit with AI), regenerate them, or restore an earlier version.
  • Your own files: upload textures, models, sounds and more, or import a whole resource pack .zip.
  • Getting it out: export the Java .zip, a Bedrock .mcpack or plugin content, push the pack straight into a player's game, publish it to the servers bound to it, or put an asset on the public gallery.

On every plan

API keys are available on every plan, the free one included. Calls spend the same AI Credits the app does. There's no separate API pricing and no per-request charge.

Base URL#

https://api.resourcepack.ai/v1

That host serves only the API. Every path in this reference is relative to it. The full spec is at /openapi.json.

Every call needs a key, so start there.

Get a key#

  1. 1

    Open the Developers page

    Go to studio.resourcepack.ai/developers and find the API keys card. The MCP keys card below it is for connecting an AI agent (see MCP server). Each kind of key only works on its own surface.

  2. 2

    Name it and create it

    The name is only for telling keys apart, so use what it's for: ci, my bot, laptop.

  3. 3

    Copy it immediately

    The key is shown once. We store only a hash of it, so we can't show it again. If you lose it, revoke it and make another.

API keys are rpai_ followed by 43 random characters (MCP keys start rpai_mcp_). The prefix makes a key that leaks into a commit or log easy to search for.

Don't confuse these with Bring Your Own Key on your account page, which is a key you give us. These are keys we give your code.

Authenticate#

Send the key as a bearer token:

curl https://api.resourcepack.ai/v1/packs \
  -H "Authorization: Bearer rpai_YOUR_KEY"

That's the only accepted way. Keys in query strings end up in logs and browser history, so they're refused.

A key is your whole account

It can read, generate into and export every pack you own or collaborate on, and it spends your credits. Keep it server-side: never in a Minecraft plugin, a browser bundle, or anything you hand to a player. Revoke it from the same card the moment you think it's out, and check its history.

Rate limits#

Each key gets 120 reads and 30 writes per rolling minute. A read is a GET; a write is any other request (creating a pack, generating, uploading, deleting), plus export. Over budget answers 429 with a Retry-After header. Credits still apply: a generation you can't afford is refused with 402. See Rate limits.

What's not here#

The API doesn't do hand edits: painting pixels, moving a 3D Model's cubes, or laying out a Dialog piece by piece. Those happen in Studio's editors. It also doesn't make Mobs yet. If you need one of these from code, tell us in Discord.