Skip to main content
Bloom is the brand layer: one place where a brand lives and evolves. Give it a website, social media, brand guides, briefs, logos, or other brand material. Bloom turns that context into a versioned Brand Skill—structured data and clear guidance that agents, applications, and people can use. As the brand changes, Bloom can publish a new version while keeping the brand itself in one place. A Brand Skill can equip any capable system creating on the brand’s behalf, whether it is making images, slides, websites, video, documents, or something else. Bloom includes image creation and transformation today; in other workflows, Bloom supplies the brand context and the connected system creates the output.

​
What Bloom provides

  • A brand in Bloom gives applications and agents one lasting identity to work with.
  • Brand Skills hold versioned brand context: a structured profile, Markdown guidance, and references to Brand Library assets.
  • The Bloom Skill is optional persistent guidance that teaches a compatible agent how and when to use Bloom. It contains no brand data and does not connect or authenticate Bloom.
  • Image tools generate, edit, resize, remove backgrounds from, and vectorize images using the current brand.
  • Brand Skill retrieval lets server-side applications use the same brand context in another system.
Read How Bloom works for the relationship between a brand and its current Skill.

​
Choose a starting point

  • Use the API quickstart when Bloom will run inside an application, backend, continuous-integration job, or automated workflow.
  • Use the MCP quickstart when a person or agent will operate Bloom through an MCP-compatible client.
Both interfaces work with the same underlying brands and images. The API publishes a stable REST contract through OpenAPI. MCP clients discover the tools and schemas currently available to the connected account. If an agent would benefit from persistent Bloom guidance across sessions, install the Bloom Skill, then use the same API or MCP path. The Skill is optional; it is not a third interface.

​
Give these docs to an agent

Paste this into an agent when you want it to assess or implement a Bloom workflow:

​
Common workflows

For exact REST fields, responses, and errors, use the API reference. For MCP, use the tool overview and the connected account’s live schemas.