Game catalog and pricing collection
Use Steam endpoints to turn game catalog and pricing collection into repeatable API requests with documented inputs and JSON responses.
Turn any public Steam store or community page into structured game data — app details and pricing, review scores with rating histograms, live concurrent player counts, achievements, news, featured listings, and SteamSpy ownership estimates as normalized JSON for game-market dashboards and research. Credential-free.
Extract Steam game details, review scores, player counts, achievements, news, store search, and SteamSpy stats as JSON from public Steam pages.
Endpoint families
6
Documented params
101
Examples
21
Live catalog snapshot
Active endpoints
21
Methods
GET
Required params
33
Schema refs
21
{
"platform": "Steam",
"endpoint": "steam-app",
"method": "GET",
"path": "/steam/app",
"auth": "apiKey"
}Ready-made datasets
Crawlora has already indexed the demand-weighted head of Steam — price, review tier, owner band, genres and community tags per game — plus a daily time series of Steam’s live charts (concurrent players, most played and top sellers). Browse the interactive studies or query them through the Datasets API.
Open the Steam games datasetUse cases
Extract Steam game details, review scores, player counts, achievements, news, store search, and SteamSpy stats as JSON from public Steam pages.
Use Steam endpoints to turn game catalog and pricing collection into repeatable API requests with documented inputs and JSON responses.
Use Steam endpoints to turn review score and player-count monitoring into repeatable API requests with documented inputs and JSON responses.
Use Steam endpoints to turn game-market and competitor research into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Steam endpoint catalog — 21 endpoints, 101 documented request parameters, and 21 published response schemas — the same catalog Docs and Playground run against.
21 documented Steam endpoints, grouped into 16 request families — Charts, Reviews and Search, plus 13 more.
101 request parameters are documented across those Steam endpoints, 33 of them required — the full input contract is public before you write any integration code.
21 of the 21 Steam endpoints ship a recorded example response, and 21 carry a documented response schema — you can code against the real JSON before the first request.
Steam endpoints document their error responses (400, 404 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
21 hosted MCP tools back the Steam endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
/steam/charts/concurrent
/steam/reviews
/steam/search
/steam/tags
/steam/achievements
/steam/app
Featured endpoints
/steam/appReturns store metadata for a single Steam app (title, type, price, developers/publishers, platforms, genres, categories, release date, metacritic, recommendation and achievement counts). cc selects the store region (and price currency) and l the text language. filters is a comma-separated subset of allowed fields to shrink the payload.
Sampled 14 Oct 2026: 3 items, 2 fields filled in every item. description: “Action” and 2 other values.
MCP tool steam_app
/steam/searchResolves a search term to Steam apps via the store typeahead (title, appid, price, platforms, metascore). Best for title -> appid lookup; returns roughly ten results. For faceted, paginated search use /steam/search/results.
Sampled 14 Oct 2026: 10 items, 5 fields filled in every item, 3 not. metascore: 72 to 95, median 77; name: “Portal 2” and 9 other values.
MCP tool steam_search
/steam/search/resultsRuns the Steam store search with pagination and sorting and returns the result rows (appid, title, release date, review summary, price, platforms). Supports start/count paging and sort_by.
Sampled 14 Oct 2026: 25 items, 6 fields filled in every item, 3 not. review_summary: Very Positive (7), Positive (4), Mostly Positive (4) and 2 more; name: “Combolands: Roguelike Citybuilder” and 24 other values.
MCP tool steam_search_results
/steam/reviewsReturns a page of user reviews for an app with cursor pagination and an aggregate query_summary (score, positive/negative totals). Aggregate totals populate only on the first page (cursor=*). Pass the returned cursor back to page.
Sampled 14 Oct 2026: 5 items, 14 fields filled in every item. timestamp_created: 2026-10-13; votes_up: 0 to 1, median 0.
MCP tool steam_reviews
/steam/reviews/histogramReturns the positive/negative recommendation counts over time (the store review graph): weekly/monthly rollups plus recent daily buckets.
Sampled 14 Oct 2026: 183 items, 3 fields filled in every item. date: 2011-08-01 to 2026-10-01; recommendations_up: 6 to 60,341, median 13,163.
MCP tool steam_reviews_histogram
/steam/playersReturns the current number of concurrent players for a Steam app, given its numeric `appid` such as `570`. The response has `appid`, `player_count` and a `source_url`. An app with no player-count data returns 404.
Sampled 14 Oct 2026: 2 of 2 fields returned with a value. player_count: 882,376.
MCP tool steam_players
Related APIs
Media & Streaming
Follow German football from the Bundesliga down to the lowest Kreisklasse. Discover competitions in all 22 federations, then read matchdays, standings, scorers, clubs, teams, and players from the DFB's own amateur-football portal.
Media & Streaming
Browse Sportskeeda's sports and entertainment coverage, community wikis, quizzes, and fan games with the catalog's current slugs and filter limits.
Media & Streaming
Research streaming catalogs, title availability, providers, offers, seasons, episodes, and release changes from JustWatch with normalized JSON.
How to scrape Steam
Steam exposes game details, user reviews, and live player counts through public store and community pages. Crawlora's Steam endpoints return them as normalized JSON — across search, app detail, reviews, rating histograms, player counts, achievements, news, and SteamSpy stats — with no Steamworks key, rate-limit juggling, or proxy setup.
/steam/search takes a required term and is the typeahead for title to appid lookups; /steam/search/results adds start, count and sort_by (Relevance, Released_DESC, Name_ASC, Price_ASC, Price_DESC, Reviews_DESC). On 2026-10-30 roguelike sorted by Reviews_DESC reported total 7,683 and returned 25 rows although count 5 was requested, so page by start and read the length returned. Prices arrive as text such as $19.84 or Free, discount_pct as -30%, and the platforms flags came back false on every row, so confirm platforms with /steam/app.
/steam/app takes appid with cc, l and filters and returns store metadata. /steam/items resolves up to 100 app ids in one call with weighted community tags, /steam/package covers purchasable bundles, /steam/achievements gives global unlock percentages (empty for apps without them), and /steam/news takes appid with count (default 10) and maxlength.
On 2026-10-30 /steam/players returned 317,286 concurrent players for Dota 2 (appid 570), the 100-rank /steam/charts/concurrent leaderboard listed 318,782 for it at rank 3 behind Counter-Strike 2 (425,638 now, peak 1,207,353), and /steam/steamspy reported ccu 623,941 with owners as the text 100,000,000 .. 200,000,000. These are different measurements, so store the route name beside every number.
/steam/reviews pages user reviews by cursor with filter, language, review_type, purchase_type, day_range and num_per_page, plus a query_summary of score and positive and negative totals. /steam/reviews/histogram returns weekly and monthly rollups and recent daily buckets, and /steam/community-recommendations returns quality reviews across the whole store.
/steam/charts/most-played ranks weekly peak players, /steam/top-sellers is the weekly chart for a country, /steam/featured-categories returns specials, top_sellers, new_releases and coming_soon, and /steam/charts/top-releases returns one page per month. Store routes take cc and l for region and language.
/steam/tags/list returns community tag ids and localized names. /steam/tags and /steam/category/{slug} browse by those tags and store facets such as maxprice, os, deck_compatibility and vrsupport with start and count, and need no free-text term.
Agent skills
Install a Crawlora agent skill and your agent can pull Steam data as JSON through the documented API, without writing a scraper. These skills cover Steam:
Evaluate Steam game niches using Crawlora's game catalog, chart and player-count history, live pricing, reviews, and release news. Use for…
npx skills add github.com/Crawlora-org/crawlora-skills --skill steam-market-opportunity-researchResearches video games via the Crawlora API — Steam (store pages, pricing, reviews, player counts, charts, tags, achievements) and PlayStation Store…
npx skills add github.com/Crawlora-org/crawlora-skills --skill gaming-researchResearch observed Steam price history and compare current game editions or PlayStation offers using Crawlora. Use for a dated discount brief…
npx skills add github.com/Crawlora-org/crawlora-skills --skill game-price-history-researchFAQ
Send an app ID to Crawlora's /steam/reviews endpoint and get user reviews, review scores, and a rating histogram as structured JSON, with pagination handled for you and no Steamworks key. Collect public data and respect Steam's terms.
Steam's public JSON endpoints work for small jobs but are rate-limited, unpaginated by default, and split across store, community, and SteamSpy hosts. Crawlora normalizes all 12 Steam endpoints into one JSON shape, handles pagination, rate limits, and proxies at volume, and exposes them as hosted MCP tools for AI agents.
Collecting publicly accessible game, review, and player-count data is generally permissible if you respect Steam's terms of use, robots directives, rate limits, and applicable law. This is for public data you are authorized to collect.
Not really. Valve has never published an official market-price API — every third-party price and market tool relies on undocumented endpoints with unpublished, aggressively enforced per-IP rate limits, and frequent 429 errors are common. Steam's review data is public but similarly undocumented, with no official bulk-export path. Crawlora normalizes reviews, rating histograms, and player counts into one documented, paginated JSON surface instead.