# Hugging Face Spaces Monitor - AI Demo Discovery & Likes — workflow

## Choose this tool

AI product scouts and developers researching public demos.

<!-- B18-REAL-SAMPLE --> Track which public demo listings appear and how their likes and SDK metadata change.

Useful output columns: `title`, `repositoryId`, `likes`, `sdk`, `createdAt`, `comparisonStatus`.

## Practical workflow

**Useful output:** A topic-based inventory of public Hugging Face Spaces for product and developer research.

1. Start with the small example input on this page and replace its targets with your watchlist. Review the result cap and set an Apify maximum run charge before running.
2. Review the dataset and Run report together. Use `recordId` / `repositoryId` as the destination identity, preserving source links and null values.
3. Map `sdk`, `tags`, `likes` and `createdAt` into a research board. Review changed SDK/tags for integration relevance and source-reported like changes as one interest signal. Open shortlisted Spaces separately to assess their actual behavior; this Actor makes no inference calls or availability checks.

**Repeat safely.** Enable `comparePrevious`, keep the same input scope and `snapshotName`, and run one writer at a time. The first saved comparison establishes history; `new` means first observed in this history, not newly published. Later, `onlyChanges: true` skips unchanged rows. Check SUMMARY for failures, limits and history updates before interpreting zero output. Missing records in a bounded window do not establish deletion.

**Delivery:** Export JSON for nested fields or map selected columns into your own sheet/database. Upsert by the row identity below; retain the run ID and observation time for replay. Scheduling and destination delivery are separate setup steps.

## Check the fit

Public Spaces search ordered by likes, one page. No inference calls, tool execution, availability tests or private Spaces. Likes do not establish product quality.

At most ten input values and five hundred saved rows per run. Results requested per query controls a single source page (1–50, default five); there is no pagination. Each input performs one bounded public source request; Requests are paced. Responses are capped at 8 MiB and share the run deadline. No authentication bypass or code execution is performed. HTTP 429 stops further requests. Source failures appear in SUMMARY and the HTML report, never as paid data rows.

## Real output sample

One selected row from a 2026-10-18 run. One saved row, selected scalar columns only. Contact details, patient demographics and long text are omitted. Original values and nulls are preserved.

Run: eH5ASb01icmz4rmbE. Summary status: ok. Incomplete: false.

Historical output from this run; the current example input is a separate starting configuration and may produce different records.

```json
{
  "title": "black-forest-labs/FLUX.1-dev",
  "repositoryId": "black-forest-labs/FLUX.1-dev",
  "likes": 9583,
  "sdk": "gradio",
  "createdAt": "2024-08-01T14:14:02.000Z",
  "comparisonStatus": "not_requested",
  "url": "https://huggingface.co/spaces/black-forest-labs/FLUX.1-dev",
  "recordId": "black-forest-labs/FLUX.1-dev",
  "sourceUrl": "https://huggingface.co/api/spaces?search=flux&limit=5&sort=likes&direction=-1",
  "observedAt": "2026-10-18T04:10:20.497Z"
}
```

## Combine with companion tools

Each Actor runs separately with its own inputs, authorization and pricing. These instructions do not configure automatic execution.

### [Hugging Face Model Change Monitor](https://mayd-it.com/data-tools/actors/huggingface-model-change-monitor/)

Track public Hugging Face model revisions, declared license, gating, base models and artifact paths. Saved comparisons for deployment watchlists. Metadata only; no model download or execution. Keep this Hugging Face Model Change Monitor evidence alongside the original source in a reviewed ai stack review workflow.

1. Choose the corresponding source target in this second Actor’s own input form; no automatic field transfer is configured.
2. Keep both original source URLs and observation dates in your review sheet; reconcile identities manually.

An advertised capability, catalog listing or rate is not a benchmark or availability guarantee. Match provider, model revision and units before comparing.

### [GitHub Repository Change Monitor - Stars, Forks & Activity](https://mayd-it.com/data-tools/actors/github-repository-change-monitor/)

Track the exact public repository’s metadata, license and activity dates alongside the discovery or release signal.

1. Choose the corresponding source target in this second Actor’s own input form; no automatic field transfer is configured.
2. Keep both original source URLs and observation dates in your review sheet; reconcile identities manually.

An advertised capability, catalog listing or rate is not a benchmark or availability guarantee. Match provider, model revision and units before comparing.
