> For the complete documentation index, see [llms.txt](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/docs/sources/source-compliance-huggingface-papers.md).

# Source Compliance: Hugging Face Papers

> Implementation-time review completed 2026-05-27. Trend Finder has a configured Apify source declaration for public Hugging Face Papers metadata. This review covers metadata-only current collection through Apify, not a direct Hugging Face adapter.

***

## Source Overview

| Field                   | Value                                                           |
| ----------------------- | --------------------------------------------------------------- |
| Source ID               | `huggingface-ai-papers`                                         |
| Source name             | Hugging Face Papers                                             |
| Primary Apify candidate | `parseforge/huggingface-papers-scraper`                         |
| Store page              | <https://apify.com/parseforge/huggingface-papers-scraper>       |
| Verified on             | 2026-05-27                                                      |
| Default build/tag       | `latest`, build `1.0.11`                                        |
| Default run options     | 4096 MB memory, 3600 second Actor timeout                       |
| Pricing observed        | Pay per event, result item around `$9.00 / 1,000 results`       |
| Trend Finder status     | Reviewed static declaration, fixture-backed normalizer coverage |

The Actor input schema reviewed on 2026-05-27 exposes `searchQuery`, `mode`, and `maxItems`. The reviewed Trend Finder starter input uses current `mode: "trending"` with `maxItems: 10`.

## Terms And Use Boundary

The Actor collects public Hugging Face Papers metadata and returns structured Dataset rows. Trend Finder may use this source only as a compact link-and-rank signal. Apify storage, run IDs, Dataset IDs, and Apify-hosted item URLs are not durable browser evidence and must not be emitted to browser payloads.

Approved browser-safe evidence:

* Paper title.
* Public arXiv URL when available, otherwise public Hugging Face paper URL.
* Short summary or abstract snippet with length cap.
* Published timestamp.
* Aggregate public upvote and comment counts.

Excluded fields:

* Author names, author lists, Hugging Face handles, affiliations, or profiles.
* GitHub repository links and project pages in the first pass.
* AI keyword arrays in the first pass.
* Thumbnails, media URLs, images, or downloaded files.
* Full paper bodies, PDFs, private telemetry, Actor run URLs, or Dataset IDs.

## Retention And Attribution

| Policy               | Value                                                                                         |
| -------------------- | --------------------------------------------------------------------------------------------- |
| Storage location     | `src/data/live-data.json` and private cache snapshots                                         |
| Retention period     | `live-data.json` overwritten on each collection run; snapshots retained locally until deleted |
| Historical retention | Local snapshots only; no reviewed historical collection window                                |
| Deletion path        | Delete generated Trend Finder data and snapshots                                              |
| Attribution          | Show source ID `huggingface-ai-papers` and link to the public paper URL                       |

## Historical Window Stance

| Field                  | Value                                                                                         |
| ---------------------- | --------------------------------------------------------------------------------------------- |
| Historical support     | Current-only                                                                                  |
| Source ID              | `huggingface-ai-papers`                                                                       |
| Safe override fields   | None                                                                                          |
| Unsupported reason     | Trending and search inputs are current views and are not reviewed bounded historical windows. |
| Compliance declaration | `historicalWindowSupport.supported = false`                                                   |

Do not translate a requested historical window into `mode` or `searchQuery` without a separate review of bounded date semantics and deletion behavior.

## Compliance Checklist

* [x] Current Apify Actor ID verified on 2026-05-27
* [x] Input fields and mode values reviewed
* [x] Default build/tag and pricing model recorded
* [x] Metadata-only browser evidence boundary documented
* [x] Apify storage excluded as durable browser evidence
* [x] Retention and deletion path documented
* [x] Attribution requirements documented
* [x] Historical-window stance recorded as current-only
* [x] Fixture-backed normalizer validation added
* [x] Live tiny capped validation completed with credentials on 2026-05-27


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/docs/sources/source-compliance-huggingface-papers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
