> For the complete documentation index, see [llms.txt](https://rpfs.gitbook.io/rpfs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rpfs.gitbook.io/rpfs/links-structure.md).

# Links Structure

By default if you don't create any new custom Gateways or Folders, your links might look quite long as they use generated sets of characters. To make them look shorter and user friendly you can either rename the Default Gateway and Sync the slug, or/and Use Folders that are as well having the option for the name to be synced with the slug. \
\
Below you can see how a link looks like with a default Gateway and Folder name synced. At the end of the link you will see the CID which is a unique code for each file uploaded to IPFS. 

<figure><img src="/files/CrtL2xxXhenE2Goagc0w" alt=""><figcaption></figcaption></figure>

And below is a link with a custom Gateway name synced with the slug. Remember, these custom gateway names are unique across all RPFS user accounts.

<figure><img src="/files/2uVYUbP29uTmAQaaped1" alt=""><figcaption></figcaption></figure>


---

# 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://rpfs.gitbook.io/rpfs/links-structure.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.