Set up PixelLab
Configure the production provider, choose a generator, and use its account workflows.
PixelLab is PixelKiln's default provider and the production choice for current projects. Its generation and account-management paths have been exercised against a live account.
Visit PixelLab or open the official API reference.
Add the credential
Create .env.local beside pixelkiln.manifest.json:
PIXELLAB_API_KEY=...
Keep this file out of Git. PixelKiln also reads the variable from the current process environment.
Select PixelLab
The provider field is optional because pixellab is the default. Declaring it
makes the choice clear:
{
"name": "my-game",
"provider": "pixellab",
"styles": {
"props": {
"generator": "map",
"outDir": "assets/generated/props",
"promptSuffix": ", isolated pixel-art game asset"
}
},
"assets": {
"anvil": {
"prompt": "a compact blacksmith anvil",
"width": 64,
"height": 64
}
}
}
Run the free checks before a paid request:
pixelkiln doctor --dry-run
pixelkiln plan
pixelkiln gen --budget 1
Copy the exact estimate from plan into --budget. PixelLab budgets use
subscription generations.
Choose a generator
| Generator | Start here when | Measured cost |
|---|---|---|
map | You need one prop, icon, building, or landmark at arbitrary dimensions | 1 generation |
pixflux | You need a closed palette or a full-bleed background | 1 generation |
1dir | You need references or several candidates for human review | 20 to 40 generations |
tiles | You need ground variations or a connected structural set | 20 to 40 generations |
map accepts these values:
view:low top-down,high top-down, orsideoutline:single color outline,selective outline, orlinelessshading:flat shading,basic shading,medium shading, ordetailed shadingdetail:low detail,medium detail, orhigh detail
PixelLab describes map objects as transparent, but the 256px map objects in our
environment benchmark were opaque. Check the alpha
channel before building a production batch. For a scenic background, use
pixflux with noBackground: false.
Read Generator selection for the full constraints and measured economics.
Account workflows
The PixelLab adapter supports balance, adopt, salvage, tag, and the
separate confirmed purge flow. These are useful when several projects share
one provider account or when existing local art needs its original provenance.
Read Recovery and account safety before changing remote
objects.
PixelLab's official MCP server gives agents direct access to PixelLab generation tools. It complements PixelKiln: the MCP handles creation, while PixelKiln owns project state, budgets, review, recovery, and packaging.
What is outside this adapter
PixelLab offers more than PixelKiln currently exposes. Character generation, multi-direction rotation, and animation are not part of this adapter. Use the manifest reference for the fields PixelKiln supports today.