> For the complete documentation index, see [llms.txt](https://docs.verygoodsecurity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verygoodsecurity.com/agentic-commerce/create-a-vgs-vault.md).

# Create a VGS Vault

Before your system (or agent) can collect, tokenize, or route sensitive data through VGS, you'll need to create a **VGS Vault**.

A Vault is your secure, isolated environment inside VGS. It acts as the central control plane for:

* Tokenizing and storing sensitive data
* Configuring secure data routes via the Inbound and Outbound Proxies

***

## Step-by-Step: Creating a Vault

### Step 1. **Sign up for an account using the VGS Dashboard**

Go to [dashboard.verygoodsecurity.com](https://dashboard.verygoodsecurity.com) and sign in. If you don't have an account, you can create one for free.

After you sign up for an account, VGS will automatically create an Organization and Vault. Please feel free to customize your experience by renaming your sandbox Organization or Vault and inviting your teammates to collaborate in the same organization.

<figure><img src="https://1369411143-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEYGADKmInkvdSjYRdEeA%2Fuploads%2FTFa4KW8pKt55xTu27TyF%2Fimage.png?alt=media&amp;token=5032af8c-9ef5-4f85-b052-bb412daf6e99" alt=""><figcaption></figcaption></figure>

If you already have a VGS Organization and Vault setup, you can create additional vaults using the "+ New" button in the dashboard or via the [VGS CLI](https://www.verygoodsecurity.com/docs/vgs-cli/commands#generate-2).

<figure><img src="https://1369411143-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEYGADKmInkvdSjYRdEeA%2Fuploads%2FkgKJf7JPHy8DqztSPV8O%2Fimage.png?alt=media&amp;token=03560875-7e8a-444f-81df-09c0cc886e5b" alt=""><figcaption></figcaption></figure>

***

### Step 2. **Find Your Vault ID**

You’ll see a unique tenant identifier in the top-left of your Vault (e.g. `tnt123abcde`).\
This is your **Vault ID** - used to initialize VGS Collect, route traffic, and configure APIs. \
\
Note: Vault ID can also be referred to as **Tenant ID**.

<figure><img src="https://1369411143-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEYGADKmInkvdSjYRdEeA%2Fuploads%2FgmJWzGUcZrqh05bxauTv%2Fimage.png?alt=media&amp;token=978a5477-2b0d-4a21-8955-d96f4449625c" alt=""><figcaption></figcaption></figure>

***

### What Can I Do With a Vault?

| Feature         | Description                                                                                                             |
| --------------- | ----------------------------------------------------------------------------------------------------------------------- |
| VGS Collect     | Secure front-end collection of card/PII data                                                                            |
| Inbound Proxy   | Tokenize miscellaneous data before it enters your environment.                                                          |
| Outbound Proxy  | Reveal and send data to PSPs or third parties                                                                           |
| Card Management | Get access to additional card services such as network tokens and cryptograms that can be used for agent-based payments |

***

### Step 3. Enable Card Management

If not already done, please email <support@vgs.io> to enable the [VGS Credential Management API](/cmp/platform/cmp-account.md) on your account.


---

# 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://docs.verygoodsecurity.com/agentic-commerce/create-a-vgs-vault.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.
