# Agency Service Page Lead Signal Extractor (`seeb/agency-service-page-lead-signal-extractor`) Actor

Extract agency service-page signals for partner research, including service offer, target client, platform expertise, proof, and lead angle.

- **URL**: https://apify.com/seeb/agency-service-page-lead-signal-extractor.md
- **Developed by:** [Techionik](https://apify.com/seeb) (community)
- **Categories:** Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$25.00 / 1,000 agency lead signals

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Agency Service Page Lead Signal Extractor

Extract agency service-page signals for partner research, including service offer, target client, platform expertise, proof, and lead angle.

Agency Service Page Lead Signal Extractor is built for one focused job: turning public source pages or pasted research snippets into usable agency lead signal records. It does not try to be a generic webpage scraper. The parser, fields, examples, and dataset schema are shaped around this actor's specific business question.

Use it when you already have public pages, listings, announcements, reviews, directories, or copied snippets and want a repeatable way to extract the information that matters without manually filling a spreadsheet.

### Who Uses It

SaaS partner teams, lead researchers, agency marketplaces, channel managers, and vendors looking for implementation partners.

### What It Finds

The actor looks for signals connected to extract agency service-page signals for partner research, including service offer, target client, platform expertise, proof, and lead angle. It keeps the output focused on fields a buyer can review, filter, enrich, or send into a CRM, spreadsheet, product backlog, procurement workflow, or research database.

The extraction method is specific to this actor:

Service-page extraction with offer/target-client parsing, platform dictionary matching, proof detection, and partner-fit scoring.

### How It Works

1. The actor accepts public URLs or pasted snippets in `agencyPageSources`.
2. Public URLs are fetched when possible and converted into visible text.
3. Pasted snippets are processed directly, which is useful for pages that block automated fetching or require manual browsing.
4. Actor-specific parsing logic extracts only the fields listed below.
5. Empty or low-information inputs are skipped safely, with clean logs instead of noisy failed rows.

### Input

Use `agencyPageSources` for the sources you want to process. Each item can be a public URL or a focused text snippet.

```json
{
    "agencyPageSources": [
        "Northstar Studio offers Shopify Plus migrations and Klaviyo retention flows for DTC beauty brands with 42 case studies.",
        "RevOpsLab provides HubSpot onboarding, Salesforce cleanup, and lifecycle campaign setup for B2B SaaS startups.",
        "WebflowWorks builds Webflow sites and analytics dashboards for funded fintech companies with portfolio examples."
    ],
    "maxResults": 3
}
```

### Output Fields

- `agencyName` - Agency, studio, consultancy, or service provider name.
- `servicePageUrl` - Agency service page URL.
- `serviceOffer` - Service being offered.
- `targetClient` - Client segment the agency targets.
- `platformExpertise` - Platforms, tools, or ecosystems the agency claims expertise in.
- `verticalNiche` - Industry or niche the agency serves.
- `proofSignal` - Proof such as case studies, migrations, portfolio, or examples.
- `partnerFitScore` - Simple fit score for partner or channel research.
- `leadAngle` - Suggested outreach angle for a service provider.
- `nextStep` - Recommended next review step.

### Example Output

```json
{
    "agencyName": "Northstar Studio",
    "servicePageUrl": "https://example.com/service",
    "serviceOffer": "Shopify Plus migrations and Klaviyo retention flows",
    "targetClient": "DTC beauty brands",
    "platformExpertise": "Shopify Plus, Klaviyo",
    "verticalNiche": "DTC ecommerce",
    "proofSignal": "42 case studies",
    "partnerFitScore": "high",
    "leadAngle": "Offer HubSpot implementation help",
    "nextStep": "Review service page and contact for partner qualification"
}
```

### Best Use Cases

- Build a focused spreadsheet from repeated source pages.
- Review public signals before sales, partnership, product, procurement, or market research work.
- Monitor a category over time using the same output fields.
- Turn copied notes from newsletters, communities, directories, review pages, or search results into a structured dataset.

### Tips For Better Results

- Use source pages that visibly contain the signal you want this actor to extract.
- For hard-to-fetch sites, paste the relevant public text snippet directly into the input.
- Keep each input item focused on one page, listing, announcement, review, or profile.
- Review extracted rows before making high-stakes business, legal, procurement, or security decisions.

### Limitations

- The actor does not bypass logins, paywalls, private systems, CAPTCHA, or anti-bot walls.
- The actor extracts from visible text and may miss information hidden behind scripts or user interactions.
- Some fields may be empty when the source does not contain that information.
- Output quality depends on source quality, so focused source text produces the strongest rows.

# Actor input Schema

## `agencyPageSources` (type: `array`):

Add public URLs or paste focused text snippets. Use one source per row. The actor extracts only signals that match its specific purpose.

## `maxResults` (type: `integer`):

Maximum number of useful dataset rows to save.

## Actor input object example

```json
{
  "agencyPageSources": [
    "Northstar Studio offers Shopify Plus migrations and Klaviyo retention flows for DTC beauty brands with 42 case studies.",
    "RevOpsLab provides HubSpot onboarding, Salesforce cleanup, and lifecycle campaign setup for B2B SaaS startups.",
    "WebflowWorks builds Webflow sites and analytics dashboards for funded fintech companies with portfolio examples."
  ],
  "maxResults": 25
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

## `summary` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("seeb/agency-service-page-lead-signal-extractor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("seeb/agency-service-page-lead-signal-extractor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call seeb/agency-service-page-lead-signal-extractor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,seeb/agency-service-page-lead-signal-extractor"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/2jTZfcbkvbfcdrEk7/builds/ndfdYfM9iYujls7w5/openapi.json