Hugging Face Models Scraper
Pricing
from $0.30 / 1,000 model records
Hugging Face Models Scraper
Export public Hugging Face model metadata, downloads, likes, tags, licenses and update dates for model research and organization comparisons.
Pricing
from $0.30 / 1,000 model records
Rating
0.0
(0)
Developer
Fetch Cat
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
23 days ago
Last modified
Categories
Features
Share
Export public Hugging Face model metadata into a dataset: model IDs, downloads, likes, tags, licenses and update dates. Hugging Face Models Scraper helps AI teams compare model catalogs and organization activity without downloading model weights or signing in to Hugging Face.
Quick start
- Open the Input tab and paste the example below.
- Click Start and open the dataset when the run finishes.
- Export JSON, CSV or Excel, or retrieve rows through the Apify API.
{"search": "llama","pipelineTag": "text-generation","sort": "downloads","limit": 10,"includeDetails": false}
This returns up to ten matching public models, not model files or full model-card text. Missing metadata remains empty. Restrictive searches can produce no rows.
Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.
Ready-to-run examples
Choose a public example to see its settings before starting a run:
- Scrape detailed Hugging Face model card metadata
- Scrape Hugging Face models by organization
- Scrape popular Hugging Face text generation models
What you get
One public model-catalog row with its ID, namespace and page URL, plus available downloads, likes, task/library tags, license metadata and revision dates. Optional detail requests can add structured card metadata and file counts. This does not download model weights, full card text or inference responses.
Who is it for?
- ML researchers assembling source-linked model candidates for separate evaluation.
- AI product teams reviewing public task and organization catalogs.
- Model-governance reviewers collecting reported license and access metadata for further checks.
- Catalog-data engineers joining model IDs and comparing their own saved snapshots.
How you can use the data
- Review a text-generation model sample. Use the existing llama search, text-generation task and ten-record cap with details off. Keep IDs, URLs and available downloads and likes together without treating them as benchmark scores.
- Inspect one organization's public catalog. Use the existing google namespace example with a small cap and chosen source sort. Retain author, tags, last-modified dates and revision values for source review rather than assuming all organizational activity was captured.
- Choose detail metadata when it matters. Enable optional details to inspect available structured card data and file counts. Retain detailFetched and detailError, because a failed request can leave a useful summary model row rather than removing it.
- Maintain your own model review sheet. Join model IDs with collection times, revisions and reported licenses. Check source license documents before making use decisions. Accepted library, language and license filters do not reliably narrow results, and inferred language tags are not a language audit. Cross-run changes are calculated in your own workflow.
Input settings
Filters are optional. No search field is globally required. Set limit explicitly for repeatable API calls.
| Setting | API key | Purpose |
|---|---|---|
| Search query | search | Search public model names/IDs. |
| Author / organization | author | One namespace, such as google. |
| Pipeline tag | pipelineTag | One task, such as text-generation. |
| Sort models by | sort | downloads, likes, trending or lastModified, descending. |
| Maximum models | limit | Save 1–1,000 records at most. The form starts at 20. |
| Include detail data | includeDetails | Request additional metadata. Off by default. |
| Library / framework | library | Accepted input. Currently does not reliably narrow results. |
| License | license | Accepted input. Currently does not reliably narrow results. |
| Language | language | Accepted input. Currently does not reliably narrow results. |
| Gated access | gated | Request gated or ungated public catalog entries. |
| Inference provider | inferenceProvider | Send a provider filter to the catalog. |
| Maximum run time | maxRunSeconds | 35–270 seconds, default 270. The run may stop collecting earlier. |
See each input's help for details. For library, language and license selection, inspect the returned libraryName, tags and license rather than assuming those input fields enforce a restriction.
Example inputs
Use the Quick start input as a small first run. Adjust the fields described above for your own data.
Output data
One row represents one model. This abbreviated example illustrates the output shape only. It is not a current model snapshot:
{"modelId": "example-org/example-model","author": "example-org","name": "example-model","url": "https://huggingface.co/example-org/example-model","likes": null,"downloads": null,"tags": [],"license": null,"detailFetched": false,"detailError": null}
| Fields | Meaning |
|---|---|
modelId, author, name, url | Identity, namespace and public model page. |
downloads, downloadsAllTime, likes, trendingScore | Popularity values only when reported. Unavailable numbers are null. |
tags, pipelineTag, libraryName, languages | Tags, task and library. languages is inferred from short language-like tags, not a language audit. |
license | Reported license from metadata or license tags. |
createdAt, lastModified, sha | Creation/update information and repository revision when reported. |
private, gated | Reported access flags. gated may be a boolean or text value. |
siblingsCount, cardData | File count and optional structured model-card metadata, not file downloads or card text. |
modelCardUrl | Constructed link to the model's main-branch README. Availability is not guaranteed. |
detailFetched, detailError | Whether extra details were returned and a note if they could not be obtained. |
scrapedAt | Collection timestamp. |
The key-value store's RUN_SUMMARY records saved counts, detail failures and warnings. A failed detail lookup can leave a useful summary row with detailFetched: false. It does not make the entire model disappear.
Download your results
Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.
See Apify's download and export guide for the available formats and field options.
Pricing
The apify-actor-start event charges for starting a run, and item charges for each saved model record, including a summary row whose optional detail request failed. Empty searches have no model-record events, while the start event still applies.
See the live Pricing tab for current rates and discounts.
Tips for best results
- Start with a small explicit model cap. Leave optional details off until their extra metadata is needed.
- Use the intended task and author filters deliberately. Broaden restrictive searches when a valid catalog query yields no records.
- Inspect returned library, language and license metadata. The accepted filters for those fields do not reliably enforce a restriction.
- Keep detail outcome fields with summary rows. Missing extra metadata is different from a missing model.
- Retain source URLs and revision values for later review. Popularity metrics and modification dates are observations rather than evaluation results.
Limits and caveats
Coverage depends on the public catalog and the run's time budget. A model cap is a ceiling rather than completeness. Valid searches without matching public records can succeed with an empty dataset. Rate limits or catalog-list failures can fail a run while completed rows remain available. Inspect RUN_SUMMARY and platform status for saved counts, detail failures and warnings.
Only public metadata is collected. Gated models may expose catalog entries, but the Actor does not unlock protected files or fetch private repositories. Model weights, inference responses, benchmarks, datasets and Spaces are outside scope, and no Hugging Face login is required. This is not an official Hugging Face service.
Optional fields can be null or empty. Structured card metadata is not full card text, and a constructed model-card URL is not guaranteed to be available. Languages inferred from short tags are not an audit. Library, license and language filters are accepted but do not reliably narrow results. Verify critical source metadata before using it in another system, and perform historical comparisons yourself.
Automation and integrations
Save your settings for next time
Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.
Run on a schedule
Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.
Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.
Send results to your other tools
Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.
For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.
API usage
Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.
The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.
For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.
cURL
curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~hugging-face-models-scraper/runs' \-H "Authorization: Bearer $APIFY_TOKEN" \-H 'Content-Type: application/json' \--data @- <<'JSON'{"search": "llama","pipelineTag": "text-generation","sort": "downloads","limit": 10,"includeDetails": false}JSON
Node.js
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: process.env.APIFY_TOKEN });const run = await client.actor('fetch_cat/hugging-face-models-scraper').call({"search": "llama","pipelineTag": "text-generation","sort": "downloads","limit": 10,"includeDetails": false});const { items } = await client.dataset(run.defaultDatasetId).listItems();console.log(items);
Python
import osfrom apify_client import ApifyClientclient = ApifyClient(os.environ['APIFY_TOKEN'])run = client.actor('fetch_cat/hugging-face-models-scraper').call(run_input={'search': 'llama', 'pipelineTag': 'text-generation', 'sort': 'downloads', 'limit': 10, 'includeDetails': False})print(client.dataset(run['defaultDatasetId']).list_items().items)
MCP and AI agents
You can ask your AI assistant to collect data with Hugging Face Models Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.
Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.
Easier setup with an Apify plugin
If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.
Use Apify AI in Console
Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Hugging Face Models Scraper. You can describe the data you want and ask questions about the results.
Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.
Choose your assistant
- Claude and Claude Code (Anthropic): Apify setup guide.
- ChatGPT and Codex (OpenAI): Apify setup guides.
- Grok Bot (xAI): Apify plugin guide.
- Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.
Connect just this scraper
To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:
{"mcpServers": {"apify": {"url": "https://mcp.apify.com?tools=fetch_cat/hugging-face-models-scraper"}}}
Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.
Use Apify's general server
Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Hugging Face Models Scraper by Fetch Cat, or give it the identifier fetch_cat/hugging-face-models-scraper.
Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.
Example requests
- “Use Fetch Cat’s Hugging Face Models Scraper to collect up to 5 public llama models for text generation sorted by downloads, with details off. Show model IDs, source links and available popularity metrics without treating them as benchmarks.”
- “Collect up to 5 public models from author google sorted by last modification with detail metadata enabled. Keep revision dates and detail outcome fields without downloading model weights or claiming full model-card text.”
- “Retrieve up to 3 public llama text-generation model records sorted by downloads with details enabled. Show available reported license, library and language tags for source review, flagging missing values and unreliable input-filter restrictions.”
Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.
Pay with x402
If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.
Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.
Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.
Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.
Other ways for agents to pay
Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.
FAQ
Can I use this as a Hugging Face models API?
Yes, for public model metadata through Apify's API or MCP. It is an independent tool, not an official Hugging Face service, and does not serve inference or download model weights.
Can I export a list of Hugging Face models to CSV?
Yes. Run a bounded search, then export the dataset as CSV, Excel or JSON. No Hugging Face login is required.
Why did I get fewer models than requested?
There may be fewer matches or the time budget may have stopped collection. Check RUN_SUMMARY. A valid search with no matching public records succeeds with an empty dataset. Broaden the search or remove a task/author filter.
Why are model details or licenses missing?
Not every model publishes the same metadata. includeDetails can improve coverage but cannot guarantee every field. A detail failure preserves summary data where available. Check the original model page before relying on a license.
Related Actors
- GitHub Repository Search Scraper — Discover source repositories for AI projects.
- GitHub Trending Scraper — Explore trending software repositories.
- arXiv Paper Search Scraper — Find research-paper metadata.
- PubMed Search Scraper — Collect biomedical publication metadata.
- Product Hunt Scraper — Research product launches.
Support and feedback
For custom additions or integrations, email hello@fetchcat.dev.
Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.
Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.
Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.
Made with care for curious people, AI agents and the possibilities in data. ♥