Endpoints and routing
Two anchor relays serve app lanes. The path decides which part of the relay you reach.
Anchor relays
wss://cinder-relay.cinderous1.workers.devwss://cinder-relay.jt0856.workers.dev
They run the same code but are separate deployments with separate storage: an event published to one is not copied to the other. Connect to both if you want redundancy, and publish to both.
Paths
| Path | What it is | For third-party apps? |
|---|---|---|
/app/<id> | App lane | Yes |
/ | The Cinderous messenger (NIP-42 AUTH required, own-inbox subscriptions only) | No |
/s/<0-f>, /presence | Cinderous message shards and presence | No |
| Anything else | Refused with a NOTICE, then closed | — |
Plain HTTP requests
Non-WebSocket requests always get 200: /healthz returns ok, a request with Accept: application/nostr+json returns the relay information document, and anything else returns a short text. A 200 therefore does not mean your path is right — open a WebSocket to check.
Self-hosting
The relay is open source and the Cloudflare version supports app lanes. If you need your own quota or longer retention, see the self-hosting guide. The Node.js version has no lanes and always applies the strict Cinderous rules.