> 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/command-reference/content-check-mode-args.md).

# Content Check Modes Options

These options are used with specific subcommands of the program that perform content checks for different data types (posts, messages, purchased content, stories/highlights)

> ℹ️ **Cached information is generally stored for around 3 days to improve efficiency**

***

## Syntax

```
ofscraper [subcommand_name] [subcommand_options]
```

### example

```
ofscraper post_check --url test
```

## General Options

[General Program Options](/ofsc/command-reference/shared-options/common-option-groups.md)

## Subcommand Options

Each content check subcommand (`post_check`, `msg_check`, `paid_check`, `story_check`) accepts common arguments for specifying content sources and controlling update behavior.

### Specifying Content Source

One of `-u` or `-f` is required.

* **-u, --url \[argument]:** (`post_check`, `msg_check`)
  * Scans content from one or more URLs provided as arguments (separate URLs with spaces or commas). `post_check` also accepts bare usernames.
  * `msg_check` also accepts a creator username, or any text containing a number, which is taken as the model id (e.g. a chat URL).
* **-u, --usernames \[argument]:** (`story_check`, `paid_check`)
  * Scans content from one or more usernames (`paid_check` also accepts a user id).
* **-f, --file \[argument]:** (all subcommands)
  * Scans content from a file with one entry per line. For `post_check` and `msg_check` the entries are URLs (or usernames, as above); for `story_check` and `paid_check` they are usernames.

### Forcing Update

* **-fo, --force:** (`post_check`, `msg_check`, `paid_check`, `story_check`)
  * **Default:** `False` (uses cached data if available).
  * Forces the API to retrieve the latest information, bypassing the cache.

### Text

### **-tn, --text**

* Specify to download text with any media tied to that text
* Available in `post_check` and `msg_check`

### **-tp, --text-only**

* Specify to download only text, skipping any media
* Available in `post_check` and `msg_check`

`--text` and `--text-only` cannot be used together.

### Post areas (`post_check` only)

* **-ca, --check-area \[argument]:** The areas to check: `all`, `archived`, `timeline`, `pinned`, `labels`, `streams`. Several can be given, separated by spaces. Default: `timeline`, `pinned`, `archived` and `streams`. Also `--post`, `--posts`.
* **-tls, --timeline-strict:** When `timeline` is selected, removes pinned and archived posts.

### Table filters

Each check subcommand also has its own table filters: `-ucl, --unlocked` or `-lc, --locked`, `-dwl, --downloaded` or `-ndw, --not-downloaded`, `-pf, --posted-after`, `-pb, --posted-before`, `-mid, --media-id`, `-pd, --post-id`, `-to, --protected-only` or `-no, --normal-only`, `-lx, --length-max`, `-lm, --length-min`, `-mt, --mediatype`, `-mdc, --media-desc`, `-sm, --size-min` and `-sx, --size-max`. Run `ofscraper <subcommand> --help` for the full list.

`-mst, --media-sort` here takes `number`, `username`, `downloaded`, `unlocked`, `length`, `mediatype`, `post_date`, `post_media_count`, `responsetype`, `price`, `post_id`, `media_id` or `text`.

> ℹ️ **Fork:** `msg_check` has its own `--help`, and bad command-line input prints a short usage message. A failed run exits with status 1.

## Subcommand Descriptions

**Here's a summary of each content check subcommand:**

* **post\_check:** Analyzes data associated with posts from specified URLs or a file. It generates a table displaying relevant information about the posts.
* **msg\_check:** Analyzes data associated with messages from specified URLs or a file. It generates a table displaying relevant information about the messages.
* **paid\_check:** Analyzes data associated with purchased content from specified usernames or a file. It generates a table displaying relevant information about the purchased content.
* **story\_check:** Analyzes data associated with stories and highlights from specified usernames or a file. It generates a table displaying relevant information about the stories/highlights.


---

# 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/command-reference/content-check-mode-args.md?ask=<question>&goal=<user_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.