Follow your Sets on the realtime member page at algoset.io/app, or connect your tools to the private JSON WebSocket endpoint.Each signal includes a strike price and clearly marked UTC times. You decide whether to trade and place every order yourself.
View your signals, check connection status and manage membership from your Algo Set account.
Keep your active signals in view, with a card for each contract. Filter by Set and asset, and check the strike, estimated probability and UTC timing.
Active access and a verified device are required. Use one live connection at a time, either the board or your own tools. Signal availability depends on your Set’s launch status.
Connect your tools to your Set’s private feed. Receive the signal’s strike price, estimated probability, firing time and contract closing time.
A five-minute contract resolves under its market's stated outcome and settlement rules. Each Set gives you information for a specific contract window. You use your own eligible venue account and place every order yourself.
Illustrative values and fixed example times. This is not a live signal, trading instruction, or a screenshot of a member interface.
Receive your Set's signal through your private delivery channels.
Check when the signal fired, when the contract closes, and whether its data and connection are current. An expired or stale signal no longer applies.
You decide whether to trade and at what size. Algo Set does not access your venue account or submit orders.
These illustrative WebSocket examples show a signal and a connection-status message. Heartbeats update the board’s connection indicator; only signals become cards. The values and times are fictional. The signal’s asset field identifies which currently supported asset the message concerns—for example, BTC, ETH, or SOL. The strike price is the underlying asset's outcome threshold for that specific contract. It is fixed for the signal and is separate from the price you pay for the contract. The market's settlement rules, including how ties are resolved, still apply.
Open-source tools on GitHub
{
"type": "signal",
"data": {
"signal_id": "signal_example",
"strategy_set": "Example Set",
"asset": "BTC",
"strike_price": 60000.125,
"strike_currency": "USD",
"observation": "YES",
"estimated_probability": 0.67,
"generated_at": "2000-01-01T12:00:00Z",
"contract_end_at": "2000-01-01T12:05:00Z",
"data_status": "CURRENT"
}
}{
"type": "heartbeat",
"data": {
"delivery_status": "CONNECTED",
"source_status": "CURRENT",
"as_of": "2000-01-01T12:00:00Z"
}
}Once your payment is confirmed, sign in to open your delivery guide and connect your tools. Sign in with your email and password. You can add an authenticator app or a passkey in account security. Your private signal board is at algoset.io/app.
Complete checkout using an available payment method. Access begins after payment is confirmed and signal delivery is enabled for your Set.
Use your verified email and password, or an optional registered passkey.
View the signals for your authorized Sets. To connect your own tools, follow the guide in your account.
Browse the code, documentation and examples for Algo Set’s public market-data and wallet tools.
A WebSocket heartbeat is a regular status message. It reports whether delivery is connected and whether the source data is fresh. If either becomes stale, Algo Set stops treating the signal as current; third-party presentations may take additional time to reflect that change.
A new signal arrives with its Set, asset, strike price and currency, firing time, and contract closing time.
A signal is current only while its window is open and its data is up to date.
New signals stop if data is stale, the connection fails, or membership ends.
After the window closes, the card moves to the ended signals from your current session. It is no longer current.
Third-party presentations may be delayed, duplicated, unavailable, or visible on another signed-in device. Members should confirm current signal and heartbeat status through the authenticated WebSocket before deciding whether to act.
