Jupiter - missing API key is reported as no route for BASE-QOUTE pair

[rapcmia]

Describe the bug

While an LP rebalancer was fetching the SOL-USDC price through the solana-mainnet-beta network connector, Hummingbot logged NO_ROUTE_FOUND with the message No route found for SOL -> USDC (ExactIn). The error also contained an upstream HTTP 401 response.

2026-08-27 19:06:52,941 - 3519877 - hummingbot.core.trading_core - INFO - Markets recorder initialized with database: conf_v2_with_controllers_1
2026-08-27 19:06:52,974 - 3519877 - hummingbot.core.trading_core - INFO - Creating the clock with tick size: 1.0
2026-08-27 19:06:52,974 - 3519877 - hummingbot.core.trading_core - INFO - Clock started successfully
2026-08-27 19:06:52,974 - 3519877 - hummingbot.core.trading_core - INFO - 'v2_with_controllers' strategy execution started.
2026-08-27 19:06:52,974 - 3519877 - hummingbot.core.trading_core - INFO - Strategy v2_with_controllers started successfully
2026-08-27 19:06:52,996 - 3519877 - Gateway - INFO - Network status has changed to NetworkStatus.CONNECTED. Starting networking...
2026-08-27 19:06:53,017 - 3519877 - hummingbot.strategy.strategy_v2_base - WARNING - solana-mainnet-beta is not ready. Please wait...
2026-08-27 19:06:53,052 - 3519877 - Gateway - INFO - Swap provider for solana-mainnet-beta: jupiter/router
2026-08-27 19:06:53,155 - 3519877 - hummingbot.data_feed.market_data_provider - ERROR - Error fetching price for SOL-USDC: Gateway error: No route found for SOL -> USDC (ExactIn). Request failed with status 401 (HttpError) [code: NO_ROUTE_FOUND]
2026-08-27 19:06:53,195 - 3519877 - Gateway - INFO - Set native currency to: SOL for solana-mainnet-beta
2026-08-27 19:06:53,413 - 3519877 - hummingbot.core.rate_oracle.rate_oracle - INFO - Network status has changed to NetworkStatus.CONNECTED. Starting networking...
2026-08-27 19:06:53,703 - 3519877 - Gateway - INFO - Set native currency to: SOL for solana-mainnet-beta

The network uses jupiter/router as its swap provider. When no Jupiter API key is configured, Gateway attempts to use the keyless Jupiter endpoint, but the resulting authorization failure is shown as a missing swap route. This makes users investigate liquidity or token support instead of explaining that a Jupiter API key is required. Adding a valid Jupiter API key and restarting Gateway allowed the price request to work again ✅

Steps to reproduce

1. Configure solana-mainnet-beta to use jupiter/router as its swap provider.
2. Leave the Jupiter API key unset.
3. Start a controller that requests a SOL-USDC price through the network connector.
4. Observe a NO_ROUTE_FOUND error that also contains an upstream HTTP 401 response.
5. Add a valid Jupiter API key and restart Gateway then confirm the price request succeeds instead of reporting a missing route.

Release version

dev-2.17

Type of installation

Source

Attach required files

n/a