API routes - remix.world

Hosts

Web app: https://remix.world
Production Go API: https://api.remix.world/api/v1
Development API: https://dev-api.remix.world/api/v1

Production market requests must include the mainnet chain selector where the endpoint supports it: chain_id=4663 or chain_ids=4663.

Mainnet route groups

Method	Route family	Purpose
`GET`	`/remixes`	Token markets and discovery
`GET`	`/remixes/{address}/ohlcv`	Token chart candles
`GET`	`/remixes/{address}/holders`	Indexed holder data
`GET`	`/remixes/{address}/transactions`	Indexed swaps
`GET/POST`	`/users/*`	User profile and account flows
`GET`	`/health`	API health

The exact response shape is defined by the production OpenAPI contract. Do not infer reward, governance, or verification availability from a route name; those capabilities are disabled on mainnet.

Authentication

First-party authenticated requests use the Dynamic JWT in the X-Authorization header. Never place private backend or Goldsky credentials in browser code.

Webhooks

Mainnet Goldsky webhook consumers are private backend routes. They are not a public integration surface; see Webhooks.