The Problem: Perplexity Credits Get Stolen Fast
Perplexity's Sonar models are designed for real-time, web-grounded answers — and that means your API key is high value. If you call Perplexity directly from React, Next.js, or Vanilla JS, your key can leak through DevTools, build artifacts, or network logs.
Environment variables do NOT secure frontend builds. Serverless still needs CORS setup, secrets management, throttling, and ongoing maintenance.
If your key leaks, your credits get burned.
What Happens When Your Perplexity Key Leaks?
- Unauthorized usage that drains credits
- Abuse from scraped keys
- Unexpected spend spikes
- Production downtime
- Broken user experience during throttling/limits
The Solution: The Salting Layer
Instead of calling Perplexity directly, you call your secure bridge:https://api.salting.io/r/salting-io-bridge-uuid
Your real Perplexity key stays encrypted inside Salting. We handle:
- Secret key vaulting
- AES-256 request encryption
- CORS enforcement
- IP & rate limiting
- Abuse protection
You get backend-level security without running a backend.
How It Works
- Add your Perplexity API key to your Salting dashboard.
- Generate a private Bridge URL.
- Lock usage to your domain (optional but recommended).
- Replace the Perplexity base URL in your frontend.
- Deploy instantly.
No Node.js proxy. No CORS debugging. No credit theft.
Salting vs Traditional Backend Setup
🚧 Traditional Backend Proxy
- Requires Node.js / Go server
- Manual CORS configuration
- Secret key stored in your infrastructure
- Custom rate limiting implementation
- Ongoing maintenance + monitoring
- More surface area for leaks
☁ Serverless Function
- Cold starts possible
- CORS handling still required
- Secrets + deployment pipeline complexity
- Scaling cost spikes under load
- Still infrastructure to maintain
⚡ Salting Layer (Recommended)
- No server required
- Encrypted key vault
- Built-in CORS enforcement
- Integrated rate limiting
- Abuse protection by default
- Deploy in under 2 minutes
What Can You Build?
- AI search experiences with citations
- News & research assistants
- Market intelligence dashboards
- Competitive analysis tools
- Fact-checking & verification UIs
- Internal knowledge utilities
Perfect for React, Vue, Angular, static sites, and serverless apps.
Frequently Asked Questions
Is Salting a proxy?
Technically yes — but optimized for security, speed, and zero infrastructure management.
Does this replace my backend?
If your backend exists mainly to hide keys and control usage, yes.
Can I keep usage locked to my domain?
Yes. Use domain locking + CORS enforcement to prevent unauthorized origins.
Does Salting add latency?
Minimal edge overhead (typically sub-30ms).
Can I use different Sonar models?
Yes. Salting forwards requests transparently.
Stop Burning Credits to Key Leaks
If your frontend can see your Perplexity key, attackers can too. Secure it in minutes and ship web-grounded AI safely.