AI agent instructions
AI agent instructions
Prerequisites
- A VGS vault holding the data to fill, and its vault ID (it starts with
tnt). - Aliases the site’s form accepts. For card numbers, the
FPE_6_T_4alias format keeps the card’s format and Luhn check (see operations). - The hostnames that receive the data: the payment provider or iframe host, not only the merchant’s site.
Configure VGS
- Create an outbound route for each host you will list in
hosts, with that host as its upstream host. VGS answers requests to a host with no matching route with HTTP 400 (FAQ). - Reveal aliases in requests. On each route, add a filter in the request phase with a reveal operation that selects the field where the agent types the alias: the form field name for form posts, a JSONPath for JSON bodies, or a regex (selecting data elements).
- Redact real values in responses. On each route, add a filter in the response phase with a redact operation that selects every field where the site can return a real value. VGS then stores the value and returns an alias instead, as in its card issuing guide. A response that matches no filter passes through unchanged, so check what each listed host returns. See why this matters.
- Get outbound access credentials under your vault’s settings (access credentials). VGS shows the password only once, when you generate the credentials.
- Download the VGS certificate for your environment (sandbox or live) from the Code snippets section of the VGS dashboard.
Map VGS’s values to the secret entry
The access credentials do not change per session, so you can save the configuration in the console with the VGS preset and start sessions with
{"type": "secret"}.