You authenticate with an API key. Create one in the Melius app under Team
settings → Integrations. See Authentication.
Base URL
x-team-id header — it defaults to the team your key belongs to:
How generations work
A generation in Melius is a canvas node — there’s no separate “generate” path, so the API stays consistent with the app. You create a node, start a run, and poll the run until it finishes:status is finished (or failed).
Post-process a node
Node tools modify a finished asset in place. The first public node tool isremove-background for image nodes and file nodes that contain images. It creates and activates a transparent PNG version on the same node and costs 12 credits.
{ "id": "<nodeRunId>" }. Poll GET /api/v1/node-runs/<nodeRunId> until the run finishes, just like a generation run.
Get the result
When a run finishes, fetch the URL of the generated file with one more call:Rate limits and credits
- Credits. Generations consume credits from the team you act on, exactly like the app. The credit cost of each model is shown in
GET /generation/models. - Rate limits. There is no monthly request quota on any plan. Requests can still return
429with aRetry-Afterheader — wait the number of seconds it gives you, then retry.
Next steps
Quickstart
Create a key and run your first generation end to end.
Authentication
API keys, the
x-team-id header, and how keys are scoped.