You run a model that takes Alterscope factors as inputs. Polling the REST endpoint every minute wastes quota and lags reality. The WebSocket factor stream pushes a row every time a factor changes for the opportunities you subscribe to.Documentation Index
Fetch the complete documentation index at: https://developer.alterscope.org/llms.txt
Use this file to discover all available pages before exploring further.
What you build
A long-lived WebSocket consumer that keeps your in-memory factor cache fresh.1. Open the connection
2. Sample message
3. Reconnect logic
The server pings every 30 seconds. If you miss two pings, reconnect with exponential backoff (start at 1s, cap at 30s). Resubscribe on each connect. The server does not replay messages on reconnect; if you need gap-fill, run a single REST query for the affected opportunities right after reconnect.4. Tier requirements
WebSocket access is Pro and Enterprise. Free tier returns 403 on the upgrade handshake.5. Troubleshooting
- 403 on connect: verify the key has
read:yield:detailscope and your org is on Pro+. - No messages: the stream is event-driven. Quiet markets produce quiet streams. Send
{"action": "ping"}if you want to confirm liveness without waiting for a factor to move.