Redeploy the web service from your workshop-demo fork after you push the dispatch changes. Create the second service in the next page.
If you already deployed the baseline in Baseline: Deploy on Render, use the same Render service: push to your fork, let auto-deploy run (or trigger Manual Deploy), and update environment variables below.
After redeploy, the UI loads, but research runs fail until you connect the second service and wire its slug env var in the next step. That is expected.
Environment variables
On your existing web service in the Dashboard:
| Variable | Value |
|---|---|
RENDER_API_KEY | API key |
ANTHROPIC_API_KEY | Claude synthesis (still on web) |
Set EXA_API_KEY on the second service when Exa calls run there.
You can remove EXA_API_KEY from the web service if it is still set from the baseline deploy.
Redeploy
- Confirm your latest commit (dispatch + SDK on server) is on your fork’s default branch.
- In the Dashboard, open your web service → Manual Deploy → deploy latest commit, or wait for auto-deploy.
- Save your web service URL (same as before unless you recreated the service).
Reference Blueprint: render.yaml in the upstream repo (your fork should match).
What you learned
- One repo: your workshop-demo fork for web code and task-run code
- Web service needs RENDER_API_KEY and ANTHROPIC_API_KEY after redeploy
- EXA_API_KEY goes on the second service when you create it
- Research runs fail until you wire the second service slug