Support different base URLs for /info, /exchange, and /ws endpoints

[smypmsa]

Problem

The SDK currently requires all endpoints (/info, /exchange, /ws) to be served from the same base URL. This makes it impossible to:

• Use different providers for different endpoints
• Use providers that only support subsets of endpoints
• Distribute endpoints across different infrastructure

Current limitation

# This forces /info, /exchange, and /ws to all use the same base URL
exchange = Exchange(wallet, base_url="https://api.hyperliquid.xyz")
# Internally creates: Info(base_url) which also creates WebSocket from base_url

Proposed solution

Add optional parameters to specify different base URLs for each endpoint:

exchange = Exchange(
    wallet,
    base_url="https://api.hyperliquid.xyz",     # Fallback default
    info_base_url="https://provider1.com",      # For /info
    exchange_base_url="https://provider2.com",  # For /exchange  
    ws_base_url="wss://provider3.com"         # For /ws
)

Benefits

• Flexible endpoint routing
• Backward compatible (all parameters optional)
• Enables partial provider support

Would you be open to a PR implementing this approach?

[traderben]

Why would you want to use different providers for different endpoints?
Can't you already create different objects for the different URLs that you might want to use? They aren't particularly tightly coupled

[smypmsa]

Why would you want to use different providers for different endpoints? Can't you already create different objects for the different URLs that you might want to use? They aren't particularly tightly coupled

As a workaround, yes, I can create different objects. However, Exchange creates its own Info instance and its methods depend on it.

[traderben]

I don't think this use case is sufficiently common and the work around seems good enough that I would be against adding the additional complexity to the Exchange constructor

[smypmsa]

@traderben Would you consider a dependency injection approach instead? Please take a look at my arguments below 😃

I understand the concern about complexity, but this isn't just about URL flexibility - it's about an architectural issue.

Current problem:

exchange = Exchange(wallet, base_url="https://api.hyperliquid.xyz")
# Exchange hardcodes: self.info = Info(base_url, True, meta, spot_meta, perp_dexs, timeout)

Exchange is actually tightly coupled to Info's concrete implementation. Hence, we have a few side effects:

1. Configuration: Info parameters are buried in Exchange constructor, not configurable
2. Extensibility: can't inject custom Info implementations
3. Responsibility: Exchange manages both trading operations AND Info lifecycle

Cleaner solution (optional parameter):

exchange = Exchange(wallet, info=custom_info)  # Dependency injection

This enables URL flexibility as a side benefit, but more importantly fixes the architectural coupling. The added complexity is minimal - one optional parameter that defaults to current behavior.

Btw, there are no RPC providers which support all endpoints. Most of them support /evm only. Here is a list of supported methods by Chainstack.