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

# Metadata Update

If your collection is `Mutable` and an error is identified in the metadata. Our team can update all the data with an off-chain and on-chain solution. If the metadata update is time-sensitive, then it is recommended to update all metadata using an off-chain VPS and then to follow up with a on-chain storage solution. As the off-chain solution can be completed within hours (with images), while the on-chain can take 1-2 days depending on the collection and image size.

### Data Stored on VPS (off-chain)

An off-chain private server will host the metadata, this is very beneficial if the metadata needs to be often updated. As changes can be made extremely quickly. There are over-head costs with a VPS but can be considered fairly negligible.

### Data Stored on Arweave (on-chain)

For a more permanent solution, an on-chain database like Arweave or alternative can be utilized. However it is not recommended for time-sensitive metadata updates, that require changes to be made immediately. 


---

# 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://docs.solpatrol.io/services/metadata-update.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.