# Hoo.be Creator Scraper — Profiles, Links & Socials (`huykenny/hoobe-creator-scraper`) Actor

Extract public Hoo.be creator profiles, social links, outbound links, embeds and storefront data as clean structured JSON. Built for creator discovery, influencer research and creator economy apps.

- **URL**: https://apify.com/huykenny/hoobe-creator-scraper.md
- **Developed by:** [Kenny Ha](https://apify.com/huykenny) (community)
- **Categories:** Social media, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Hoo.be Creator Scraper — Profiles, Links & Socials

Extract **Hoo.be creator profiles, social links, outbound links, embeds and
storefront data** into clean structured JSON. Built for creator discovery,
influencer research and creator economy apps.

**No browser automation. One HTTP request per profile. No login, no proxy
needed.** Measured on 25 real profiles: 100% success, ~0.44 s and ~83 kB per
profile, zero retries.

### What does this Actor do?

Point it at [hoo.be](https://hoo.be) creator handles and it returns one clean
record per creator: identity, bio, avatar, verification, every outbound link
with a classified type, social accounts resolved into `{ platform, url,
username }`, structured embeds, and any publicly priced items. Add
`mode: MONITOR` and it reports what changed since the previous run.

It works as an unofficial data API over public Hoo.be profiles — usable from
the Apify API, JavaScript/Python clients, schedules, webhooks, Make, Zapier
and n8n.

### What this Actor extracts

- **Creator** — `creatorId`, `username`, `displayName`, `bio`, `profileUrl`,
  `avatarUrl`, `backgroundImageUrl`, `verified`, `customDomain`
- **Links** — `title`, `url`, `type`, `platform`, `position`, `thumbnailUrl`,
  `destinationDomain`, `isAdultContent`
- **Social profiles** — `platform`, `url`, `username` (structured, not a URL dump)
- **Products** — `price`, `productUrl`, `imageUrl`, `promoCode` *(rare — see
  Limitations)*
- **Embeds** — `variant`, `platform`, `contentId`, `embedUrl`
- **Tip jars** — title and offered amounts
- **Counts** — `linkCount`, `socialProfileCount`, `productCount`, `embedCount`

#### Link types

`SOCIAL` · `PRODUCT` · `SHOP` · `AFFILIATE` · `MUSIC` · `VIDEO` ·
`NEWSLETTER` · `COMMUNITY` · `DONATION` · `WEBSITE` · `OTHER`

Classification is deterministic and unit-tested. Hoo.be labels each link's
platform itself, so platform detection is **read from the source**, not guessed
from the domain — domain matching is only a fallback when Hoo.be says `other`.

#### Social platforms detected

Instagram, TikTok, YouTube, X/Twitter, Twitch, Facebook, Snapchat, Threads,
LinkedIn, Reddit, Pinterest, Discord, Telegram, Kick, Bluesky and more.
Thirteen distinct platforms appeared across 25 test profiles.

### Use cases

#### Influencer discovery

Create structured creator databases from Hoo.be profiles.

#### Creator economy analytics

Analyze how creators monetize — which stores, affiliate programs, newsletters
and paid platforms they link to.

#### Agency CRM

Enrich creator records with public profile and social information.

#### Creator commerce

Track public products, prices and storefront links.

#### Social graph enrichment

Resolve one creator across every social platform they list.

#### Monitoring

Track profile, link and product changes over time.

### Modes

| Mode | What it does |
|---|---|
| `PROFILE` | Scrape the handles you list |
| `BATCH_PROFILES` | Same, labelled for long lists (dozens to hundreds) |
| `DISCOVERY` | Adds every creator in Hoo.be's public sitemap (~100 profiles) |
| `MONITOR` | Scrape and report what changed since the previous run |

### Input

```json
{ "mode": "PROFILE", "profiles": ["alixearle"] }
```

Handles, `@handles` and full URLs all work and are normalized automatically:

```json
{
  "mode": "BATCH_PROFILES",
  "profiles": ["alixearle", "@perezhilton", "https://hoo.be/lydiaviolet"],
  "maxItems": 100
}
```

| Field | Default | Description |
|---|---|---|
| `mode` | `PROFILE` | See modes above |
| `profiles` | – | Handles or profile URLs (deduplicated automatically) |
| `maxItems` | – | Stop after this many profiles |
| `includeLinks` | `true` | Outbound links |
| `includeSocialProfiles` | `true` | Structured social accounts |
| `includeProducts` | `true` | Publicly priced items |
| `includeEmbeds` | `true` | Embedded content metadata |
| `onlyChanges` | `false` | MONITOR only — emit just change events |
| `stateStoreName` | `hoobe-monitor-state` | Named store holding monitoring snapshots |
| `maxConcurrency` | `2` | Kept low: Hoo.be rate-limits |
| `requestDelayMs` | `800` | Minimum gap between requests |
| `proxyConfiguration` | off | Optional — not needed by default |

### Output

```json
{
  "creatorId": "67a92efe9debda9cc95ae103",
  "username": "perezhilton",
  "displayName": "Perez Hilton",
  "bio": "The original blogger…",
  "profileUrl": "https://hoo.be/perezhilton",
  "avatarUrl": "https://cdn.hoobe.media/…webp",
  "verified": true,
  "customDomain": null,
  "socialProfiles": [
    { "platform": "instagram", "url": "https://instagram.com/theperezhilton", "username": "theperezhilton" },
    { "platform": "tiktok", "url": "https://tiktok.com/@thatshowbizdude", "username": "thatshowbizdude" }
  ],
  "links": [
    { "linkId": "6a0cfb018ad436137862271e", "title": "LUCY NICOTINE",
      "url": "https://lucy.co/PEREZ", "type": "PRODUCT", "platform": null,
      "position": 3, "destinationDomain": "lucy.co", "isAdultContent": false }
  ],
  "products": [
    { "productId": "6a0cfb018ad436137862271e", "name": "LUCY NICOTINE",
      "price": 42, "currency": null, "productUrl": "https://lucy.co/PEREZ" }
  ],
  "embeds": [
    { "variant": "youtube-channel", "platform": "youtube",
      "contentId": "UC2xO_e0eSftVTvagxWxDQaQ", "embedUrl": "https://www.youtube.com/embed/…" }
  ],
  "linkCount": 9, "socialProfileCount": 9, "productCount": 1, "embedCount": 2,
  "email": null,
  "scrapedAt": "2026-08-23T20:51:34.170Z",
  "source": "hoo.be"
}
```

Download as JSON, CSV, Excel, XML or HTML. The Console ships two prepared
views: **Creators** and **Change events**.

### Monitoring & change detection

First run stores a baseline and reports nothing. Later runs compare and emit:

`NEW_LINK` · `REMOVED_LINK` · `LINK_CHANGED` · `NEW_PRODUCT` ·
`PRODUCT_REMOVED` · `PRODUCT_PRICE_CHANGED` · `NEW_SOCIAL_PROFILE` ·
`SOCIAL_PROFILE_REMOVED` · `BIO_CHANGED` · `DISPLAY_NAME_CHANGED` ·
`AVATAR_CHANGED` · `VERIFIED_CHANGED`

```json
{
  "eventType": "PRODUCT_PRICE_CHANGED",
  "username": "somecreator",
  "subject": "Course bundle",
  "previousValue": 49,
  "currentValue": 39,
  "currency": null,
  "url": "https://example.com/course",
  "detectedAt": "2026-08-24T20:00:00.000Z",
  "profileUrl": "https://hoo.be/somecreator"
}
```

Two design guarantees, both tested: **two runs over an unchanged profile
produce zero events**, and removals are never reported when the run only
collected part of a profile (disabled sections or `maxItems`) — a missing link
would otherwise look deleted when it simply wasn't fetched.

Set `onlyChanges: true` for scheduled monitoring: unchanged profiles produce no
output and cost nothing beyond the run fee.

### API usage

Replace `<TOKEN>` with your Apify API token.

**curl**

```bash
curl -X POST "https://api.apify.com/v2/acts/huykenny~hoobe-creator-scraper/run-sync-get-dataset-items?token=<TOKEN>" \
  -H 'Content-Type: application/json' \
  -d '{"mode":"PROFILE","profiles":["alixearle"]}'
```

**JavaScript**

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

const client = new ApifyClient({ token: '<TOKEN>' });
const run = await client.actor('huykenny/hoobe-creator-scraper').call({
    mode: 'BATCH_PROFILES',
    profiles: ['alixearle', 'perezhilton'],
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
```

**Python**

```python
from apify_client import ApifyClient

client = ApifyClient("<TOKEN>")
run = client.actor("huykenny/hoobe-creator-scraper").call(
    run_input={"mode": "BATCH_PROFILES", "profiles": ["alixearle", "perezhilton"]}
)
items = client.dataset(run["defaultDatasetId"]).list_items().items
```

### Integrations

Standard Apify integrations apply: schedules, webhooks, Make, Zapier, n8n,
Google Sheets/Drive, Slack, and the Apify MCP server (which exposes every Store
Actor to AI agents — no separate MCP server needed for this Actor).

### Pricing

| Event | Price |
|---|---|
| `actor-start` | $0.005 per run |
| `creator-result` | $0.003 per profile |
| `change-event` | $0.003 per detected change |

| Profiles | Cost |
|---|---|
| 1 | $0.008 |
| 10 | $0.035 |
| 100 | $0.305 |
| 1,000 | $3.005 |

Failed profiles, duplicate inputs and unchanged monitoring results are **not
charged**.

### Limitations

Stated plainly, because they are properties of Hoo.be, not of this Actor:

- **Direct profile handles/URLs are the primary input.** Hoo.be has no public
  search or full creator directory. `DISCOVERY` reads Hoo.be's public sitemap,
  which lists **~100 creators** — a useful sample, not the whole platform.
- **Products are rare.** Only 1 of 65 tested profiles exposed a public price.
  The Actor extracts them when present, but most profiles have none.
- **No currency on prices.** Hoo.be publishes a price number without a
  currency, so `currency` is always `null` rather than a guess.
- **No follower, revenue, sales or traffic figures.** Hoo.be does not publish
  them publicly, so this Actor does not output or estimate them.
- **No creator email.** A Hoo.be contact block exposes only a button label, not
  an address. `email` is always `null`; no third-party enrichment is performed.
- **Rate limits are real.** Measured: 4 parallel requests with no delay produced
  HTTP 429 on 34 of 100 profiles. Defaults are deliberately conservative;
  lowering them may trigger throttling.
- Depends on Hoo.be's public page structure. If that changes, the Actor raises
  `PAGE_STRUCTURE_CHANGED` instead of quietly returning an empty profile.

### Responsible use

This Actor requests only public profile pages (`/{handle}`) and Hoo.be's public
`sitemap.xml`. It **does not** touch `/api/` or link-redirect paths, both of
which Hoo.be's `robots.txt` disallows, and it identifies itself honestly with
its own User-Agent. No login, no CAPTCHA solving, no authentication bypass, no
private or subscriber-only data, and no contact-detail guessing.

### FAQ

**Do I need a Hoo.be account?** No. Only public pages are read.

**Can I get every Hoo.be creator?** No — Hoo.be publishes no full directory.
Supply the handles you care about, or use `DISCOVERY` for the ~100 creators in
the public sitemap.

**Why is `currency` always null?** Hoo.be doesn't publish one next to the price.
Inventing "USD" would be a fabricated value.

**Why no follower counts?** Hoo.be doesn't expose them publicly.

**Does one bad handle break the run?** No. It becomes an error record in the
dataset (not charged) and the run continues.

**How do I get only changes?** `mode: MONITOR` with `onlyChanges: true`.

### Disclaimer

This Actor is **not affiliated with or endorsed by Hoo.be**. It extracts only
publicly accessible data. Users are responsible for complying with applicable
terms, privacy rules and laws.

# Actor input Schema

## `mode` (type: `string`):

PROFILE / BATCH\_PROFILES scrape the handles you provide (identical behaviour, both accept many profiles — BATCH\_PROFILES is just a clearer label for large lists). DISCOVERY adds every creator listed in hoo.be's public sitemap (~100 profiles — this is the only public creator list hoo.be exposes, not the full platform). MONITOR scrapes your handles and reports what changed since the previous run.

## `profiles` (type: `array`):

Hoo.be handles or profile URLs — `chumelenice`, `@chumelenice` and `https://hoo.be/chumelenice` all work. Duplicates are removed automatically. Required for every mode except DISCOVERY.

## `maxItems` (type: `integer`):

Stop after this many profiles. Leave empty for no limit.

## `includeLinks` (type: `boolean`):

Every outbound link with title, destination URL, classified type, platform and position.

## `includeSocialProfiles` (type: `boolean`):

Social accounts resolved into { platform, url, username }. Hoo.be labels the platform itself, so this is read rather than guessed.

## `includeProducts` (type: `boolean`):

Paid items with a public price. Note: most hoo.be profiles have none — roughly 1 in 65 tested profiles exposed a price, and hoo.be never publishes a currency alongside it.

## `includeEmbeds` (type: `boolean`):

Embedded YouTube / TikTok / Instagram / Spotify / Apple Music content with variant, content ID and embed URL.

## `onlyChanges` (type: `boolean`):

MONITOR only. Emit just the change events, not the full profile records — handy for scheduled runs, webhooks, Make, Zapier and n8n. Unchanged profiles produce nothing and are not charged.

## `stateStoreName` (type: `string`):

Named key-value store holding monitoring snapshots between runs. Change it to keep separate watch lists apart (e.g. one per client).

## `maxConcurrency` (type: `integer`):

Parallel requests. Kept low on purpose: hoo.be rate-limits — measured, 4 parallel requests with no delay produced HTTP 429 on 34 of 100 profiles.

## `requestDelayMs` (type: `integer`):

Minimum gap between requests, in milliseconds. Lower is faster but more likely to hit hoo.be's rate limit.

## `proxyConfiguration` (type: `object`):

Optional and off by default — hoo.be answers plain requests fine, so a proxy only adds cost. Turn it on only if you run very large batches from one IP.

## Actor input object example

```json
{
  "mode": "PROFILE",
  "profiles": [
    "alixearle"
  ],
  "includeLinks": true,
  "includeSocialProfiles": true,
  "includeProducts": true,
  "includeEmbeds": true,
  "onlyChanges": false,
  "stateStoreName": "hoobe-monitor-state",
  "maxConcurrency": 2,
  "requestDelayMs": 800,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `results` (type: `string`):

One record per creator profile (links, social profiles, products, embeds). In MONITOR mode the dataset also carries change-event records.

## `runSummary` (type: `string`):

Profiles requested/written, failures by error code, change-event totals, HTTP requests, traffic and charged events.

# 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 = {
    "profiles": [
        "alixearle"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("huykenny/hoobe-creator-scraper").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 = { "profiles": ["alixearle"] }

# Run the Actor and wait for it to finish
run = client.actor("huykenny/hoobe-creator-scraper").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 '{
  "profiles": [
    "alixearle"
  ]
}' |
apify call huykenny/hoobe-creator-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,huykenny/hoobe-creator-scraper"
        }
    }
}

```

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/9jUJXz7nn4isPplvX/builds/E5oBs95uf6fQyZm04/openapi.json