Research

Competitor Intelligence API

Monitor competitor websites for positioning, products, pricing, screenshots, style changes and content updates.

Crawl AI Query Products Screenshots

Monitor competitors Read docs

01 Crawl and sitemap discovery

02 AI query templates

03 Screenshot evidence

04 Product and pricing extraction

How it works

From input to useful output in three steps

POST /v1/workflows/competitor-monitoring

Discover

Find relevant pages

Use sitemap, crawl and search to locate pricing, product, case-study and feature pages.

GET /v1/web/scrape/sitemap

Extract

Ask for competitor signals

Query specific datapoints such as pricing language, integrations or target customers.

POST /v1/brand/ai/query

Review

Attach visual evidence

Capture screenshots and product records so research can be reviewed by humans.

GET /v1/web/screenshot

Example workflow

Competitor site to research brief

Team asks

What changed in competitor positioning, pricing and product pages?

MediaHarvester monitors

Sitemaps, selected pages, screenshots, product records and extracted datapoints.

Team receives

A source-backed research brief with links and visual evidence.

{
  "domains": ["competitor.com"],
  "fields": ["pricing", "positioning", "products"]
}

Built for

Teams that can use this immediately

Product marketing

Challenge: Competitor messaging changes quietly.

Solution: Monitor selected pages and extract signals.

Impact: Teams react with evidence.

Agencies

Challenge: Manual audits take hours.

Solution: Generate a structured brief from public pages.

Impact: Reports start with real data.

Founders

Challenge: Market research is scattered.

Solution: Combine crawl, screenshots and AI query.

Impact: Faster competitive understanding.

Implementation FAQ

Questions teams ask before building Competitor Intelligence API

12 answers

What does Competitor Intelligence API help me build?

It turns Competitor intelligence API for SaaS, agencies and product teams. into a repeatable workflow. The first practical outcome is crawl and sitemap discovery.

Which API should I call first?

Start with POST /v1/workflows/competitor-monitoring. 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: What changed in competitor positioning, pricing and product pages? 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 product marketing, agencies, founders, 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/competitor-monitoring 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.