Read blueprint/20-entrevista.md, segment 3 · Q10 to Q12 · from /conectar, and follow it. There
are the three questions —the provider, its credentials, and what else to connect— and step 13, which
closes by noting in .wca-estado.json which variables were set and which were not.
The details of each provider —the signature, the routes, and its variables— are in
blueprint/31-proveedores.md: open the section for meta, zernio or demo when segment 3
sends you there. Do not mix the variables of one with those of the other.
demo does not ask for credentials. It is not a fake transport: it replays recorded deliveries, the same
raw bytes and the same signature header. It is useful for testing the whole path before connecting.
The values are written by whoever installs, in .env. You name the variable, say where it is
obtained from, and verify that it is set. You never print it or copy it to another file.
Changing providers changes signature verification. Run /revisar afterward.