What is routing optimization?

Routing optimization intelligently selects the best blockchain data provider for each request based on real-time analysis of cost, reliability, and performance. Instead of using a fixed provider, Uniblock dynamically routes to the optimal provider for current conditions. Use routing optimization when you need:

Lowest possible costs without sacrificing reliability
Automatic adaptation to provider performance changes
Optimal provider selection for different endpoint types
Data-driven routing decisions

Routing optimization is available on Growth plans and above. View pricing →

How it works

Uniblock continuously monitors provider performance and makes routing decisions based on:

Cost analysis - Current pricing for each provider
Reliability tracking - Success rates, uptime, error rates
Performance metrics - Response times, throughput
Historical data - Provider performance over time
Endpoint-specific optimization - Different providers excel at different endpoints

Request → Analyze providers
       → Provider A: $0.001/call, 99.9% uptime
       → Provider B: $0.002/call, 99.95% uptime
       → Provider C: $0.0015/call, 99.5% uptime
       → Route to Provider A (best cost/reliability ratio)

Optimization factors

Cost efficiency

Uniblock tracks real-time provider pricing:

Provider	Cost per call	Monthly cost (1M calls)
Covalent	$0.0008	$800
Moralis	$0.0012	$1,200
Alchemy	$0.0015	$1,500
QuickNode	$0.0020	$2,000

Routing decision: Route to Covalent for maximum cost savings.

Reliability

Success rates and uptime are continuously monitored:

Provider	Uptime	Success rate	Error rate
Alchemy	99.95%	99.8%	0.2%
Infura	99.90%	99.5%	0.5%
QuickNode	99.85%	99.3%	0.7%
Moralis	99.80%	99.0%	1.0%

Routing decision: Balance cost with reliability based on your preferences.

Performance

Response times and throughput are tracked:

Provider	Avg response time	P95 response time	Throughput
QuickNode	120ms	250ms	1000 req/s
Alchemy	150ms	300ms	800 req/s
Infura	180ms	350ms	600 req/s
Moralis	200ms	400ms	500 req/s

Routing decision: Route to QuickNode for latency-sensitive operations.

Endpoint-specific optimization

Different providers excel at different endpoint types:

Endpoint type	Best provider	Reason
Token balances	Covalent	Lowest cost, high reliability
NFT metadata	Alchemy	Best NFT data quality
Transaction history	Moralis	Comprehensive historical data
Real-time events	QuickNode	Lowest latency
Token prices	CoinGecko	Most accurate pricing

Real-world examples

Example 1: Cost optimization for token balances

Scenario: Your app makes 1 million token balance requests per month. Without optimization:

All requests → Alchemy ($0.0015/call)
Monthly cost: $1,500

With optimization:

Requests → Covalent ($0.0008/call, 99.9% uptime)
Monthly cost: $800
Savings: $700/month (47% reduction)

Request:

curl --location \
'https://api.uniblock.dev/uni/v1/token/balances?chainId=1&address=0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb' \
--header 'x-api-key: YOUR_API_KEY'

Outcome: Automatic routing to Covalent saves $700/month without code changes.

Example 2: Reliability optimization for critical operations

Scenario: Your trading platform requires maximum reliability for price data. Optimization preference: Reliability > Cost Routing decision:

Provider A: $0.001/call, 99.5% uptime ❌
Provider B: $0.002/call, 99.95% uptime ✅ (selected)
Provider C: $0.0015/call, 99.8% uptime ❌

Request:

curl --location \
'https://api.uniblock.dev/uni/v1/token/price?chainId=1&tokenAddress=0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2' \
--header 'x-api-key: YOUR_API_KEY'

Outcome: Routes to most reliable provider despite higher cost.

Example 3: Performance optimization for real-time data

Scenario: Your app displays real-time NFT sales and needs low latency. Optimization preference: Performance > Cost Routing decision:

Provider A: 200ms avg, $0.001/call ❌
Provider B: 120ms avg, $0.002/call ✅ (selected)
Provider C: 180ms avg, $0.0015/call ❌

Request:

curl --location \
'https://api.uniblock.dev/uni/v1/nft/transfers?chainId=1&collectionAddress=0xBC4CA0EdA7647A8aB7C2061c2E118A18a936f13D' \
--header 'x-api-key: YOUR_API_KEY'

Outcome: Routes to fastest provider for best user experience.

Example 4: Dynamic adaptation to provider issues

Scenario: Your primary provider experiences performance degradation. Initial state:

Provider A: $0.001/call, 99.9% uptime ✅ (primary)
Provider B: $0.002/call, 99.95% uptime

After degradation:

Provider A: $0.001/call, 95% uptime ❌ (degraded)
Provider B: $0.002/call, 99.95% uptime ✅ (now primary)

Outcome: Automatically switches to Provider B until Provider A recovers.

Configuration

Configure routing optimization in the Uniblock dashboard:

Optimization strategy

Choose what to optimize for:

Strategy	Description	Use case
Balanced (default)	Optimize cost and reliability equally	Most applications
Cost-optimized	Prioritize lowest cost	Budget-conscious apps
Reliability-optimized	Prioritize highest uptime	Critical operations
Performance-optimized	Prioritize lowest latency	Real-time applications

Minimum reliability threshold

Set minimum acceptable reliability:

Threshold	Description	Use case
95%	Allow less reliable providers	Non-critical data
99% (default)	Standard reliability	Most applications
99.9%	High reliability	Financial applications
99.95%	Maximum reliability	Critical operations

Cost ceiling

Set maximum acceptable cost per call:

Ceiling	Description	Use case
$0.001	Very low cost	High-volume, low-margin
$0.002 (default)	Moderate cost	Standard applications
$0.005	Higher cost acceptable	Premium features
Unlimited	Cost not a factor	Enterprise applications

Endpoint-specific rules

Configure different optimization for different endpoints:

Example configuration

{
  "token/balances": {
    "strategy": "cost-optimized",
    "minReliability": 99.0
  },
  "token/price": {
    "strategy": "reliability-optimized",
    "minReliability": 99.9
  },
  "nft/transfers": {
    "strategy": "performance-optimized",
    "maxLatency": 200
  }
}

Monitoring and analytics

Track routing optimization in the Uniblock dashboard:

Cost savings

Total cost - Current month spending
Projected savings - Compared to fixed provider
Cost per endpoint - Breakdown by endpoint type
Provider cost distribution - Which providers are used most

Provider distribution

Request distribution - Percentage of requests per provider
Cost distribution - Percentage of costs per provider
Reliability by provider - Success rates for each provider
Performance by provider - Average latency for each provider

Optimization effectiveness

Routing decisions - Why each provider was selected
Optimization score - How well routing is optimized
Missed opportunities - Times when better routing was possible
Adaptation speed - How quickly routing adapts to changes

Key benefits

Cost efficiency

Save 30-50% on provider costs through intelligent routing.

Automatic adaptation

Routing adjusts automatically to provider performance changes.

Reliability assurance

Never sacrifice reliability for cost savings.

Performance optimization

Route to fastest providers for time-sensitive operations.

Best practices

Set appropriate thresholds - Balance cost savings with reliability requirements. Don’t set thresholds too aggressive.

Monitor provider distribution - Ensure routing is actually optimizing. High concentration on one provider may indicate issues.

Use endpoint-specific rules - Different endpoints have different requirements. Optimize each category separately.

Review optimization regularly - Provider pricing and performance change. Review settings quarterly.

Comparison: Fixed vs. optimized routing

Aspect	Fixed routing	Optimized routing
Provider selection	Manual	Automatic
Cost	Fixed	Optimized (30-50% savings)
Adaptation	Manual updates	Real-time adaptation
Reliability	Single provider risk	Multi-provider resilience
Performance	Fixed	Optimized per endpoint
Maintenance	High	Low

Next steps

Backup providers

Learn how routing optimization works with backup providers.

Auto-retry

Understand how retries work with optimized routing.

Data consensus

Combine optimization with data verification.

Dashboard

Configure optimization settings and monitor savings.

Common pitfalls

Too aggressive cost optimization - Setting cost thresholds too low may exclude reliable providers. Balance cost with reliability.

Ignoring endpoint-specific needs - Not all endpoints have the same requirements. Configure rules per endpoint type.

Not monitoring provider distribution - Routing concentrated on one provider indicates optimization isn’t working. Investigate and adjust.

Forgetting to review settings - Provider landscape changes. Review optimization settings quarterly to ensure optimal routing.

🏁 Welcome

🚀 Getting Started

🌐 Uniblock

Routing optimization

What is routing optimization?

How it works

Optimization factors

Cost efficiency

Reliability

Performance

Endpoint-specific optimization

Real-world examples

Example 1: Cost optimization for token balances

Example 2: Reliability optimization for critical operations

Example 3: Performance optimization for real-time data

Example 4: Dynamic adaptation to provider issues

Configuration

Optimization strategy

Minimum reliability threshold

Cost ceiling

Endpoint-specific rules

Monitoring and analytics

Cost savings

Provider distribution

Optimization effectiveness

Key benefits

Cost efficiency

Automatic adaptation

Reliability assurance

Performance optimization

Best practices

Comparison: Fixed vs. optimized routing

Next steps

Backup providers

Auto-retry

Data consensus

Dashboard

Common pitfalls

🏁 Welcome

🚀 Getting Started

🌐 Uniblock

​What is routing optimization?

​How it works

​Optimization factors

​Cost efficiency

​Reliability

​Performance

​Endpoint-specific optimization

​Real-world examples

​Example 1: Cost optimization for token balances

​Example 2: Reliability optimization for critical operations

​Example 3: Performance optimization for real-time data

​Example 4: Dynamic adaptation to provider issues

​Configuration

​Optimization strategy

​Minimum reliability threshold

​Cost ceiling

​Endpoint-specific rules

​Monitoring and analytics

​Cost savings

​Provider distribution

​Optimization effectiveness

​Key benefits

Cost efficiency

Automatic adaptation

Reliability assurance

Performance optimization

​Best practices

​Comparison: Fixed vs. optimized routing

​Next steps

Backup providers

Auto-retry

Data consensus

Dashboard

​Common pitfalls

What is routing optimization?

How it works

Optimization factors

Cost efficiency

Reliability

Performance

Endpoint-specific optimization

Real-world examples

Example 1: Cost optimization for token balances

Example 2: Reliability optimization for critical operations

Example 3: Performance optimization for real-time data

Example 4: Dynamic adaptation to provider issues

Configuration

Optimization strategy

Minimum reliability threshold

Cost ceiling

Endpoint-specific rules

Monitoring and analytics

Cost savings

Provider distribution

Optimization effectiveness

Key benefits

Best practices

Comparison: Fixed vs. optimized routing

Next steps

Common pitfalls