How I replaced manual company research with an Apify Actor my Cursor agent can call Developer Manojaditya Nadar built an Apify Actor called site-intent that visits a fixed set of pages per company domain and returns one structured JSON row per company, then connected it to the Cursor coding agent through the Apify MCP server at https://mcp.apify.com so the agent can call it as a tool. The Actor, built with Crawlee and Playwright, opens each homepage, optionally reads sitemap.xml, follows internal links to pricing, blog and careers pages, and samples posts or an RSS feed to fill fields including has_blog, pricing_page_exists, blog_cadence_band, qualify_ready and pre_segment. Nadar reports running the Actor on four real domains from Cursor for about three cents, replacing manual research that he said could take a week on a list of 800 names. Manojaditya Nadar https://github.com/Manojaditya64 as part of Write for Apify https://apify.com/resources/write-for-apify - a program for developers sharing original articles about what they've built with Apify. I run outbound for B2B SaaS. My lead lists tell me a company exists: industry, headcount band, headquarters. They do not tell me whether the blog is still active, pricing is public, or the homepage sounds like a product company or an agency. For months I did that research by hand. I would open each site, click through to the blog and pricing pages, and try to remember what I saw. Five companies were manageable. Eight hundred were not. I built an Apify Actor called site-intent to automate that step. It visits a small, fixed set of pages per company and returns one structured summary row per domain. Then I connected it to Cursor through the Apify MCP server https://docs.apify.com/mcp so my AI agent can run it like any other tool during a conversation. This article explains what the Actor does, how I designed its inputs so agents do not send the wrong JSON, and what happened when I ran it on four real domains from Cursor for about three cents. Prerequisites You will need: - An Apify account https://console.apify.com and API token - Cursor https://cursor.com or another client that supports MCP Model Context Protocol - The Apify MCP server at https://mcp.apify.com - Basic familiarity with web scraping concepts I run site-intent as a private Actor in my Apify account. My Actor ID is 8YtTAk2XgTf3NL1yy , but that only works on my account. Nobody else can call it. The code is public on GitHub. To reproduce this Actor yourself, clone the site-intent repo https://github.com/Manojaditya64/site-intent , then deploy it to your own Apify account: npx apify-cli login npx apify-cli push Apify assigns your Actor ID on first push. Pin or call that ID from MCP, not my ID. The MCP workflow in this article is the same; only the Actor ID changes. The research step that slowed me down My pipeline starts with a spreadsheet of domains, often filtered from a larger firmographic list company size, industry, location, and similar fields . Before I pay for contact enrichment Prospeo, for example or email verification, I want answers to simpler questions: - Does this company have a blog? When did it last publish? - Is pricing visible on the site? - Does the copy mention AEO answer-engine optimization or similar topics I care about? - Does the site look like a SaaS product company or a services agency? I used to answer those by opening each domain in a browser. On a list of 800 names, that alone could eat a week. What I wanted instead was a machine-readable record per domain: a single JSON object my scripts or AI agent could read and filter on before I spent money on enrichment. What site-intent does On Apify, an Actor is a small cloud app that takes JSON input, does work often scraping , and writes results to a dataset a table of JSON rows . site-intent is built with Crawlee https://crawlee.dev and Playwright. For each domain you pass in, the Actor: 1. Opens the company homepage and the www variant if needed 2. Optionally reads sitemap.xml to find blog-related URLs 3. Follows internal links to locate pricing, blog, careers, and similar pages 4. Samples a few blog posts or an RSS feed to estimate how recently the site published 5. Combines everything into one output row for that company The important design choice is the last step. Many scrapers return one row per page. site-intent returns one row per company, with fields like has blog , pricing page exists , and blog cadence band already filled in. That is what makes it usable for lead qualification. In outbound, I do not need every paragraph from every page. A page dump forces me or an LLM to re-parse HTML for each domain. One row with qualify ready , pre segment , and blog cadence band lets me filter hundreds of names before I pay for contact enrichment or write a personalized email. What it does not do - It does not call an LLM inside the Actor that keeps runs cheap and repeatable - It does not find email addresses - It does not crawl the entire website - It does not fetch revenue or employee counts I use a separate enrichment step for that If I need an AI-written summary later, I run that in Python after the dataset comes back. The Actor only handles structured scraping. How it decides a company is worth a closer look The main output flag is qualify ready . It is computed with simple rules, not an AI model: js const qualify ready = home && home.word count || 0 80 && pricing page exists || blog index fetched || has blog ; In plain terms: the homepage must have more than 80 words, and the site must have a pricing page or a blog. If qualify ready is false, I skip paid enrichment for that domain. 1. AEO / AI-search signal detection js const AEO RE = /ai search|aeo\b|answer engine|chatgpt|claude|perplexity|gemini|ai discovery|ai visibility|appear in chatgpt/i; // Evaluated against homepage H1, meta description, content, and pricing page text: aeo copy present: AEO RE.test mergedForAeo 2. Pre-segment routing function inferPreSegment intent: Partial