.env file.
How it works
What Gate handles
- Consent UI — hosted, branded consent page with your logo, colors, and ToS
- Bot detection — every signup is scored by Foil. Bots are blocked automatically.
- Agent tokens — Gate issues
agt_tokens that authenticate all post-signup interactions - Credential delivery — encrypted handoff of API keys to the CLI
- Dashboard login —
npx signup yourproduct loginopens your dashboard via magic link
What you handle
- Account creation — your webhook creates the account in your system
- API key issuance — your webhook returns whatever credentials the developer needs
- Dashboard auth — one route on your server to verify Gate’s magic link tokens
Relationship to Foil
Gate uses Foil’s browser agent detection to score every signup. You don’t need to integrate Foil separately — Gate handles it. However, the API keys Gate delivers can be for any product, not just Foil.What’s next
- Add Gate to your product — step-by-step integration guide
- CLI reference — all
npx signupcommands