The problem worth solving
Apply customer-approved colors and typography to a first-run workspace while preserving accessibility.
The first minutes inside a product often feel generic because a new customer is asked to recreate information already visible on their own website.
A workflow that teams can actually ship
Collect a company domain with permission, offer a suggested logo and theme, render a preview immediately, then let the user confirm or change it before saving.
For this pattern the practical entrypoint is `POST /v1/workflows/brand-kit`, combined with whichever workflow endpoint or presentation layer the product requires.
Workflow map
Scenario in practice
A B2B SaaS product asks for a customer domain during signup and needs a convincing first workspace in seconds.
Start with one observable workflow, keep source URLs available during review and expand only after the result is reliably useful.
Try the capability
POST /v1/workflows/brand-kit Local API key:mh-localhost-dev-key
POST /v1/workflows/brand-kitImplementation notes
Personalization should reduce effort rather than create an opaque profile. Show the suggestion, explain its origin and make skipping effortless.
When the result affects a customer-facing experience, add an approval or override path rather than treating extraction output as immutable truth.
Signals to monitor
Evaluate setup completion time, activation, suggestion acceptance, overrides and whether branded onboarding improves retention without increasing support work.
Metrics turn a promising prototype into a maintainable product capability and make regressions easier to catch.
Try it with MediaHarvester
Open the local playground, choose the feature matching `POST /v1/workflows/brand-kit` and test with a public or authorized target.
The local project includes API, documentation, SDK, CLI, MCP and no-code surfaces so the same idea can move from exploration into implementation.
FAQ
Questions teams ask before implementing this workflow
What does this personalization workflow return?
It uses POST /v1/workflows/brand-kit and related MediaHarvester surfaces to return structured context together with metadata appropriate to the workflow.
Can I test this locally?
Yes. Run the local service at http://127.0.0.1:8013 and send X-API-Key: mh-localhost-dev-key to protected API routes.
Does it work with private or blocked pages?
The platform is designed for publicly accessible or authorized sources. Verification, login, permission and robots restrictions are reported rather than bypassed.
Can this be automated?
The same API surfaces are available through CLI, Python and TypeScript SDKs, MCP tools and starter no-code integration templates.
How do I keep the result current?
Use cache freshness controls such as maxAgeMs where exposed, and schedule refreshes in a production worker only as frequently as the business case needs.