Playtide — Steam Market Intelligence API

Endpoints

Base URL https://api.212.147.241.73.sslip.io. Responses are JSON; trends are cached briefly. Free tier during beta: no API key needed, 120 requests/minute per IP.

Endpoint	Description
`GET /v1/apps/:appid/players/trend`	Player-count history with min/max/average, week-over-week change, and a generated insight line. Query: `days` (1–365, default 30). Requesting a trend for an untracked game starts tracking it.
`GET /v1/manifest`	Versioned tool manifest for MCP (Model Context Protocol) clients and operators. Send `current_version` for a conditional fetch. Pin your copy and opt clients in with `STEAM_MCP_REMOTE_MANIFEST=1`.
`GET /v1/pulse/latest`	Latest from the Playtide market digest: methodology and observations on Steam trends and live-ops patterns. Query: `limit` (1–10, default 3).
`GET /v1/status`	Service health: uptime, tracked app count, total snapshots, freshest reading.
`GET /healthz`	Liveness probe for uptime monitors.

Quickstart

One request, no signup:

# Player trend for Counter-Strike 2 (appid 730)
curl https://api.212.147.241.73.sslip.io/v1/apps/730/players/trend?days=7

# Latest market-digest entries
curl https://api.212.147.241.73.sslip.io/v1/pulse/latest?limit=3

# Service status
curl https://api.212.147.241.73.sslip.io/v1/status

MCP servers point at the backend with two environment variables:

STEAM_MCP_BACKEND_URL=https://api.212.147.241.73.sslip.io
STEAM_MCP_REMOTE_MANIFEST=1

Why Playtide

History Steam doesn't keep

Steam publishes only the current player count. Playtide snapshots tracked apps every 30 minutes, so you get the trend series nobody else has.

Zero setup

Plain REST JSON over HTTPS. No SDKs, no signup, no keys during beta. Ask by appid or exact game name.

Analysis included

Every trend ships with computed stats and a plain-language insight line, written against the data — not boilerplate.