Vault
Creator Settings
Connect wallet auth, store provider keys in Supabase, and keep live Zap runs user-owned.
Thirdweb Wallet Auth
Use a Supabase access token from the wallet proof flow.
Wallet proof proxy
Sign a Zap wallet proof, or paste the JSON payload produced by your Thirdweb wallet signature flow.
Link a chat channel
Generate a one-use code, then send /link CODE to Zap in Slack, Telegram, or iMessage. Codes expire after five minutes.
Provider Secrets
Stored encrypted in Supabase. Browser reads are masked.
aws_access_key_id
not stored
aws_region
not stored
aws_role_arn
not stored
aws_s3_output_uri
not stored
aws_secret_access_key
not stored
aws_session_token
not stored
gmi_api_key
not stored
fal_key
not stored
runware_key
not stored
prodia_token
not stored
openrouter_key
not stored
ai_gateway_api_key
not stored
vertex_api_key
not stored
vertex_location
not stored
vertex_output_gcs_uri
not stored
vertex_project
not stored
vertex_service_account
not stored