Transfer Routes

HyperliquidPolymarket

Returns the multi-step transfer routes enabled by the current deployment. The forward route moves HyperCore USDC through HyperEVM to Polygon pUSD. Deployments with reverse ingress enabled also return the Polygon pUSD to HyperCore USDC route described below.

Endpoint

POST /info

Request Body

{
  "type": "protocolTransferRoutes"
}

Response

200: Available
503: Unavailable

{
  "routes": [
    {
      "termsMode": "quoted",
      "fundingAsset": "0x00012710",
      "destinationFinality": "polygon_finalized",
      "steps": [
        {
          "source": {
            "kind": "hyperliquid",
            "dex": "",
            "asset": "0x00012710"
          },
          "destination": {
            "kind": "chain",
            "networkId": "eip155:999",
            "address": "0x1111111111111111111111111111111111111111",
            "asset": "0x800201b88339cb7199b77e23db6e890353e22632ba630f"
          }
        },
        {
          "source": {
            "kind": "chain",
            "networkId": "eip155:999",
            "address": "0x1111111111111111111111111111111111111111",
            "asset": "0x800201b88339cb7199b77e23db6e890353e22632ba630f"
          },
          "destination": {
            "kind": "chain",
            "networkId": "eip155:137",
            "address": "0x2222222222222222222222222222222222222222",
            "asset": "0x800101c011a7e12a19f7b1f670d46f03b03f3342e82dfb"
          }
        }
      ]
    }
  ]
}

{
  "error": "Protocol transfer routes are unavailable",
  "code": "SERVICE_UNAVAILABLE",
  "timestamp": 1785254400000
}

The addresses above are examples. Always use the values returned by the active deployment. When reverse ingress is enabled, this same response also includes a Polygon pUSD → HyperEVM USDC → HyperCore USDC route with schemaVersion: 2. Its destination finality is hypercore_settled. Request its quote with the existing protocolTransferQuote info operation, submit it with the existing executeProtocolTransfer exchange operation, and poll the existing protocolTransferStatus operation. schemaVersion distinguishes the signed canonical shape; it does not select a separate API path. Protocol-transfer route discovery does not publish or enforce a protocol monetary cap.

Endpoint Shapes

Hyperliquid endpoint:

{
  "kind": "hyperliquid",
  "dex": "",
  "asset": "0x00012710"
}

Chain endpoint:

{
  "kind": "chain",
  "networkId": "eip155:137",
  "address": "0x2222222222222222222222222222222222222222",
  "asset": "0x800101c011a7e12a19f7b1f670d46f03b03f3342e82dfb"
}

Start Here

Info

Analytics

Exchange

WebSocket

Endpoint

Request Body

Response

Endpoint Shapes

​Endpoint

​Request Body

​Response

​Endpoint Shapes

Endpoint

Request Body

Response

Endpoint Shapes