RelayGuard

Quickstart

Get from zero to your first eth_blockNumber in about 15 minutes.

1. Create an account

Sign up at app.0xrelayguard.com/register. This creates a workspace and production environment. Onboarding defaults to Ethereum mainnet — you can pick a different first network from the dropdown if you prefer.

2. Add RPC providers

In the onboarding wizard, add at least two providers for your chosen network (e.g. Alchemy + Infura on Ethereum, or your Base RPC URLs). Use endpoints you are authorized to route traffic through. Provider URLs are encrypted at rest and never shown again after save.

Assign different independence groups if you plan to use Security Mode later — quorum requires providers that do not share the same upstream.

After onboarding, add more networks anytime from Networks in the dashboard. Many EVM mainnets and testnets are supported — see the full list with slugs on the Networks page. Each network has its own providers and Security Mode settings; one API key works across all configured networks.

3. Create an API key

Generate a key in the dashboard. Copy the plug-and-play URL from the overview or API keys page. Keys use the rg_live_ prefix.

4. Call the gateway

Replace :chain with your network slug (e.g. ethereum, base):

curl -s -X POST https://gateway.0xrelayguard.com/rpc/ethereum \
  -H "Authorization: Bearer rg_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

Or with Foundry Cast using a tool URL:

cast block-number --rpc-url "https://gateway.0xrelayguard.com/rpc/ethereum?key=rg_live_YOUR_KEY"

Expected: HTTP 200 with a hex block number in result.

5. Check provider health

The dashboard Overview shows live provider health for the network selected in the header. Authenticated GET /status also returns per-chain health for your workspace. See the API reference for details.

6. (Optional) Set contract-level policy

Once Security Mode is enabled, you can import contract ABIs from Etherscan and configure quorum or deny rules per function. Go to Security Mode → Contract policy → Import contracts, enter a contract address, and the ABI is fetched automatically. Then set per-function policy in the expanded function table.

See Security Mode for the full policy reference.

Troubleshooting

  • 503 no providers configured — add at least one provider for that network in the dashboard before sending traffic.
  • 401 unauthorized — check the Bearer token and that the key is not revoked.
  • 429 rate limited — per-key limits apply; contact us if you need higher caps during beta.