Skip to main content
Every variable a host developer sets. Keys are credentials; config selects. VENDO_API_KEY is the one variable that fills an adapter slot you left unset. Every other key here authenticates something you already chose in createVendo. Two of these are URLs that get swapped: VENDO_BASE_URL is your app’s public URL, VENDO_CONSOLE_URL is the Vendo console’s.

Host process

An unset NODE_ENV stores secrets in plaintext. On the default local store, the plaintext allowance is NODE_ENV !== "production" — so unset, or any value other than production, allows it. The only signal is one console.warn the first time a secret is written.Set both on any real deployment:
.env
Either one alone is enough to stop plaintext: with the key set, secrets are encrypted whatever NODE_ENV says; with NODE_ENV=production and no key, the store refuses to write a secret rather than writing it in the clear. Vendo Cloud’s hosted store is unaffected — this is the local store only.

Auth presets

Each preset reads its vendor’s own variables rather than a Vendo-named one.
vendo init writes the local ones. VENDO_API_KEY and VENDO_SERVICE_KEY land in .env.local. Every other value is yours to set, production ones on your deploy platform.
Vendo also reads internal test seams and harness markers. They are not contract and can change without notice.