API Overview

The REST playground defaults to Monad mainnet. Select testnet in its server dropdown before testing there. Use the corresponding mainnet deployment or testnet deployment addresses, chain ID, wallet signatures, and JWT. Changing the server does not transform values already entered into a request. Response examples illustrate the schema, not live state; some recorded responses are labelled testnet snapshots. Use Relay to submit signed actions, Data Source for catalogs and finalized history, and Exchange Gateway for current projections and live updates.

Submitting trades: account permission, authentication, signing, and Relay submission.
Reading market data: markets, charts, trade history, and live books.
Following account activity: balances, orders, and fills.

Service endpoints

Kuru exposes these API surfaces on both networks:

Surface	Mainnet	Testnet
Relay REST	`https://relay.mainnet.kuru.io`	`https://relay.testnet.kuru.io`
Relay WebSocket	`wss://relay.mainnet.kuru.io/relay/ws`	`wss://relay.testnet.kuru.io/relay/ws`
Data Source REST	`https://api.mainnet.kuru.io`	`https://api.testnet.kuru.io`
Exchange Gateway REST	`https://gateway.mainnet.kuru.io`	`https://gateway.testnet.kuru.io`
Exchange Gateway WebSocket	`wss://gateway.mainnet.kuru.io/ws`	`wss://gateway.testnet.kuru.io/ws`

The Data Source API returns finalized materialized reads together with the feedEpoch and market or user sequence needed to continue on an Exchange Gateway WebSocket stream. Exchange Gateway REST exposes the current retained projection views directly. Relay APIs separately handle authenticated submission and delivery of signed trading-wallet actions. For direct onchain integration, use the TypeScript SDK or Contract Reference. For SDK-backed sponsored submissions, use Trading-wallet signing and Relay.

Integration Guides

Exchange APIs

Data Source APIs

Relay APIs

API Overview

Service endpoints

​Service endpoints

Service endpoints