feat / gateway update pool API to use chain+network organization

[fengtality]

Summary

• Add gateway_base_url attribute to AccountsService
• Simplify CLMMPoolListItem to match Gateway fetch-pools response format
• Update CLMMPoolListResponse to use pageSize instead of limit
• Remove Query aliases to match hummingbot-api-client parameter names
• Add GET/POST /gateway/apiKeys endpoints for RPC provider API key management
• Add get_api_keys() and update_api_keys() methods to gateway_client
• Add UpdateApiKeysRequest model

New Endpoints

GET /gateway/apiKeys

Returns all configured API keys from Gateway:

{
  "helius": "46951ec2-16af-4fc0-a5df-970b0eb925b7",
  "infura": "920646320ec3463fa1b5235be9fa48d3",
  "coingecko": "CG-Rw786jTpNmV1MvRrqpDAHR6r",
  "etherscan": ""
}

POST /gateway/apiKeys

Update API keys in Gateway configuration:

{
  "api_keys": {
    "helius": "new-api-key",
    "infura": "another-key"
  }
}

Response:

{
  "success": true,
  "message": "Updated 2 API key(s). Restart Gateway for changes to take effect.",
  "restart_required": true,
  "restart_endpoint": "POST /gateway/restart",
  "updated_keys": ["helius", "infura"]
}

Related PRs

• hummingbot: feat / gateway update pool API to use chain+network organization hummingbot#8206
• gateway: feat / organize pool templates by network instead of connector gateway#630
• hummingbot-api-client: feat: add network pool endpoints and executor logs hummingbot-api-client#17
• condor: feat / Network-first pools management and default networks feature condor#76

Test plan

• Manual testing with pool listing endpoints
• Test GET /gateway/apiKeys returns current keys
• Test POST /gateway/apiKeys updates keys correctly

🤖 Generated with Claude Code

[rapcmia]

• Build local hummingbot lib from hummingbot/hummingbot#8206
• Build local docker images for this PR and hummingbot/gateway#630
• Start hummingbot-api via make deploy ok
• Tested GET and POST /gateway/apiKeys on port 8000 ok
  • GET returns current keys.
  • POST successfully updated helius and infura.
  • Values are consistent with ./gateway-files/conf/apiKey.yml.
• Manual pool-listing tests on solana-mainnet-beta for meteora, orca, and raydium (CLMM context) ok
  • Meteora and Orca address lookup works via GET /gateway/clmm/pools.
  • Raydium CLMM lookup works via GET /gateway/networks/{network_id}/pools?connector=raydium&pool_type=clmm (Raydium is not supported by GET /gateway/clmm/pools).
• Token save test: passed.
  • POST /gateway/networks/solana-mainnet-beta/tokens/save/2b1kV6DkPAnxd5ixfnxCpjxmKwqjjaYmCZfHsFu24GXo succeeded and added PYUSD.
  • Verification via GET /gateway/networks/solana-mainnet-beta/tokens confirms token is present.
• Test lp executor using meteora ok
  • LP executor creation passed for Meteora SOL-USDC
  • Executor lifecycle was validated end to end
    • RUNNING (in range, position created
    • Stop request accepted (/executors/{executor_id}, keep_position=true)
    • TERMINATED (close_type=POSITION_HOLD)
• Portfolio/Balances
  • portfolio/state with refresh:true was verified after a real SOL -> USDC swap and reflected updated balances.
  • Multi-exchange + Gateway balance queries were verified with Binance + Solana balances returned, and Gateway wallets confirmed (Solana + Ethereum).
    • For ethereum, add preferred network to default_networks of ethereum-mainnet