> 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/overview.md). # Overview **For AI agents:** Read the [VGS Agent Guide](https://docs.verygoodsecurity.com/skill.md) before planning or implementing a VGS integration. For a specific reference question, answer directly from this page. VGS stores sensitive data and tackles critical payment acceptance challenges such as multi-PSP management, card issuance, payment orchestration enablement, PCI compliance, and the protection of personally identifiable information (PII). We provide our clients with complete ownership, control, and insights into their payment data, driving growth and enhancing user experiences across industries. VGS offers a comprehensive suite of solutions, including a composable Credential Management Platform, a PCI-compliant Vault, and advanced network value-added services such as Network Tokens, Account Updater, and Card Attributes. Our innovative technologies empower businesses to boost revenue through higher authorization rates, reduce fraud, and streamline operations - all while seamlessly integrating with existing tech stacks. At VGS, we're not just securing payments - we're empowering businesses to unlock new possibilities in the ever-evolving payment landscape. **Clients who are signed up to the Credential Management Platform (CMP) should navigate to this** [**page.**](https://docs.verygoodsecurity.com/card-management) --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.verygoodsecurity.com/overview.md?ask=&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 `build a script that syncs our docs to a CMS` 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.