mudpie

Company profile · 3 min read

Bloom: the brand layer for agents

Bloom turns brand sources into a canonical system that agents and products can call through a web app, API or MCP to create on-brand assets.

Published · Updated

What it does

Bloom is a brand layer that turns scattered brand evidence—websites, decks, Figma files, social, images and guides—into a canonical system agents and products can call. It can generate on-brand images, video, copy and campaigns through the web app, API or MCP. The YC profile frames the product as brand infrastructure; the current homepage shows the ingest, systemise and create loop.

The fit is a marketing team, agency or product builder that wants agents to produce on-brand work without repeatedly re-explaining voice, aesthetics and references. Bloom is also relevant to software teams embedding brand context into their own products.

Why I’d look closer

The product has a clear operational model. A brand is created from ordered sources, analyzed into a ready state, then used by an API or MCP generation call. The docs expose asynchronous brand readiness, image generation, OAuth/API authentication and a source-based onboarding flow. That is better than treating brand as a static PDF.

Pricing is public. The pricing page lists a Scale plan at $100/month with 500 credits/month, shared workspaces, pooled credits and unlimited team seats. The YC launch reports more than 175,000 on-brand assets generated; that is company-reported traction, not independent creative-quality proof.

The founder context is relevant. The YC profile describes Ray Fitzgerald as the founder of Lucid and a former Inscribe builder who is focused on product and organic growth.

What I’d ask

How are conflicting brand sources resolved, how are generated assets versioned, and what happens when a brand changes its logo, palette or voice? I’d onboard one brand from real source material, test API/MCP outputs against a human review set, and inspect data retention and image rights.

My editorial take

Bloom is a strong fit for teams making lots of agent-generated creative where consistency is the bottleneck. The canonical-brand thesis is practical. The product earns its place if it keeps agents on-brand without turning the source-ingestion process into another manual content project.

Quick facts

Field Sourced detail
Buyer fit Marketing teams, agencies, founders and products embedding brand context
Public pricing Scale $100/month with 500 credits/month; team/volume options shown
Interfaces Web app, REST API and MCP
Traction signal Company reports 175,000+ assets generated

Sources checked

Checked 2026-09-19.

Source Used for
YC company profile Product, founder and traction claim
Bloom homepage Current ingest/systemise/create workflow
Bloom pricing Public plan and credit structure
Bloom API docs Brand readiness and generation workflow

Cohort context

Bloom is listed in Spring 2026. In our 2026-09-18 directory snapshot, 112 of 193 listed companies in that cohort have YC’s primary industry label B2B (58.0%). This is a current-directory comparison, not an original intake count or a performance ranking. Nine-cohort dataset.

Public website snapshot

Observed 2026-09-19T16:16:08.470Z in raw homepage HTML. This records visible metadata and advertised links, not agent execution or product quality.

Signal Homepage observation
Product description metadata Observed
Canonical link Observed
H1 or H2 heading Observed
Typed structured data Observed
Docs/developer link Observed
Pricing link Observed
llms.txt link Observed
Markdown alternate Not observed in this response

Public observations · Collection method. Missing links here do not establish that a capability or file is absent elsewhere.

About the author

I cofound Lazyweb and publish Mudpie. This is an owner-written publication, not an independent testing organization. Research notes distinguish observations, sourced reporting and editorial judgment.

First1000 ↗ · X ↗