Private beta - London hosted websocket feed

Polymarket wallet signals before public feeds catch up.

PolySocket.dev streams watched-wallet activity directly to your websocket so developers, bot makers, API users, and trading infrastructure teams can react earlier.

Join the server View connection flow

Not a copytrading botNo executionStructured websocket events

98.7%overall win rate vs tested websocket providers

722msmedian lead vs tested websocket providers combined

20.2smedian lead vs Polymarket /activity

119.8smedian lead vs Polymarket /trades

simple integration

Auth code. Wallet IDs. Live websocket stream.

The product is intentionally small: you tell PolySocket which wallets matter, and your system receives the usable wallet activity signal as a structured event.

Authenticate

Open the websocket with your access token or private beta auth code.

Subscribe wallets

Send the Polygon wallet IDs you want to monitor. Add one wallet or a full watchlist.

Route signals

Receive structured wallet activity events and send them into your bot, alerting, dashboard, or API.

wss://feed.polysocket.dev/v1beta endpoint

const socket = new WebSocket("wss://feed.polysocket.dev/v1");

socket.onopen = () => socket.send(JSON.stringify({
  auth: "ps_live_xxx",
  wallets: ["0x7a91...f12c", "0x9bc4...01aa"]
}));

socket.onmessage = ({ data }) => {
  routeToYourSystem(JSON.parse(data));
};

low-latency path

Hosted from London for a direct watched-wallet signal path.

PolySocket is designed around a direct low-latency feed path instead of waiting on public RPC provider fanout or indexed public API updates. It is a feed for systems that already have their own execution, alerting, analytics, or automation.

example eventstructured JSON

{
  "type": "wallet_activity",
  "wallet": "0x7a91...f12c",
  "chain": "polygon",
  "region": "london",
  "detectedAt": "2026-05-02T16:18:43.112Z",
  "leadMsVsAlchemy": 564
}

benchmarks

PolySocket lands first in the early signal window.

These sample runs compare when the watched-wallet signal becomes usable through PolySocket versus common websocket providers and indexed Polymarket APIs.

watched wallet eventPolySocket gets the first usable signalpublic visibility catches up

Wallet activity starts0ms

PolySocket first signalfirst usable signal

Alchemy WS+564ms

PublicNode WS+717ms

Bor WS+882ms

/activity API+20.2s

/trades API+119.8s

Comparison	Sample	Win rate	Median lead	P75 lead
Alchemy websocket	54	about 100%	564ms	744ms
PublicNode websocket	50	about 100%	717ms	1,157ms
PublicNode Bor websocket	52	about 96%	882ms	1,194ms
All tested websocket providers	156	98.7%	722ms	995ms
Polymarket /activity API	45	effectively 100%	20.2s	26.4s
Polymarket /trades API	31	effectively 100%	119.8s	150.0s

built for builders

Use the feed where speed actually matters.

Feed copytrade bots with faster wallet signals

Build wallet activity alerts and dashboards

Route watched-wallet events into internal APIs

Compare high-conviction wallet activity against markets

Monitor specific Polymarket wallets without waiting on indexed APIs

Give trading infrastructure a cleaner real-time input

clear boundary

Infrastructure feed. Not a trading bot.

What PolySocket does

Streams selected Polymarket wallet activity to your websocket as low-latency, structured data for your own systems.

What PolySocket does not do

It does not execute trades, manage positions, size orders, custody funds, or decide what your strategy should do.

private beta

Subscribe for early access to the PolySocket feed.

Join the server, request access, and test watched-wallet websocket signals before the public API surface is finalized.

Join server Request access