Planned Signals API: quant-signals

Launch gates

PUBLIC ACCESS COMING SOON

This page records the intended authenticated read-only contract, not a live member service. The API remains non-purchasable; its deployed edge must reject anonymous, expired, revoked, and wrong-tier requests before returning authenticated telemetry. Any public delayed telemetry surface is separate from API authorization.

API checkout requests are rejected with tier-unavailable.
No authenticated Stream API credentials or member entitlements are issued. Telegram onboarding keys are not API credentials.
Launch requires the authenticated API surface to reject anonymous, malformed, expired, revoked, and wrong-tier requests at its deployed edge.
Every event must pass the 24-hour embargo and field-level redaction review.

Sample planned SIGNAL_OPEN frame

{
  "event": "SIGNAL_OPEN",
  "symbol": "XAUUSD",
  "direction": "LONG",
  "entry": 2748.50,
  "stop_loss": 2735.00,
  "take_profit": 2789.00,
  "target_r": 3.0,
  "max_slippage": 0.80,
  "regime": "volatility_breakout",
  "gate_confidence": 0.842
}

TELEGRAM WEBHOOK Bot Integration TURNING IT ON

Planned delivery for local bot clients. The channel is built to carry structured signal text so Python, Node, or Go can parse lot size and dispatch into a broker API.

PLANNED GET /v1/signals

Intended delayed closed-deal record (minimum 7-day lag, day-resolution), normalized symbols, and provable win/loss labels. Contract illustration only; this route is not live.

PLANNED GET /v1/positions

Intended public open-position record with a 24-hour delay and masked entry coordinates. Unmasked coordinates remain unavailable to public API clients until launch gates pass.

PLANNED GET /v1/performance

Intended indexed performance summary (base 100 growth, max drawdown, win rate), derived from the same certified model database as the public preview. Contract illustration only.

Quickstart

The intended REST audit envelope will return data, source, and generated_at (UTC) once the gateway passes its launch gates. The samples below are contract illustrations, not callable endpoints.

cURL planned REST audit snapshot

# Coming soon. No public host, Stream API endpoint, or credential is issued.
# Telegram Smart Signals are the current buyable channel.

Python planned stream consumer

# Coming soon. No public authenticated Stream API host or credential is enrolled.
# Any public delayed telemetry surface is separate from API entitlement.

Availability and Failover Contract

The planned gateway must publish one ledger for every client-visible term. The current status is unavailable; the following rows are acceptance gates, not live service levels.

Term	Value	What it means for you
Public status	Coming soon	No public Stream API enrollment, credentials, or entitlement is issued today. Telegram onboarding keys are separate and do not authorize API access.
Authentication	Launch gate	Anonymous, expired, revoked, and wrong-tier requests must fail before any authenticated telemetry is returned.
Data boundary	Launch gate	The public contract must define the 24-hour embargo and redaction behavior for every field.
Connectivity	Launch gate	REST polling, WebSocket reconnects, heartbeats, and recovery semantics must be exercised against the deployed edge.

The planned service will not publish uptime guarantees until heartbeat, recovery, and error-code behavior are exercised against the deployed edge.

Stream event schema

Planned API frames will use a fixed envelope: event, symbol, ts (engine timestamp, UTC epoch millis). Strategy-specific fields follow.

Event	Payload Fields	Description
SIGNAL_OPEN	entry, stop_loss, take_profit, target_r, max_slippage, gate_confidence	Verified setup dispatched with bracket coordinates and 0.80 pt slippage boundary.
ORDER_FILLED	fill_price, slippage, lots	Broker fill confirmation with realized slippage against the boundary.
TRAIL_UPDATE	new_stop, trail_r	Stop-loss relocation as the position locks profit in R increments.
TAKE_PROFIT	exit_price, realized_r	Target execution closing the deal with realized R multiple.
STOP_LOSS	exit_price, realized_r	Protective stop execution closing the deal at bounded loss.

Delivery Posture

What the future service must prove before launch. No uptime or live-service claim is made while the gateway is unavailable; the posture below is an acceptance checklist.

DETECTION heartbeat contract

A future heartbeat must make a missed frame detectable client-side within 60 to 90 seconds. This target cannot be claimed until it is tested against the deployed edge.

RECOVERY during reconnect

The planned stream must reconcile a reconnect against the delayed REST snapshot before accepting a new frame. No route is available to clients today.

PUSH LANE path diversity

Telegram delivery must remain independent of the future API stream. A stream outage must not take the alerts channel down, and the alerts channel must not authorize API access.

INTEGRITY reconcile, never assume

Every future closed deal must reconcile against the broker fill record before publication. A client must never infer a close that the feed did not report.

Telegram Smart Signals are open. The authenticated Stream API is still under development.

No API seat can be purchased, no public credential can be issued, and no endpoint may return data while the gateway rollout flag is false. When the service launches, it will distribute read-only signals without taking custody or execution control of client capital.

Reserve Telegram access Inspect the tape

Where this feed comes from

The intended feed contract, its evidence base, and the checks that must pass before the public gateway opens.