Skip to main content
Bloom is the brand layer: the canonical home of a Brand’s identity, made callable by the systems that create on its behalf. Give Bloom a website, Instagram account, files, or a combination of sources. The Brand Agent turns that evidence into an active Brand Skill containing structured identity and detailed guidance. Bloom uses the Skill automatically when it creates for that Brand.

​
What Bloom provides

  • Brands give applications and agents one stable resource for the identity they are using.
  • Brand Skills hold the complete, versioned Brand context: a structured profile, Markdown guidance, and references to Brand Library assets.
  • Image tools generate, edit, resize, remove backgrounds from, and vectorize images using the active Brand.
  • Brand Skill retrieval lets enabled server-side integrations use the same Brand context in another system.
Bloom currently creates and transforms images. Another system can use a retrieved Brand Skill to guide a deck, website, or other branded artifact, but that system—not Bloom—creates the output. Read How Bloom works for the relationship between a Brand and its active 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.

​
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.