API overview
Everything the Studio does to a pack, your own code can do too: create a pack,
generate blocks, models, items and icons into it, and download the finished
.zip.
On a paid plan
API keys are available on any paid plan. 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 the API and nothing else. Every path in this reference is relative to it.
Get a key#
- 1
Open the Developers page
studio.resourcepack.ai/developers, then find the API keys card. The MCP keys card under it is for connecting an AI agent (see MCP); the two kinds are separate, and each only works on its own surface. Neither is Bring Your Own Key, on your account page, which is a key you bring so model generations bill to your OpenAI account. These are keys we give you so your code can call us.
- 2
Name it and create it
The name is only for telling keys apart later, so use the thing it's for —
ci,my bot,laptop. - 3
Copy it immediately
The key is shown once and never again. We store a hash of it, not the key, so there is no way for us to show it to you a second time — if you lose it, revoke it and make another.
API keys look like rpai_ followed by 43 random characters (MCP keys like
rpai_mcp_ followed by the same). The prefix is there so
a key that leaks into a commit or a log is easy to search for.
Authenticate#
Send the key as a bearer token:
curl https://api.resourcepack.ai/v1/packs \
-H "Authorization: Bearer rpai_YOUR_KEY"There's no other way to send it. A key in a query string ends up in access logs,
browser history and Referer headers, so it isn't accepted.
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.
Rate limits#
Two budgets per key, measured over a rolling minute: 120 reads and 30
writes, where a write is creating a pack, generating anything, or exporting.
Over budget answers 429 with a Retry-After header.
Credits are still the throttle that matters — a generation you can't afford is refused with a 402 however slowly you ask. See Rate limits for what counts against which.
What's not here#
The API covers creating packs, generating into them, and getting assets back out. It deliberately doesn't cover editing pixels or geometry, iterating on an existing asset, deleting things, pack settings, collaborators or syncing to a server — those live in the Studio. If you need one of them programmatically, say so in Discord.