Environments
Which host to call, and how to ask an API which chain it reads.
What is live today
TREND runs on its own dev validator. The mainnet programs are not deployed: their ids are reserved and no launch exists there. Statement as of 2026-10-10.
| Dev (live) | Mainnet (not live) | |
|---|---|---|
| API | https://api.dev.trend.fun | https://api.trend.fun (reserved) |
| Realtime stream | wss://api.dev.trend.fun/v1/stream | wss://api.trend.fun/v1/stream (reserved) |
| Client | https://dev.trend.fun | https://trend.fun (holding page) |
| Docs | https://docs.dev.trend.fun | https://docs.trend.fun |
| Chain | TREND's own validator. Balances, launches and prices exist only there. | Solana mainnet. Nothing of ours is deployed there yet. |
Only dev is live. The mainnet hosts are reserved names; do not point anything at them yet.
Which chain am I talking to
Ask the API:
curl -s https://api.dev.trend.fun/healthzThe answer includes:
{ "ok": true, "cluster": "localnet", "programId": "G5VTggvWQRn9skJJ1YrDfPvpprVZYdhkUgCRxwpfcokz" }cluster: "localnet" means TREND's own validator. Balances, launches and prices on it exist only there: a remote chain
asked about those addresses answers truthfully that they do not exist. Read cluster and programId rather than
assuming, and refuse to act when they are not what you expect.
CORS
Browsers on the TREND client and docs origins can call the API directly. A browser page elsewhere is blocked by the API's origin allowlist, so call it from a server. The docs origins are on the allowlist so the playground in the reference can send a request.
Resets
The dev validator is reset from time to time. Every launch, mint and balance on it changes when that happens. Never store a dev launch address as if it were permanent.