Environment & Secrets

SENTi-radar requires several API keys and environment variables for full functionality. This guide covers setting up secrets for both frontend and backend.

Overview

SENTi-radar uses two types of environment variables:

Frontend (VITE_*)

Public variables embedded in the Vite build, accessible in the browser

Backend (Supabase Secrets)

Server-side secrets for edge functions, never exposed to the client

Never commit .env files to version control. Use .env.example as a template and add .env to .gitignore.

Required API Keys

Supabase

Required for: Database, authentication, edge functions

Create a Supabase project

Get your project credentials

Navigate to Project Settings → API:

Project URL: https://your-project.supabase.co
Anon/Public Key: Public key for client-side requests
Service Role Key: Secret key for server-side operations (never expose in frontend)

Scrape.do

Required for: Live X (Twitter) and Reddit data scraping

Create an account at scrape.do

Get your API token

Navigate to Dashboard → API Tokens and copy your token

Choose your plan

Free tier: 1,000 requests/month
Starter: 10,000 requests/month ($29)
Pro: 100,000 requests/month ($99)

Scrape.do is the primary data source for X/Twitter and Reddit. Without it, the app falls back to YouTube or algorithmic generation.

YouTube Data API v3

Required for: YouTube video comments (optional)

Go to Google Cloud Console

Visit console.cloud.google.com

Create a new project

Or select an existing project

Enable YouTube Data API v3

Navigate to APIs & Services → Library → Search for “YouTube Data API v3” → Enable

Create credentials

APIs & Services → Credentials → Create Credentials → API Key

Restrict your API key (recommended)

Edit API key → API restrictions → Select “YouTube Data API v3”

Quota: 10,000 units/day (free tier)

Gemini API

Required for: AI-powered sentiment analysis and summaries (optional)

Get Gemini API key

Visit ai.google.dev and sign up

Create an API key

Navigate to API Keys → Create API Key

Choose your model

SENTi-radar uses gemini-1.5-flash for fast, cost-effective analysis

Without Gemini, the app falls back to keyword-based sentiment analysis, which is less accurate but fully functional.

Groq (Optional)

Required for: Alternative LLM for summaries (optional)

Visit console.groq.com

Generate API key

Navigate to API Keys → Create new key

Frontend Environment Variables

Local Development

Create a .env file in the project root:

.env

# Supabase Configuration
VITE_SUPABASE_URL=https://owrqiailcuwlzxeekhms.supabase.co
VITE_SUPABASE_PUBLISHABLE_KEY=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...

# Scrape.do (required for live X/Reddit data)
VITE_SCRAPE_TOKEN=your-scrape-do-token

# YouTube Data API v3 (optional)
VITE_YOUTUBE_API_KEY=AIzaSyC...

# Gemini AI (optional, falls back to keyword analysis)
VITE_GEMINI_API_KEY=AIzaSyD...

# Groq (optional, secondary LLM)
VITE_GROQ_API_KEY=gsk_...

All frontend environment variables must be prefixed with VITE_ to be accessible in the browser via import.meta.env.VITE_*.

Production

Set environment variables in your hosting platform:

Vercel

Go to Project Settings → Environment Variables
Add each variable:
- Name: VITE_SUPABASE_URL
- Value: https://your-project.supabase.co
- Environment: Production
Redeploy to apply changes

Netlify

Go to Site Settings → Build & Deploy → Environment
Click “Add variable”
Add each VITE_* variable
Trigger a new deploy

Cloudflare Pages

Go to Settings → Environment Variables
Add Production variables
Redeploy the project

Lovable

Go to Project Settings → Environment Variables
Add each variable with its value
Deploy or redeploy to apply

Backend Secrets (Supabase)

Setting Secrets

Edge functions access secrets via Deno.env.get(). Set them using the Supabase CLI:

supabase secrets set SCRAPE_DO_TOKEN=your-token-here

Listing Secrets

View configured secrets (values are hidden):

supabase secrets list

Output:

SCRAPE_DO_TOKEN
YOUTUBE_API_KEY
GEMINI_API_KEY
SUPABASE_URL
SUPABASE_SERVICE_ROLE_KEY

Unsetting Secrets

Remove a secret:

supabase secrets unset GEMINI_API_KEY

Required Secrets by Function

analyze-sentiment

Required:

SUPABASE_URL
SUPABASE_SERVICE_ROLE_KEY

Optional:

GEMINI_API_KEY (falls back to keyword-based analysis)

fetch-twitter

Required:

SUPABASE_URL
SUPABASE_SERVICE_ROLE_KEY

Optional (in priority order):

SCRAPE_DO_TOKEN (primary data source)
PARALLEL_API_KEY (fallback)
YOUTUBE_API_KEY (fallback)

fetch-reddit

Required:

SUPABASE_URL
SUPABASE_SERVICE_ROLE_KEY

Optional:

SCRAPE_DO_TOKEN (for Reddit JSON API)

fetch-youtube

Required:

SUPABASE_URL
SUPABASE_SERVICE_ROLE_KEY

Optional:

YOUTUBE_API_KEY

analyze-topic

Required:

SUPABASE_URL
SUPABASE_SERVICE_ROLE_KEY

Note: Inherits requirements from all called functions

generate-insights

Required:

SUPABASE_URL
SUPABASE_SERVICE_ROLE_KEY

Optional:

GEMINI_API_KEY

scheduled-monitor

Required:

SUPABASE_URL
SUPABASE_SERVICE_ROLE_KEY

Environment Variable Reference

Frontend Variables

Variable	Required	Description	Example
`VITE_SUPABASE_URL`	✅ Yes	Supabase project URL	`https://abc123.supabase.co`
`VITE_SUPABASE_PUBLISHABLE_KEY`	✅ Yes	Supabase anon/public key	`eyJhbGciOiJIUzI1NiIs...`
`VITE_SCRAPE_TOKEN`	⭐ Recommended	Scrape.do API token for X/Reddit	`scrape_do_abc123...`
`VITE_YOUTUBE_API_KEY`	❌ Optional	YouTube Data API v3 key	`AIzaSyC...`
`VITE_GEMINI_API_KEY`	❌ Optional	Gemini AI API key	`AIzaSyD...`
`VITE_GROQ_API_KEY`	❌ Optional	Groq API key	`gsk_...`

Backend Secrets

Secret	Required	Description	Example
`SUPABASE_URL`	✅ Yes	Supabase project URL	`https://abc123.supabase.co`
`SUPABASE_SERVICE_ROLE_KEY`	✅ Yes	Supabase service role key (never expose publicly)	`eyJhbGciOiJIUzI1NiIs...`
`SCRAPE_DO_TOKEN`	⭐ Recommended	Scrape.do API token	`scrape_do_abc123...`
`YOUTUBE_API_KEY`	❌ Optional	YouTube Data API v3 key	`AIzaSyC...`
`GEMINI_API_KEY`	❌ Optional	Gemini AI API key	`AIzaSyD...`
`PARALLEL_API_KEY`	❌ Optional	Parallel.ai API key (fallback)	`pk_...`

Validation & Testing

Test Frontend Environment

Open browser console:

console.log('Supabase URL:', import.meta.env.VITE_SUPABASE_URL);
console.log('Has Scrape Token:', !!import.meta.env.VITE_SCRAPE_TOKEN);

Expected output:

Supabase URL: https://your-project.supabase.co
Has Scrape Token: true

Test Edge Function Secrets

Deploy a test function:

test-secrets.ts

import { serve } from "https://deno.land/[email protected]/http/server.ts";

serve(() => {
  const secrets = {
    hasSupabaseUrl: !!Deno.env.get("SUPABASE_URL"),
    hasServiceRoleKey: !!Deno.env.get("SUPABASE_SERVICE_ROLE_KEY"),
    hasScrapeToken: !!Deno.env.get("SCRAPE_DO_TOKEN"),
    hasGeminiKey: !!Deno.env.get("GEMINI_API_KEY"),
  };
  
  return new Response(JSON.stringify(secrets, null, 2), {
    headers: { "Content-Type": "application/json" },
  });
});

Deploy and test:

supabase functions deploy test-secrets
curl https://your-project.supabase.co/functions/v1/test-secrets

Security Best Practices

Never commit secrets

Add to .gitignore:

.env
.env.local
.env.production
.env.secrets

Rotate keys regularly

Update API keys monthly and after any security incidents

Use separate keys for dev/prod

Create separate API keys for development and production environments

Restrict API key permissions

Enable API restrictions in Google Cloud Console, Supabase RLS, etc.

Monitor API usage

Set up alerts for unusual usage patterns in:

Supabase Dashboard
Scrape.do Dashboard
Google Cloud Console

Troubleshooting

Environment variables are undefined

Symptoms: import.meta.env.VITE_SUPABASE_URL returns undefinedCauses:

Variable not prefixed with VITE_
.env file not in project root
Build cache not cleared

Solutions:

# Ensure VITE_ prefix
VITE_SUPABASE_URL=https://...

# Clear cache and rebuild
rm -rf dist node_modules/.vite
npm run build

Supabase secrets not accessible in edge functions

Symptoms: Deno.env.get("SCRAPE_DO_TOKEN") returns undefined or empty stringCauses:

Secrets not set via supabase secrets set
Wrong project linked

Solutions:

# Verify linked project
supabase status

# List secrets
supabase secrets list

# Set missing secrets
supabase secrets set SCRAPE_DO_TOKEN=your-token

API key quota exceeded

Symptoms: 429 errors from Scrape.do, YouTube, or GeminiSolutions:

Check usage in provider dashboard
Upgrade to higher tier
Implement caching to reduce API calls
Use fallback mechanisms (app already includes these)

Invalid API key errors

Symptoms: 401/403 errors from external APIsSolutions:

Verify API key is correct (no extra spaces)
Check API key hasn’t expired
Ensure API is enabled (e.g., YouTube Data API v3 in Google Cloud)
Test API key directly with curl:

# Test Scrape.do
curl "https://api.scrape.do?token=YOUR_TOKEN&url=https://example.com"

# Test YouTube API
curl "https://www.googleapis.com/youtube/v3/search?part=snippet&q=test&key=YOUR_KEY"

Deployment

Environment & Secrets

Overview

Frontend (VITE_*)

Backend (Supabase Secrets)

Required API Keys

Supabase

Scrape.do

YouTube Data API v3

Gemini API

Groq (Optional)

Frontend Environment Variables

Local Development

Production

Backend Secrets (Supabase)

Setting Secrets

Listing Secrets

Unsetting Secrets

Required Secrets by Function

Environment Variable Reference

Frontend Variables

Backend Secrets

Validation & Testing

Test Frontend Environment

Test Edge Function Secrets

Security Best Practices

Troubleshooting

Next Steps

Deploy Frontend

Deploy Edge Functions

Build docs developers (and LLMs) love

Deployment

​Overview

Frontend (VITE_*)

Backend (Supabase Secrets)

​Required API Keys

​Supabase

​Scrape.do

​YouTube Data API v3

​Gemini API

​Groq (Optional)

​Frontend Environment Variables

​Local Development

​Production

​Backend Secrets (Supabase)

​Setting Secrets

​Listing Secrets

​Unsetting Secrets

​Required Secrets by Function

​Environment Variable Reference

​Frontend Variables

​Backend Secrets

​Validation & Testing

​Test Frontend Environment

​Test Edge Function Secrets

​Security Best Practices

​Troubleshooting

​Next Steps

Deploy Frontend

Deploy Edge Functions

Build docs developers (and LLMs) love

Overview

Required API Keys

Supabase

Scrape.do

YouTube Data API v3

Gemini API

Groq (Optional)

Frontend Environment Variables

Local Development

Production

Backend Secrets (Supabase)

Setting Secrets

Listing Secrets

Unsetting Secrets

Required Secrets by Function

Environment Variable Reference

Frontend Variables

Backend Secrets

Validation & Testing

Test Frontend Environment

Test Edge Function Secrets

Security Best Practices

Troubleshooting

Next Steps