# /mega/store

Robot: `/mega/store`

The URL to the result file will be returned in the \<dfn>Assembly Status JSON\</dfn>.

Stage: ga

## Example

```json
{
  "steps": {
    "exported": {
      "robot": "/mega/store",
      "use": ":original",
      "credentials": "YOUR_MEGA_CREDENTIALS",
      "path": "my_target_folder/${unique_prefix}/${file.url_name}"
    }
  }
}
```

## Parameters

* `interpolate`: Controls whether Assembly Variables are interpolated for individual instruction fields. By default, most Robot instruction fields interpolate Assembly Variables. Set this to \`false\` to treat every instruction field as literal text, or set an individual field path to \`false\` to treat only that field as literal text. For Robot-specific fields that are literal by default, set this to \`true\` or set that field path to \`true\` to opt back into interpolation. Use field names such as \`path\`, or dotted paths such as \`ffmpeg.vf\` for nested objects.
* `output_meta`
* `result`
* `queue`
* `force_accept`
* `ignore_errors`
* `use`: Specifies which Step(s) to use as input. - You can pick any names for Steps except \`":original"\` (reserved for user uploads handled by Transloadit) - You can provide several Steps as input with arrays: \`\`\`json { "use": \[ ":original", "encoded", "resized" ] } \`\`\` - You can also tag an input Step with \`as\` to pass semantic intent to robots: - You can also tag input Steps with \`as\` to pass semantic intent to robots: \`\`\`json { "use": \[ { "name": ":original", "as": "image" }, { "name": ":original", "as": "mask" } ] } \`\`\` > \[!Tip] > That's likely all you need to know about \`use\`, but you can view \[Advanced use cases]\(/docs/topics/use-parameter/).
* `credentials`
* `bucket`
* `bucket_region`
* `host`
* `key`
* `secret`
* `path`
* `acl`
* `headers`
* `sign_urls_for`