> For the complete documentation index, see [llms.txt](https://cloakedkeys.gitbook.io/ofsc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cloakedkeys.gitbook.io/ofsc/content-check-modes.md). # Content Check Modes ## What is this
It scrapes data from OnlyFans.com, parsing the database to showcase content information via a generated table. The check table is for OnlyFans only. Each media item occupies its own row within the table, which is searchable and offers filtering options. The table is comprehensive, containing various details for each entry * price of content * Will try to show if media is in your library based on media id * If the media is unlocked (a missing value shows as locked) * The post that a media is connected * Date the media was posted * text included with the media * Length of media It utilizes caching to expedite processes. The cache is established either during regular scraping or when running in content check mode, persisting for 3 days before the program updates with fresh data. Additionally, you can employ '--force' to fetch the most recent information. *** ## Opening it from the menu Run `ofscraper`, choose **Perform Action(s)**, then **Browse and pick media (check table)**. Pick the creators as usual, then the table: **Posts**, **Messages**, **Paid** or **Stories**. * While the media is fetched, the same page progress as a normal scrape is shown. * When you close the table, any downloads you sent from it finish, then you're back at the menu. * The menu uses the commands' defaults: a creator's saved post list when there is one, and for Posts the Timeline, Pinned, Archived and Streams areas. To fetch a fresh list or pick other areas, use the commands below with `--force` or `--check-area`. * Settings the table changes don't carry over to the next run. See [Table Management](/ofsc/content-check-modes/table-management.md) for picking and downloading media in the table. *** ## cmdline arguments ### ### Post Check Mode This functionality is for reviewing posts on the main timeline or for paid content accessed through the post URL 1. you must add the --url or --file argument (areas come from `--check-area`, default Timeline, Pinned, Archived and Streams) 2. You can combine the previous args 3. \--url can be split by comma or passed multiple times 4. \--file can only be passed once, and does not spit string will be interpreted as single url #### Examples `ofscraper post_check --url url,url,url` `ofscraper post_check --url url --url url` `ofscraper post_check --file file` `ofscraper post_check --file file --url url` #### File Should contain accepted urls line separated #### Accepted urls **post page** ``` https://onlyfans.com/1113331313/model ``` **model page** ``` https://onlyfans.com/model ``` **model name** ``` model ``` **model number** ``` 11131313 ``` ### ### Message Check Mode To avoid redundancy, the "check mode" is equivalent to "post\_check," differing only in the accepted types of posts. When the cache expires all messages must be scraped again. #### Examples Again all the previous examples will work `ofscraper msg_check --url url,url,url` #### Accepted urls **chat page** ``` https://onlyfans.com/my/chats/chat/11131313/ ``` **model name** ``` model ``` **model number** ``` 11131313 ``` ### ### Paid Check Mode It gathers paid content using the username provided 1. you must add the --username or --file argument 2. You can combine the previous args 3. \--username can be split by comma or passed multiple times 4. \--file can only be passed once, and does not spit string will be interpreted as single username #### Examples ``` ofscraper paid_check --username username,username ``` ``` ofscraper paid_check --username username --username username ``` ``` ofscraper paid_check --file file ``` ``` ofscraper paid_check --file file --username username ``` #### File Should contain usernames line separated #### Accepted username **model name** ``` model ``` **model number** ``` 11131313 ``` ### ### Story Check Mode It collects stories and highlights using the provided username > stories are temporary content and may change frequently 1. you must add the --username or --file argument 2. You can combine the previous args 3. \--username can be split by comma or passed multiple times 4. \--file can only be passed once, and does not spit string will be interpreted as single username #### Examples `ofscraper story_check --username username,username` `ofscraper story_check --username username --username username` `ofscraper story_check --file file` `ofscraper story_check --file file --username username` #### File Should contain usernames line separated ### ### Getting latest content In each of these modes, details for each model are cached (3 days for msg\_check). To fetch the most recent content, append the "--force" argument to any of these modes. ``` ofscraper msg_check --url url --force ``` --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://cloakedkeys.gitbook.io/ofsc/content-check-modes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.