Web RPC Gateway

An abuse-resistant Solana RPC URL for dApp frontends — https://www-rpc.venum.dev/v1/<your-id>. Only real users in real browsers can call it; scrapers, bots, and scripts pointed at the same URL get denied.

Sometimes called the dApp Gateway: same product, different name. Distinct from the free Solana RPC at rpc.venum.dev, which is the right pick for server-side, scripted, or bot use.

When to use which

Use case	Endpoint
Browser-rendered dApp frontend	Web RPC (www-rpc.venum.dev/v1/<id>)
Backend service / cron / indexer	rpc.venum.dev (guide)
Local dev script, CI test	rpc.venum.dev
Wallet adapter inside a dApp page	Web RPC

The Web RPC is shaped for browser traffic and abuse-resistant by design — server-side clients are intentionally pointed at rpc.venum.dev instead.

Setup (30 seconds)

1. Sign in at app.venum.dev. Your dashboard shows your Web RPC URL.
2. Copy https://www-rpc.venum.dev/v1/<your-id>.
3. Replace your existing RPC URL in your dApp:

// before
const conn = new Connection('https://example-rpc.provider.com/<your-key>');

// after
const conn = new Connection('https://www-rpc.venum.dev/v1/abcdefghijkl');

That's the change. Every standard Solana JSON-RPC method works — read methods, sendTransaction, simulateTransaction, the lot.

What you get

• No secret in your client bundle. Your dApp's JS no longer ships an RPC API key. View Source on your site reveals nothing reusable.
• Abuse-resistant by design. The Web RPC only serves browser-originated traffic from real users. Scrapers pointing at the URL get a 403 instead of stealing your quota.
• Drop-in compatibility. Same JSON-RPC contract as any Solana RPC. No SDK changes, no special client code.

Plug your own RPC Paid tier

Secure your existing RPC against abuse and bots.

Already paying Triton, Helius, QuickNode, or running your own validator? Keep it. Forward your Web RPC to your own URL and we'll filter the traffic before it reaches your upstream — same browser-only enforcement, your bandwidth, your contract.

1. Upgrade to Starter or Pro at app.venum.dev.
2. Expand the Plug your own RPC card under your Web RPC URL.
3. Paste your provider URL (the one with the secret in it). We probe it once with getHealth to make sure it's reachable.
4. Save. Your dApp keeps calling https://www-rpc.venum.dev/v1/<your-id> — every request now lands on your upstream, after our abuse filters.

Your URL is stored server-side and never echoed back to any client — the dashboard only sees a connected flag, not the URL itself. Disconnect any time to fall back to our pooled upstream. Downgrading to Free pauses the forwarding (your URL stays saved); upgrading restores it.

Free during beta

The pooled Web RPC is enabled for every Venum account during beta — Free tier included. Plug-your-own-RPC and custom-domain support (rpc.yourdomain.com via CNAME) are paid-tier features.

Server-side access

If your code is running on a server, in CI, or anywhere outside a real browser, use rpc.venum.dev (it's free). The Web RPC will deny those requests on purpose so they don't drain your dApp's quota.

// server-side / bot
const conn = new Connection('https://rpc.venum.dev/?apiKey=<YOUR_VENUM_API_KEY>');

See the Solana RPC guide for the full reference.

FAQ

Does it support WebSocket subscriptions? Yes — accountSubscribe, slotSubscribe, etc. work the same way as on rpc.venum.dev. Browsers connect via wss://www-rpc.venum.dev/v1/<your-id> (web3.js derives this automatically from the HTTP URL).

My dApp also runs in a Node.js test environment. Will those requests work? No — point Node tests at rpc.venum.dev (free, allows server-side clients).

Can I rotate my Web RPC URL? Open a ticket at app.venum.dev and we'll issue a fresh <id>. The old one stops working immediately.

Does it cost anything? Free during beta. Pricing for production tiers (custom domain, higher rate limits, plug-your-own-RPC) is in flight.