Agencies
Agency Client Reporting
Automate branded audits, website research, screenshots, styleguides and client presentation assets.
Brand kit
Screenshot
Styleguide
Slides
How it works
From input to useful output in three steps
POST /v1/workflows/client-presentation
Build the client context
Retrieve brand data, styleguide tokens and a screenshot from the client domain.
POST /v1/workflows/brand-kit
Collect page evidence
Crawl selected pages or ask AI query for services, positioning and proof points.
POST /v1/brand/ai/query
Fill the deliverable
Use workflow output to populate client reports, slides or dashboard previews.
POST /v1/workflows/client-presentation
Example workflow
Client domain to branded report
A client URL and a repeatable audit or proposal template.
Brand profile, logos, styleguide, screenshot, sitemap and selected page content.
A branded report or presentation with fewer manual setup steps.
{
"domain": "client.com",
"title": "Q3 Website Audit"
}Built for
Teams that can use this immediately
Marketing agencies
Challenge: Each audit starts from scratch.
Solution: Fetch brand and website context first.
Impact: Reports get to draft faster.
Consultants
Challenge: Visual polish takes time.
Solution: Use client logos, colors and screenshots.
Impact: Deliverables feel tailored.
Web design teams
Challenge: Discovery is scattered across tools.
Solution: Collect assets, pages and styleguide in one flow.
Impact: Kickoff is more organized.
01
Start every report with context
Pull logo, description, colors, styleguide and screenshot data before writing recommendations.
02
Make reports feel custom
Use extracted brand assets to theme proposals, decks, audits and client portals.
03
Automate repeatable deliverables
Pair workflow APIs with Make, Zapier or n8n to create client assets from a single domain field.
Implementation FAQ
Questions teams ask before building Agency Client Reporting
What does Agency Client Reporting help me build?
It turns Automated client reports for agencies and consultants. into a repeatable workflow. The first practical outcome is brand kit workflow.
Which API should I call first?
Start with POST /v1/workflows/client-presentation. The workflow section shows the supporting endpoints to add when you need more context, evidence or visual assets.
What input do I need from my user?
The smallest useful input is shown in the example workflow: A client URL and a repeatable audit or proposal template. Ask only for the domain, URL, email, ticker or descriptor that the selected endpoint actually needs.
What should I store from the response?
Store the normalized result together with source URLs, confidence or access state, and the time it was fetched. This keeps later refreshes and human review explainable.
Can I use this from a backend, CLI or AI agent?
Yes. The REST endpoint, TypeScript and Python SDKs, CLI and MCP tools use the same local API contract. No-code templates are available for business workflows.
How do I keep the result current?
Use maxAgeMs where the endpoint supports it, or schedule the relevant crawl or workflow. Refresh facts that can change and cache stable assets such as logos more aggressively.
What happens when the website blocks access?
The API reports blocked, verification_required, login_required, robots_disallowed or permission_required instead of treating an empty page as a successful result.
How should I handle missing fields?
Keep the UI usable with optional fields, sensible placeholders and manual overrides. A missing logo, address or classification should not prevent the rest of the workflow from completing.
Who is this workflow designed for?
The examples focus on marketing agencies, consultants, web design teams, but the API response is general enough to use in custom applications.
Can I review the result before publishing it?
Yes. Show extracted values, source URLs and generated visual previews in an approval step before changing customer-facing content or records.
Is batch processing supported?
Use the batch, crawl or workflow endpoint shown for the capability when available. For smaller integrations, process a controlled list and record individual failures rather than failing the whole job.
How do I try the complete example locally?
Open the linked playground from this page or call POST /v1/workflows/client-presentation at http://127.0.0.1:8013 with X-API-Key: mh-localhost-dev-key. The example payload on this page is ready to adapt.
Related use cases
Explore adjacent workflows
Power LLMs with Web Context
Give AI agents real-time website context with clean markdown, crawl results, screenshots, brand data and structured extraction.
Reduce Onboarding Friction
Personalize onboarding automatically with company logos, colors, fonts, styleguides, descriptions and industry classification.
Enrich Company Profiles
Build richer CRM, directory and marketplace profiles with logos, descriptions, socials, colors, addresses and industry data.
Automated Brand Kits
Generate brand kits on demand with logos, colors, typography, component tokens, CSS variables and Tailwind theme exports.
Stock Ticker Enrichment
Resolve public-company tickers and ISINs into company websites, logos, brand profiles and stock metadata.
Logo Link API
Serve company logos through a spreadsheet-friendly public Logo Link endpoint with monogram fallback.