
Choose the change
An exact profile request preserves the requested structured values, but Rainbrand may also update related Markdown. For example, a palette change can update the visual guidance that describes how those colors are used.
When changing the palette, send the complete color list in the desired order. For a matching HEX value, omitted names, groups, and usage keep their current values; send
null to remove one of those fields. A gradient change replaces the complete gradient list. Omit gradients to keep them, or send an empty list to remove them all.
Either type can include supporting evidence: a website, Instagram account, files, or images already in the Brand Library. Stage local files before submitting them. For a primary logo, first save the image to the Brand Library and reference its image ID. For a custom font, follow the font upload flow and reference the returned font asset ID and family.
For exact profile fields and evidence limits, read the Create a Brand Edit reference or the connected server’s live MCP schema.
Prepare a candidate
- API
- MCP
Read the active Brand Skill and use its Set Keep the returned edit
skillId as baseSkillId. Then call Create a Brand Edit:EDIT_REQUEST_KEY to a unique value for this operation. Reuse it with the same body when retrying the request; use a new key for a different operation.For an exact profile edit, replace change with a profile request, such as:id. While its status is preparing, call Get a Brand Edit with wait=true. If it is still preparing, follow the response’s retry guidance and repeat the read with the same ID.Handle a request for input
Atinput_required, read the clarification or choice and answer in the format it requests. Answering continues preparation; it does not apply the edit.
API clients submit a typed response to Continue a Brand Edit, using the current interaction ID and an Idempotency-Key. If the result is preparing, read the edit again with wait=true. Use the returned option IDs for a selection, or provide an answer in the accepted format. A client can also decline the interaction.
MCP clients that support native input can handle the exchange within the request. Other clients use continue_brand_edit with the returned edit and interaction IDs. If preparation continues, follow with get_brand_edit and wait: true.
Inspect the candidate
When status reachesawaiting_approval, inspect the proposed profile, guidance, and asset changes. For complete Markdown, read a changed file with the API or get_brand_edit_file in MCP. Follow the returned cursor to read the remaining content.
Refine a candidate
To revise a candidate awaiting approval, create another edit withreplacesEditId in the API or replaces_edit_id in MCP. Describe the refinement in the new request.
The existing candidate stays available while its replacement is being prepared or waiting for input. Only when the replacement reaches awaiting_approval does Rainbrand discard the old candidate and make the new one available to apply. A failed refinement does not lose the previous candidate.
Apply or discard
Call Apply a Brand Edit orapply_brand_edit to make the candidate the active Brand Skill. Call Discard a Brand Edit or discard_brand_edit to end the edit without changing the active brand.
If the active brand changes after the edit was based on it, the candidate cannot overwrite that newer version. Read the current Brand Skill and prepare a new edit from it.
After applying an edit, retrieve the active Brand Skill to use the updated context outside Rainbrand. If preparation fails, read the returned error before trying again.
The Brand Edit reference and live MCP tools/list define the exact fields, statuses, and errors.