Very Good Security
Very Good Security (VGS) is a data security and payments infrastructure company that lets organizations operate on sensitive data — payment card numbers, bank accounts, PII, and other regulated information — without the cost or liability of storing it themselves. Its core Vault tokenization platform substitutes sensitive values with format-preserving aliases so customer systems never touch raw data, dramatically reducing PCI DSS, SOC 2, HIPAA, and GDPR compliance scope. VGS also offers Zero Data (a proxy that keeps the customer environment entirely out of PCI scope), a Card Management Platform (network tokens, account updater, 3D Secure), and VGS Control for compliance automation. The developer surface includes the Vault HTTP API for aliases/tokenization, VGS Collect and VGS Show client SDKs, a Terraform provider, and the vgs-cli command line tool. Founded in 2015, VGS is backed by a16z and stores over 5 billion tokens.
Very Good Security publishes 1 API on the APIs.io network: aliases API. Tagged areas include Company, Data Security, Tokenization, Payments, and Vault.
The Very Good Security catalog on APIs.io includes 1 event-driven AsyncAPI specification.
Very Good Security’s developer surface includes CLI, sandbox, changelog, authentication, documentation, API reference, getting-started guide, and 30 more developer resources.
Kin Score
APIs 1
Individual APIs this provider publishes, each with its own machine-readable definition.
Very Good Security aliases API
Unique IDs that retain all the essential information about the data without compromising its security.
MCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
very-good-security-mcp.yml
MCP SERVEREvent Specifications 1
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Very Good Security Webhooks
ASYNCAPISecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes governing access to this provider's APIs.
Resources
Get Started 5
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll for all 7
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type