Ad system
hyperplay.ai
hyperplay.ai appears only as a RESELLER: 17 app-ads.txt files. We found no readable sellers.json for hyperplay.ai, so none of the 17 lines naming it can be checked.
- Apps declaring it
- 288
- Sellers in sellers.json
- 0
- Lines verified
- —
- Lines with errors
- 0
- Avg. supply path score
- 46.2 / 100
0 DIRECT · 288 RESELLER
Invalid
no line checked yet
17 lines in total
295 apps scored
App counts, the sellers.json breakdown and the directory ranking are as of , recomputed daily (the same numbers as the directory). Line counts are recounted every 10 minutes. sellers.json last read 12 October 2026. The supply path score sums up how short and clean the declared paths are, 0 to 100 (how it is computed).
How to add hyperplay.ai to app-ads.txt
One line per account, in the app-ads.txt at the root of the domain your App Store and Google Play listings name as the developer website.
hyperplay.ai, YOUR_ACCOUNT_ID, DIRECT
hyperplay.ai, YOUR_ACCOUNT_ID, RESELLER- Field 1:
hyperplay.ai, the domain hyperplay.ai uses in app-ads.txt. - Field 2: your account ID with hyperplay.ai. It must equal the
seller_idin hyperplay.ai's sellers.json. - Field 3: DIRECT if you hold the account, RESELLER if a partner holds it and sells your inventory. DIRECT vs RESELLER
- Field 4 (optional): a certification authority ID. Most lines naming hyperplay.ai carry none, or different ones, so we do not suggest one.
sellers.json at a glance
- Status
- Invalid
- Sellers listed
- 0
- Confidential
- 0 (0%)
- Passthrough
- 0
- Removed, last 30 days
- 0
- Last read
- Oct 12, 2026
Cross-check of lines naming hyperplay.ai
- Verified 0
- Seller ID not found 0
- DIRECT but intermediary 0
- RESELLER but publisher 0
- Seller type BOTH 0
- Confidential seller 0
- No sellers.json 17
- Unchecked 0
Every line naming hyperplay.ai is looked up in its sellers.json. What each status means
Common errors with hyperplay.ai lines
-
No sellers.json
17 lines
hyperplay.ai has no sellers.json we can read, so these lines cannot be checked by anyone.
Apps that declare hyperplay.ai
| App | Store | Relationship | Status |
|---|---|---|---|
| iOS | RESELLER | Live | |
| iOS | RESELLER | Live | |
| iOS | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| iOS | RESELLER | Live | |
| Android | RESELLER | Live | |
| iOS | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| iOS | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| iOS | RESELLER | Live |
Questions about hyperplay.ai
Does hyperplay.ai publish a sellers.json?
There is a file, but it is not valid sellers.json (last read 12 October 2026), so lines naming hyperplay.ai cannot be checked against it.
How many apps declare hyperplay.ai in app-ads.txt?
288 apps in Stoqlab's data (delisted apps included) declare hyperplay.ai: 0 with at least one DIRECT line and 288 with at least one RESELLER line, across 17 app-ads.txt files, as of 13 October 2026 (recounted daily).
Not sure whether your line should say DIRECT or RESELLER? DIRECT vs RESELLER in app-ads.txt
Sources: the public app-ads.txt files of tracked apps and the sellers.json of hyperplay.ai. Something wrong? Tell us.