Why this subject deserves an implementation guide
The starting question for this article came from a public Context.dev post titled "Martialytics Welcomes Trial Signups with Context.dev". Rather than reproduce that article, this guide asks what the same product problem looks like inside MediaHarvester and what can be verified in the running application.
The first minutes inside a product often feel generic because a new customer is asked to recreate information already visible on their own website.
The MediaHarvester approach
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.
The primary surface for this workflow is `POST /v1/workflows/brand-kit`. It can be tried from the API playground and integrated through the local API key, SDK, CLI or MCP layer.
Workflow map
A realistic application scenario
A B2B SaaS product asks for a customer domain during signup and needs a convincing first workspace in seconds.
The workflow begins with a narrowly scoped public or authorized source, records the endpoint output and makes the result reviewable before it becomes visible to users or informs an automated decision.
Try the capability
POST /v1/workflows/brand-kit Local API key:mh-localhost-dev-key
POST /v1/workflows/brand-kitImplementation choices that matter
Personalization should reduce effort rather than create an opaque profile. Show the suggestion, explain its origin and make skipping effortless.
This matters because a production feature is judged less by a perfect demo result than by how it behaves when an asset is missing, a source changes, a response is cached or a request is not allowed.
How to measure whether it works
Evaluate setup completion time, activation, suggestion acceptance, overrides and whether branded onboarding improves retention without increasing support work.
The app should retain enough source and request metadata to debug poor results while applying appropriate retention and access policies for customer data.
A responsible next step
Run the included endpoint against a website you control or are authorized to process, inspect the response in Visual and JSON modes, then decide which fields deserve automation and which deserve human approval.
MediaHarvester deliberately treats blocked, verification-required, login-required, robots-disallowed and permission-required outcomes as information, not obstacles to be bypassed.
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.