> 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/shared-options/scrape-metadata-options/account-sorting-args.md).

# Model Sorting & Processing Options

These options allow you to control how models are displayed in the list and the order in which they are processed during program actions (e.g., liking posts, downloading content)

> ℹ️ **When a model is set to renew, the "expired" option refers to the renewal date**

## Sorting Criteria

### -st, --sort \[argument]

* **Controls:** The order of the model list and processing order.
* **Possible choices:**
  * `name`: Sorts by model name (default).
  * `subscribed`: Sorts by whether the model is currently subscribed
  * `expired`: Sorts by the renewal date
  * `current-price`: Sorts by the current price of the model.
  * `promo-price`: Sorts by the promotional price of the model (if available).
  * `regular-price`: Sorts by the regular price of the model (if available).
  * `renewal-price`: Sorts by the renewal price of the model (if applicable).
  * `last-seen`: Sorts by the last time the model was seen
* **Example:** With `-st expired`, models with expiring subscriptions will be processed first.

### -ds, --desc

* **Arranges:** The model list in descending order.
* **Default:** `False` (ascending order)
* **Use case:** You might use this option to prioritize models at the bottom of the list (e.g., with `-st last-seen -ds`).


---

# 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/shared-options/scrape-metadata-options/account-sorting-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.