The repo auto-detects your deployment preference:
| If you... | Then... |
|---|---|
Add OPENAI_API_KEY secret to GitHub |
→ GitHub Pages deploys automatically |
| Don't add the secret | → Workflow skips, use Vercel instead |
Best for: Free hosting, fully automatic
-
Add your OpenAI API key:
- Go to repo Settings → Secrets → Actions → New secret
- Name:
OPENAI_API_KEY - Value: Your OpenAI API key
-
Enable GitHub Pages:
- Go to repo Settings → Pages
- Source:
gh-pagesbranch - Click Save
That's it! Every push to main will:
- Translate agents to 18 languages
- Build the index
- Deploy to GitHub Pages
# Update CNAME file with your domain
echo "agents.yourdomain.com" > CNAME
git add CNAME && git commit -m "Set custom domain" && git pushThen add DNS: CNAME record pointing to [username].github.io
Best for: CORS control, analytics, rate limiting
- Go to vercel.com/new
- Import your repository
- Configure:
Setting Value Framework Other Build Command bun run buildOutput Directory public - Add environment variable:
OPENAI_API_KEY - Deploy!
- ✅ CORS control (restrict which sites can access your agents)
- ✅ Analytics and usage metrics
- ✅ Rate limiting
- ✅ Faster global CDN
The included vercel.json has sensible defaults for CORS and caching.
| Feature | GitHub Pages | Vercel |
|---|---|---|
| Cost | Free | Free tier |
| Setup | Add 1 secret | Import + configure |
| CORS Control | ❌ | ✅ |
| Analytics | ❌ | ✅ |
| Custom Domain | ✅ | ✅ |
| Auto-deploy | ✅ | ✅ |
Q: What if I don't add the OpenAI secret? A: The GitHub Action will skip gracefully and show instructions for Vercel.
Q: Can I use both? A: Yes, but they'll serve the same content. Pick one.
Q: How do I switch from GitHub Pages to Vercel? A: Just import to Vercel. Optionally remove the secret from GitHub to stop those builds.
Q: What's the OPENAI_API_KEY for? A: Translating your agents to 18 languages automatically.