Getting Started

Ryze Protocol exposes three services for integrators, available on both mainnet and testnet:

Mainnet (Base)

Service	Base URL
Ryze API	https://mainnet.api.ryze.pro/api
Ryze Router	https://mainnet.router.ryze.pro
Relayer	https://mainnet.relayer.ryze.pro/api/v1
Price Proxy	https://mainnet.proxy.ryze.pro

Testnet (Base Sepolia)

Service	Base URL
Ryze API	https://sepolia.api.ryze.pro/api
Ryze Router	https://sepolia.router.ryze.pro
Relayer	https://sepolia.relayer.ryze.pro/api/v1
Price Proxy	https://sepolia.proxy.ryze.pro

TIP

Use the testnet endpoints for development and testing. The API and Router have identical interfaces on both networks.

Quick Example

Fetch the token list, then request a swap quote:

# 1. Get available tokens
curl https://mainnet.api.ryze.pro/api/assets

# 2. Get a swap quote (USDC -> WETH, 100 USDC)
curl -X POST https://mainnet.router.ryze.pro/quote \
  -H "Content-Type: application/json" \
  -d '{
    "tokenIn": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "tokenOut": "0x4200000000000000000000000000000000000006",
    "amountIn": "100000000",
    "slippageTolerance": 50,
    "maxHops": 3
  }'

Conventions

• Numbers: Large numbers (balances, amounts) are returned as strings to preserve precision. Token amounts are in raw units (e.g., 100000000 = 100 USDC with 6 decimals).
• WAD format: Fee percentages and prices use WAD format where 1e18 = 1.0 (100%). For example, a 0.3% swap fee is 3000000000000000.
• Addresses: Lowercase Ethereum addresses with 0x prefix.
• Timestamps: ISO 8601 in responses, Unix seconds in query parameters.
• Pagination: API endpoints use page and limit query parameters. Responses include a pagination object with totalItems, totalPages, hasNext, hasPrev.

Chain

Ryze is deployed on Base (Chain ID: 8453).

Contract	Address
MultiHopRouter	0x662F15226f5b6Bf8aA10512374Af3115412C04bA
WeightedPoolFactory	0x3810D54a4EA3084Ef68587A8bE3778cAD9301fF7
WETH	0x4200000000000000000000000000000000000006
USDC	0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
cbBTC	0xcbB7C0000aB88B473b1f5aFd9ef808440eed33Bf

Error Handling

Both services return errors as JSON:

{
  "error": "description of what went wrong"
}

Common HTTP status codes:

Code	Meaning
200	Success
400	Bad request (invalid parameters)
404	Resource not found (unknown pool, token pair)
503	Service unhealthy

Next Steps

• Fetch Assets -- get the token list
• Get Swap Quotes -- request optimized swap routes
• Fetch Pools -- browse pool states and stats