Ad system
hyperplay.ai
hyperplay.ai is the domain an ad system uses in app-ads.txt and ads.txt files. 250 apps in our data declare it.
- Apps declaring it
- 250
- Sellers in sellers.json
- 0
- Lines verified
- —
- Lines with errors
- 0
- Avg. supply path score
- 46.5 / 100
0 DIRECT · 250 RESELLER
Invalid
no line checked yet
14 lines in total
250 apps scored
Apps and lines are recounted every 10 minutes. The sellers.json breakdown and the directory ranking are as of , recomputed daily. sellers.json last read 11 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 11, 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 14
- 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
14 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 |
|---|---|---|---|
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live |
Questions about hyperplay.ai
How do I add hyperplay.ai to app-ads.txt?
Add one line for each account hyperplay.ai gives you: "hyperplay.ai, YOUR_ACCOUNT_ID, DIRECT". Use DIRECT when you hold the account yourself and RESELLER when a partner holds it and sells your inventory through hyperplay.ai. The account ID must be the seller_id hyperplay.ai lists for you in its sellers.json; hyperplay.ai will give it to you. Put the file at the root of the domain named as your developer website in the App Store and Google Play listings.
Does hyperplay.ai publish a sellers.json?
There is a file, but it is not valid sellers.json (last read 11 October 2026), so lines naming hyperplay.ai cannot be checked against it.
How many apps declare hyperplay.ai in app-ads.txt?
250 apps in Stoqlab's data (delisted apps included) declare hyperplay.ai: 0 with at least one DIRECT line and 250 with at least one RESELLER line, across 14 app-ads.txt files. Counts are recomputed daily.
What is the difference between DIRECT and RESELLER?
DIRECT means the publisher owns the account; RESELLER means an intermediary sells the inventory on the publisher's behalf. DIRECT lines should match a PUBLISHER entry in the network's sellers.json, RESELLER lines an INTERMEDIARY entry.
Sources: the public app-ads.txt files of tracked apps and the sellers.json of hyperplay.ai. Something wrong? Tell us.