StashSage for POE2

v0.5.31 (11/20/2026)

Machine Learning by Budodude

Web Scraping by NocKtuRn4L

Free Path of Exile 2 price-check overlay. Machine-learning valuations for rare items, from live trade data.

Price items in Discord · Request API access for your own tool

Downloads for v0.5.31

Desktop

On Windows, extract the whole ZIP to a folder and run StashSage.exe from there. Keep it beside the _internal folder. You can create a desktop shortcut.

Requires approximately 2.1 GB of disk space on Windows.

Android Companion

No APK is offered for this release.

iPhone Companion

Coming via TestFlight.

Join Discord

The desktop app prices items locally; no item or account data is sent to StashSage for pricing.

StashSage prediction overlay showing price estimates and comparable Path of Exile 2 items

Top 10 Mods for Item Value

Browse trained models (collapsed by default)
Importances are normalized per model. Values shown as percentages.

Why StashSage

Does this sound like you?

  • You pick up items that could be good, but aren't quite sure
  • Your stash fills up with "I'll price this later" items
  • Pricing through the in-game trade UI feels tedious, so you avoid it
  • Typing mods, comparing rolls, and overthinking prices takes more effort than it's worth
  • You don't need a perfect price - you just want a smart starting point
  • One hotkey, instant comparable items, list it, and get back to mapping

No Single Ground Truth

There is no single "right" answer for an item's price. Demand changes with every league and patch, so yesterday's completed sales may not represent today's market.

Trading Reality

The data we see is from items that haven't yet sold. Expensive listings linger while good deals disappear, so raw trade results are noisy and unreliable on their own. If anything, they may represent a price ceiling.

How We Measure Value

StashSage focuses on practical shortcuts instead of perfect accuracy. We look for tools that help you:

  • Judge a reasonable listing price in seconds.
  • Track and encode market dynamics.
  • Avoid obvious price trolls or stale posts.
Bottom line: our goal is faster choices. If you spend less time scrolling trade listings and more time playing, the system is doing its job, even if some items never sell.

Explore Features

Price a single item, review past predictions, value your listed stash, or track listing changes over time. Choose your setup to use these tools on desktop, Android, or through a connected phone or agent.

Discord bot — price single items in Discord

Paste an item's copied description into Discord to get a price estimate and comparable listings. The bot uses the hosted pricing service; no desktop installation is required.

  1. Select or hover over the item in game for which you'd like to see price predictions.
  2. Press CTRL+C to copy the item's in-game description.
  3. Paste the description to StashSage Serve bot in our Discord channel to receive your predictions.
  4. Review the estimate and comparable items. Modifier filtering and desktop visualizations are available in the prediction overlay.

The bot prices against multiple leagues — Forbidden Rites and Runes of Aldur. Every prediction reply shows which league answered, and you can switch with:

  • !league — check which league you're currently priced against.
  • !league list — see every league currently installed.
  • !league set <league> — save your preference, e.g. !league set forbidden-rites or !league set runes-of-aldur.

Your choice is saved per Discord user and follows you across servers and DMs.

Want this in your own Discord server? Invite the StashSage bot — no setup on your end, just @mention it or paste an item in any channel.

StashSage Setups

Four ways to run StashSage. Pick the one that matches your devices; each card says where the work runs and where your data stays.

Desktop

Everything in one place: the prediction overlay, prediction history, StashScrape and StashWatch.

Runs on
Your Windows or Linux PC.
Data stays
On your PC.
Needs
The desktop app only.

Desktop setup · Explore the overlay

Android alone

Price your stash with StashScrape on your phone, no PC involved.

Runs on
Your Android phone.
Data stays
On your phone, separate from desktop data.
Needs
Android 8+ and the APK. No APK is offered for this release.

Android setup and sharing

Phone + desktop via Tailscale

Check and control your desktop's StashWatch from a phone browser or the Android app while the PC does the work.

Runs on
Your awake PC with StashSage open.
Data stays
Desktop watch history; Android can cache it offline.
Needs
Tailscale on both devices and desktop access enabled.

Connect your phone

Agent + desktop via Tailscale

Let an agent, such as Muse, check listings, control watches and read watch activity from your desktop.

Runs on
Your awake PC with StashSage open.
Data stays
On your PC; only requested records go to the agent.
Needs
An HTTP-capable agent runner on your Tailscale network.

Connect your agent

What syncs and what does not. A connected phone or agent uses the desktop's watches and history. Phone-run StashScrapes and independent phone watches stay on the phone; Tailscale does not automatically sync them. Export a phone StashScrape run to open it in the desktop viewer.

The Discord bot and the public API are separate hosted services. Neither needs the desktop app. The step-by-step guides below cover each setup.

Set up the desktop app
  1. Download StashSage for Windows or Linux using the links at the top of this page.
  2. Extract the complete archive. On Windows, keep StashSage.exe beside its _internal directory and launch it.
  3. Use the overlay hotkeys for single-item predictions, and the sidebar for History, StashScrape and StashWatch.

Desktop use needs no Tailscale connection or desktop access token. Use the overlay guide, history guide, StashScrape guide or StashWatch guide for the workflow.

Use Android independently and share saved runs

There is no Android download for this release. Choose a release that includes the signed Android APK to use the standalone phone app.

  1. In Run, enter your trade account, choose an installed league, and set Wait Between Searches (120–300 seconds).
  2. Choose All Listings or Merchant Only and the categories to price, then tap Run StashScrape.
  3. Follow the background progress notification. In View StashScrapes, sort and filter results, switch currencies, copy stash searches, or re-price saved listings with the installed models.
  4. Use Share run or save copies to a chosen folder. Transfer the run folder into your desktop's StashScrape save folder to open it in the desktop viewer. Sharing a CSV exports the table; sharing a run includes the saved listings.

Android StashWatch requires v0.5.25 or later with a signed APK that includes the native watch tab.

Independent phone watches do not merge with desktop watches. A listing that disappeared since an earlier scrape is no longer observed, rather than a confirmed sale. Install a newer APK to update the phone's bundled pricing models.

Connect to your desktop: shared Tailscale setup

Use this connection for a phone browser, Android desktop mode, or an agent. Keep StashSage running and the PC awake; minimizing to the tray keeps desktop checks active while clients disconnect.

  1. On the PC: in the redesigned desktop build, open Help → Setups and enable Allow phones and agents to connect. Desktop v0.5.25 downloads keep these controls in StashWatch; v0.5.24 calls the switch Enable HTTP access for phones and agents. Leave the service port at 5006 (recommended). You do not need to choose a port.
  2. On both devices: install Tailscale, sign in with the same Tailscale account, and connect.
  3. On the PC: open PowerShell (Windows) or Terminal (Linux) and paste the command below. If asked to enable HTTPS, follow the link Tailscale prints, then run the command again. See the official Tailscale Serve instructions for help.
tailscale serve --bg --https=10000 http://127.0.0.1:5006
  1. Get the phone link: copy the HTTPS address Tailscale prints, including :10000, for example https://your-pc.your-tailnet.ts.net:10000/. Desktop v0.5.25 and later also offer Copy phone link after setup. Transfer that link to your phone.
  2. Get the password: on the PC, press Copy access token (Copy API token in v0.5.24). Transfer the copied token privately to your phone.

Continue with the phone instructions or agent instructions.

Connection help

Open web page on this PC previews the page locally at http://127.0.0.1:5006/. Your phone uses the HTTPS Tailscale link, including :10000. Only change the local service port in Advanced settings if 5006 is unavailable, and use the new local port in the setup command.

The desktop access token is your private StashSage access password. It is separate from a Tailscale login key and a hosted pricing API key. Paste it into the connection's token field or secure settings; keep it out of URLs and public messages.

To stop monitoring, press Pause. To stop HTTP access, disable its option or exit StashSage. Remove this Tailscale proxy with tailscale serve --https=10000 off.

Use a phone with your desktop

First complete the shared desktop connection setup. These clients control your desktop's StashWatch; the desktop owns its check schedule and history.

Phone browser: iPhone, iPad or Android

Connect Tailscale on your phone, open the HTTPS desktop link, paste the copied token into Desktop access token, and press Connect. The page lets you save and control watches, browse listings and activity, and download CSV. It keeps the token only in the open page's memory and forgets it when closed.

Native Android app

Install a signed Android v0.5.25 or later APK with the native StashWatch tab for this mode. This release offers no Android APK; the browser option still works.

In StashWatch, choose Desktop via Tailscale, then Add desktop connection. Paste the HTTPS link into HTTPS desktop URL and the token into Desktop access token, then press Test and save. Import a desktop watch or save one with the native controls.

Android caches desktop watch history for offline viewing. When the phone disconnects, the awake desktop keeps monitoring. Independent This phone watches and phone-run StashScrapes stay separate; use run sharing to transfer saved StashScrape results.

The remote service returns observed listings and asking prices. Run StashScrape on desktop or Android for model valuations; the phone connection does not expose the desktop overlay or prediction history.

Use an agent with your desktop

An agent such as Muse can use the desktop HTTP API if its tool runner can make authenticated requests from your Tailscale network. This is a general HTTP connection; StashSage does not supply a dedicated Muse integration.

  1. Complete the shared desktop connection setup with Tailscale connected on the desktop and the agent runner. Connecting only your phone does not give a cloud agent access.
  2. Put the HTTPS desktop link and desktop access token into the agent's secure connection settings.
  3. Ask the agent to create or select a watch for your account, league, listing type and categories. For a one-off listing snapshot, leave it paused and request Check now. For repeated checks, start the watch.
  4. The agent can follow the job status, retrieve observed listings as JSON or CSV, and read watch activity. See the desktop API reference for supported calls.

Start StashSage on your desktop before connecting. The current API exposes listing snapshots and watch activity; full model-valued StashScrape runs and prediction history are not exposed to agents. Your agent provider handles any records you ask it to retrieve.

Desktop API for agents and integrations

These calls go to your own desktop's HTTPS connection. Send Authorization: Bearer <token> or X-API-Key: <token> using its desktop access token.

  • GET /stash/catalog — list categories and known leagues.
  • GET /stash/watches and POST /stash/watches — read or save watches.
  • PATCH /stash/watches/{id} — edit settings while no check is running.
  • POST /stash/watches/{id}/start, /pause or /check — control a watch. A manual check returns a job ID.
  • GET /stash/runs/{id} — read a job's status.
  • GET /stash/watches/{id}/listings — read last-known listings; append ?format=csv to download CSV.
  • GET /stash/watches/{id}/events?after=0 — read chronological activity. Save the returned next_cursor and use it as the next after value to avoid logging events twice.

For reliable integrations, send a stable X-Request-ID when requesting a check and reconcile its returned job ID. Use the watch's settings_version as If-Match when editing. Track event generation and head_cursor alongside next_cursor when caching desktop history.

Watches are created paused; start one or request a manual check after saving its settings. This local monitoring API is separate from the hosted item-pricing API, whose credentials and base URL are issued separately.

StashSage FAQ

What is StashSage?

StashSage is a free desktop price-checking and trade utility for Path of Exile 2. It estimates rare-item value, shows comparable listings, highlights influential modifiers, and supports stash pricing workflows.

How does StashSage estimate POE2 item prices?

StashSage runs two models side by side. Model #1 is an XGBoost regressor — a tree-based model that weighs each modifier and how modifiers interact, learned from the modifiers and listed prices of every item in the dataset. Model #2 is a nearest-neighbor (KNN) comparison that reuses XGBoost's modifier weighting to find the most similar listed items and takes their mean and median price. Both learn from current, unsold listings, so estimates are practical starting points, not guaranteed sale prices — even a fairly priced item may not sell.

Why do the two estimates sometimes disagree?

Model #1 (XGBoost) and Model #2 (KNN) take different approaches, so their numbers can diverge — treat them as two perspectives on the same item rather than one right answer. The Model #1 visualization also shows where an item's predicted value sits relative to other items in its category.

How should I read the comparison (Model #2) estimate?

KNN's neighbors don't have to match perfectly — a partial overlap on mods and values can still be a useful comparison. Be careful pricing items with fewer than six modifiers against six-mod items: ask whether your four-mod item is really closer to another four-mod item with the same mods at very different values, or to a five-mod item that shares three exact mods and adds two you don't have.

Which items are supported?

The pricing models are designed for rare Path of Exile 2 items. Magic and unique items are not the intended prediction targets, and support varies by item category and available training data.

Does StashSage upload my item or account data?

The desktop application performs its normal pricing operations locally. Hosted API access requests store your Discord identity and request history as described in API request privacy. Requests sent to third-party services are subject to those services' behavior and policies.

StashWatch saves settings and listing history on the device doing the checks: desktop, or Android in This phone mode. Connected clients access your desktop's records through the authenticated service you enable on your own computer. Android can cache that desktop history locally; an agent receives the records you request. See setup choices and data sharing.

Which operating systems are supported?

Portable downloads are available for Windows and Linux. Windows users extract the complete ZIP and keep StashSage.exe beside its _internal directory. iPhone and iPad can use the connected StashWatch browser view while the desktop stays running.

What display mode should Path of Exile 2 run in?

The prediction overlay is optimized for Windowed Fullscreen. Other display modes may not render the overlay correctly.

How current are the pricing models?

New models are trained every few days and posted for download with StashSage releases. The version and build date at the top of this page identify the currently published application.

Public API

The same pricing engine behind the Discord bot is available as a small HTTP API for your own tools and scripts. Send it copied item text, get back a value estimate, comparable listings, and the modifiers driving the price — the same payload the desktop app renders.

This hosted service works without the desktop app and uses its own API key. To control your computer's watches and read its listing history, use the desktop API in the setup guides.

Manual approval, best-effort. This is a small unpaid service, not a general-purpose developer platform. There is no uptime or stability guarantee, and the contract may change or pause without notice. Fine for personal tools and Discord bots; don't build anything load-bearing on it.

Request an API key

Building your own tool or integration? Request access through Discord. Every request requires administrator approval.

Requests are open: anyone in the StashSage Discord can request a key. Every request is reviewed manually, and approval is not guaranteed.

  1. Join the StashSage Discord.
  2. Find StashSage Serve in the server's member list, open its profile, and choose Message. Use this private conversation with the bot, not a public server channel.
  3. Send the following message, replacing the example with your project name and intended use. Keep the description after !apikey request between 10 and 300 characters.
    !apikey request Guild Price Helper - item price checks for our guild website
  4. The bot confirms your request number. Keep direct messages enabled and the bot unblocked while an administrator reviews it. Pending requests expire after seven days; approval is not automatic.
  5. Check your request at any time by sending !apikey status in the same private conversation.
  6. If approved, the bot privately sends your API key, base URL, and usage instructions. Save the key as a server-side secret; never place it in browser JavaScript, public repositories, or screenshots. The bot will not reveal it again.

Access is linked to your Discord account. An administrator can assign a friendly name while retaining that account link. Consumer keys support league discovery and single-item predictions; rate limits apply, and metrics and batch scoring are unavailable.

API keys are for your own integrations. Ordinary Discord bot pricing and local desktop or Android pricing do not require you to request a key. This is also separate from your computer's desktop access token.

If delivery fails, allow direct messages and ask an administrator to retry using your request number. If your key is lost or exposed, ask an administrator to revoke and replace it. Do not post the key when asking for help. See what we store for API requests.

Authentication

Send your key on every request as an X-API-Key header, or as Authorization: Bearer <key>.

Rate limits

30 prediction requests per 60 seconds per key (/predict and /predict-gui combined). Over the limit returns 429; honor the Retry-After header. The same delay appears in error.details.retry_after_seconds.

POST/predict

JSON request body:

FieldTypeRequiredNotes
item_textstringYesThe full copied item text, exactly as pasted from the game (CTRL+C while hovering it).
leaguestringNoInstalled league ID or exact name (case-insensitive), e.g. forbidden-rites or runes-of-aldur — see GET /leagues for what's currently installed. Omitting it uses the server's configured default league. An explicit value that isn't installed is rejected rather than silently falling back — see errors.
sourcestringNoFree-form label for your own usage tracking; does not affect the response. Use a short, stable slug for your client (for example poe2-companion).
channel_idstringNoDiscord channel id, if calling from a Discord context.
guild_idstringNoDiscord server (guild) id, if applicable; omit for DMs.

Example request

curl -X POST "$STASHSAGE_API_URL/predict" \
  -H "X-API-Key: $STASHSAGE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"item_text": "Item Class: Amulets\nRarity: Rare\n...", "league": "forbidden-rites", "source": "my-tool"}'

Example response — 200 OK

Trimmed; real responses include full modifier and neighbor detail.

{
  "request_id": "18a02c64be4a4b2f9927430956515957",
  "release": {
    "api_version": "0.5.15", "model_version": "0.5.15", "build_date": "2026-09-04",
    "training_data_as_of": "2026-09-03T14:06:02+00:00",
    "model_trained_at": "2026-09-03T14:32:16+00:00"
  },
  "league": { "id": "forbidden-rites", "label": "Forbidden Rites", "defaulted": false },
  "currency_conversions": {
    "divine_to_exalt": 394, "chaos_to_exalt": 40,
    "display": "1d = 394e,  1c = 40e"
  },
  "xgb": {
    "predictions": { "xgb": 3235.6 },
    "bucket": "High", "bucket_low": 1576.0, "bucket_high": 47280.0
  },
  "target_item": {
    "item_name": "Ghoul Touch",
    "mods": [ { "pattern": "+# to maximum Life", "value": 45, "display": "+45 to maximum Life" } ]
  },
  "knn": {
    "summary": { "count": 3, "median": 3100.0, "mean": 3180.5 },
    "neighbors": [
      {
        "item_name": "Ghoul Wrap",
        "price_exalts": 3100.0, "price_display": "3100e/78c/8d", "price_simple": "3100e",
        "mods": [ { "pattern": "+# to maximum Life", "value": 42, "display": "+42 to maximum Life" } ]
      }
    ]
  }
}

Response fields

The example above is trimmed. These are the blocks every 200 response carries. Fields may be added over time, so ignore keys you don't recognise rather than treating them as errors.

FieldNotes
request_idOpaque id for this call. Include it when reporting a problem.
release.api_versionVersion of the StashSage release serving the request. It tracks the overall release — today it mirrors model_version — and is not an independent response-contract version, so a bump does not by itself mean the schema changed.
release.model_versionVersion of the published model bundle the server has loaded.
release.build_dateDate that release was built. This is the build date of the API and model bundle, not the cutoff of the market data behind the models — see model and data freshness.
release.training_data_as_ofWhen the market data behind this prediction was assembled, ISO 8601 UTC. This is the freshness signal to display — see model and data freshness. null when the model that answered has no usable timestamp.
release.model_trained_atWhen that model was trained, ISO 8601 UTC. Usually minutes after training_data_as_of; the gap is training time, not data age. null when unknown.
release.build_commit, release.git_shaOptional build identifiers, present only when the running deployment has them. Handy when reporting a problem; don't depend on them.
league{"id", "label", "defaulted"} — the league this prediction was priced against. defaulted is true when the request omitted league and the server's configured default was used. See GET /leagues for the installed set.
currency_conversionsThe rates this response's display strings were rendered with: divine_to_exalt, chaos_to_exalt (each a whole number of exalts), and a preformatted display line. Read currency conversions before using them for anything but display.
xgb.predictions.xgbModel #1 point estimate, in exalts.
xgb.bucket, xgb.bucket_low, xgb.bucket_highValue band the estimate falls into, with band edges in exalts. bucket_high is null for the open-ended top band.
target_itemThe server's own parse of the item you submitted — name, matched modifier patterns with their values, and computed DPS for weapons. Worth checking when a prediction looks wrong: it shows exactly what the models saw.
knn.summarycount of comparable listings found, plus the median and mean of their prices, in exalts. median and mean are omitted — not null — when no neighbor had a readable price, so count is the only key guaranteed to be present.
knn.neighborsThe comparable listings themselves, nearest first (ascending distance from your item). See neighbor objects for the per-neighbor fields.
xgb_visualPresentation-shaped copy of the estimate for the desktop overlay and Discord embeds: the same prediction, a bucket label prefixed with a colour block, and color_square. Mirrored to the top level as xgb_bucket, xgb_color_hex, and xgb_color_square. Read xgb instead — these are display sugar and change with the UI.
updatesDesktop-updater block, attached only when the deployment has an update manifest configured. Not part of the pricing contract; ignore it.

GET/leagues

Lists the installed leagues you can pass to /predict//predict-gui, and which one is the default. Same X-API-Key authentication as /predict; no request body.

{
  "default_league": "forbidden-rites",
  "leagues": [
    { "id": "forbidden-rites", "label": "Forbidden Rites" },
    { "id": "runes-of-aldur", "label": "Runes of Aldur" }
  ],
  "release": { "api_version": "0.5.17", "model_version": "0.5.17", "build_date": "2026-09-13" }
}

Only usable, fully-loaded leagues are listed — check here rather than hardcoding an id, since which leagues are installed (and which is default) can change between releases.

Neighbor objects

Each entry of knn.neighbors is one comparable listing. /predict and /predict-gui build neighbors with the same serializer, so these fields are identical on both endpoints.

FieldAlways presentNotes
item_nameYesThe listing's item name; an empty string when the source row carried no name.
price_exaltsYesThe listing's price in exalts, as a number. null when the row had no readable price. This is the field to compute on.
price_displayYesThe same price preformatted across all three currencies, "<exalt>e/<chaos>c/<divine>d" (for example 3100e/78c/8d), each rounded to a whole number using currency_conversions. null when the price is unreadable.
price_simpleYesShort form in whichever currency the listing was posted in, e.g. 8d or 3100e. null when the price is unreadable.
modsYesThe modifiers the neighbor was matched on: pattern (the normalized mod text, with # standing in for the value), value, and a rendered display. May be empty. Entries also carry a comparison against the same mod on your item when your item has it.
base_type, icon_url, base_categoryNoPresent only when the item name resolves to a known base in the icon manifest. Absent — not null — otherwise, so test for the key.
dpsNoWeapons only: the computed DPS figures for that neighbor.
stash_nameNoPresent only when the source listing carried one.

Units

Every price and estimate in the response is a plain number of exalts (Exalted Orbs): xgb.predictions.xgb, the bucket edges, knn.summary.median, knn.summary.mean, and neighbor prices alike. Listings posted in divine or chaos are converted to exalts before training and comparison, so exalts are the single canonical unit throughout — there is no per-field currency to inspect. Use currency_conversions to render a value in another currency.

Currency conversions

The rates in currency_conversions come from the training-time sidecar of whichever league's model answered your request — they are not a live market feed, and they only move when that league is retrained and a new release ships. Because each installed league trains independently, the same item can convert at different rates in different leagues — always read currency_conversions from the response you got rather than caching a rate across leagues. They are exactly what every price_display and price_simple string in that same response was rendered with, which is why those strings are always internally consistent with each other. If you need a current divine or chaos price, take it from a live source and apply it to the exalt numbers yourself.

Model and data freshness

Listings are re-scraped and models retrained every few days, per category, and published with a StashSage release. Two timestamps in the release block describe the answer you just got:

  • training_data_as_of — when the feature matrix behind this prediction was assembled from scraped listings. This is the one to show users.
  • model_trained_at — when the model itself was fitted on that matrix, normally minutes later.

Both are per model, not per release: categories retrain independently, so an amulet and a bow answered by the same deployment can legitimately report different dates. Both are also upper bounds — scraping precedes the matrix build, so the newest listing in the training data is somewhat older than the stamp. Neither is an exact market cutoff, and neither should be presented as one.

Either can be null when the model that answered carries no usable timestamp; treat that as "unknown" and fall back to release.build_date, which remains a coarse upper bound on the age of everything in the release. The keys are always present, so null means unknown rather than unsupported.

Versioning and change notice

Because api_version follows the release rather than the response contract, don't use it to gate on schema changes. Build your client to tolerate added fields, and ask in Discord if you want notice ahead of a contract change — the API is best-effort, but we would rather warn integrators than break them.

Errors

Every error response is {"error": {"code", "message", "details"}, "release": {...}}. details is omitted when there is nothing to add; on the codes below it carries request_id. /predict-gui shares /predict's league selection, authentication, and rate limits, so the same codes apply to both.

Statuserror.codeMeaning
400bad_requestitem_text is missing, empty, or could not be parsed as a valid item.
400invalid_leagueAn explicit league value isn't installed, is retired, or is malformed — it never silently falls back to the default. Check GET /leagues for valid ids.
401unauthorizedAPI key is missing, invalid, or revoked.
404no_modelThe item's category has no trained pricing model yet.
429rate_limitedToo many requests for this key in the current window; see retry_after_seconds.
500inference_failedPrediction failed inside the model; include request_id when reporting it.
500internal_errorUnhandled server-side failure. Carries no details, so quote the X-Request-Id header you sent when reporting it.
503league_unavailableleague was omitted and the server has no valid default league configured (for example, multiple leagues installed with none chosen as default). Pass an explicit league from GET /leagues.

Explore DataWiseGuys

Interested in learning more about other DataWiseGuys projects? Check them out below.

SocialSync - Seen us posting on X or Instagram? That was probably SocialSync, our social media automation app, doing the work. Check it out!

Want to brainstorm developing your own app with analytics or machine learning? Reach out to us.