Getting Started
Start using BlazingNode in minutes
Create a trial, copy your Polygon RPC endpoint, add your API key, and test one real workload before replacing your current provider.
You do not need to migrate everything first. Test one failing Polygon workload, measure the result, then choose the plan or add-on that fits.
How the 7-day trial works
The trial is for workload validation. It lets you compare a real path that already matters to you before you commit to a plan.
Step 1
Create your account
Start from the trial flow and create your account using the existing signup path. The goal is not full migration. It is to get to one clean workload test quickly.
Step 2
Get your API key
API keys identify and protect the workload. Higher plans include more API keys, but the trial is enough to validate one real path first.
Step 3
Copy your Polygon RPC endpoint
BlazingNode gives you a standard Polygon RPC endpoint that works with normal JSON-RPC tooling. You do not need a custom SDK to begin testing.
Step 4
Make your first request
Use a standard JSON-RPC request. If you already use Polygon tooling, this should look familiar.
curl -X POST "https://YOUR_BLAZINGNODE_ENDPOINT" \
-H "Content-Type: application/json" \
-H "x-api-key: YOUR_API_KEY" \
--data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'Step 5
Test one real workload
Use the exact workflow that is failing now. That gives you a real before-and-after comparison instead of a synthetic test.
Step 6
Track usage and choose a plan
Compare monthly request volume, peak RPS, and trace usage before you choose a recurring plan.
Step 7
Add only what you need
- Extra 10M request packs for 35 USDC when monthly volume is the issue.
- Trace bundles when trace or debug calls are the real constraint.
- 72-hour burst passes for short events, launches, mints, claim windows, or traffic spikes.
- Upgrade when the higher usage repeats every month.
Burst is for short windows. Monthly request volume is for everyday usage. Trace capacity is for debugging and transaction analysis.
Need help?
Use the setup path that matches the question
Use docs for setup details, Ask Daniel where available on the site for guided help, and the Problem Solver when you need to narrow the actual failure pattern.
Internal links
Test BlazingNode on one real Polygon workload
Start with the workload that already causes 429s, timeouts, stale reads, trace issues, or pricing uncertainty. If it performs better, then choose the plan or add-on that fits your usage.