> For the complete documentation index, see [llms.txt](https://data-programs.gitbook.io/singularity/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://data-programs.gitbook.io/singularity/kr/cli-reference/storage/create/premiumizeme.md).

# Premiumizeme

{% code fullWidth="true" %}

```
이름:
   싱귤래리티 저장소 만들기 premiumizeme - premiumize.me

사용법:
   singularity storage create premiumizeme [command options] [arguments...]

설명:
   --api-key
      API 키입니다.
      
      보통 사용하지 않습니다 - 대신 OAuth를 사용하십시오.
      

   --encoding
      백엔드의 인코딩입니다.
      
      자세한 내용은 [개요의 인코딩 섹션](/ko/overview/#encoding)을 참조하십시오.


옵션:
   --api-key value  API 키입니다. [$API_KEY]
   --help, -h       도움말 표시

   고급

   --encoding value  백엔드의 인코딩입니다. (기본값: "Slash,DoubleQuote,BackSlash,Del,Ctl,InvalidUtf8,Dot") [$ENCODING]

   일반

   --name value  저장소의 이름 (기본값: 자동 생성)
   --path value  저장소의 경로

```

{% endcode %}


---

# 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://data-programs.gitbook.io/singularity/kr/cli-reference/storage/create/premiumizeme.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.