Opening next view...

Company scope

About Tech-Ping

Operational scope for Tech-Ping's read-only odds desk: data sources, signal coverage, launch limits, and non-goals.

Product mode
Read-only desk Monitoring, screening, signals, and alert review without trade or bet placement.
Coverage
Kalshi + sportsbook odds Prediction-market prices and stored sportsbook snapshots are first-class launch data.
Launch surfaces
Web + Android US-only, individual accounts, and push-first alert delivery.
Excluded
No execution flow No orders, bet slips, positions, or affiliate betting language in the product.

Operating boundaries

What the public trust surface proves

Area Current state Evidence shown Boundary
Product mode Read-only market desk Prices, edges, signal state, freshness, and delivery readiness No order entry, bet placement, portfolios, or execution language
Data sources Prediction markets plus stored sportsbook odds Current price, fair value, range, books, and last-check labels Public pages do not call providers directly during render
Signals Threshold and movement monitoring after sign-in Recipe, threshold, current value, distance, capacity, and delivery state Signals notify; users decide independently outside Tech-Ping
Launch limits US-only, 18+, individual accounts Web plus Android launch scope and push-first delivery No iOS distribution, teams, org roles, SMS, or email alerts at launch

What Tech-Ping is

Tech-Ping is a read-only odds intelligence desk for prediction markets and sportsbook comparison data. It keeps screening, tracked markets, signal rules, and delivery review in one account-scoped workflow.

Tech-Ping does not place trades, bets, orders, or manage positions.

Launch data and signals

Launch coverage combines supported prediction-market prices with stored sportsbook consensus, range, and book-count evidence where that comparison data is available.

  • Use Markets Board for dense screening across supported odds sources.
  • Use tracked markets when an event deserves repeated review, history, and news context.
  • Use signals for threshold, movement, expiry, volume, spread, and cross-source comparison monitoring.

Launch boundaries

  • Launch surfaces are web and Android for US 18+ individual accounts.
  • Public pages show cached or illustrative rows only; signed-in pages show account-scoped tracked markets, signals, and delivery state.
  • Device registration happens on mobile because the signed-in phone or tablet creates the push token that receives alerts.
  • No trading, bet placement, bet slips, portfolios, organizations, or execution workflow are part of the launch product.