> 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/getting-started/config-options/setting-metadata-path.md).

# Setting metadata path

In the config.json file, you can modify the default metadata location or adjust where the script searches for database files

Using your existing metadata files from DIGITALCRIMINALS' script enables immediate utilization of the dupe checker, with any new files added subsequently being appended to the existing ones

***

## Config File Location

[Config Location](/ofsc/getting-started/config-options/config-location.md)

## Changing metadata location

Adjust the metadata section in the config.json file by inserting the appropriate locations or paths using the provided placeholders

```
{sitename} = Onlyfans

{first_letter} = first letter of model's username

{model_username} = The model's username.

{model_id}= Unique identification number for model
{config_path}= The directory containing the config.json file
{profile} =The currently active profile
{save_location} = This option retrieves the parsed path specified in the 'save_location' 
option
{my_username}=The authorized account's username
{my_id} = The identification number assigned to the authorized account

{current_price}= Free if current price is 0 dollars else paid
{regular_price}=Free if regular price is 0 dollars else paid
{promo_price}= Free if promo price is 0 dollars else paid
{renewal_price}= Free if renewal price is 0 dollars else paid
```


---

# 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/getting-started/config-options/setting-metadata-path.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.