Ad system
nexverse.ai
Most of the 49,495 apps that declare nexverse.ai reach it through a reseller: 93% have a RESELLER line, 48% a DIRECT one (5,232 files, 3,745 of them through mobupps.com's account). Of 19,395 lines checked against its sellers.json (860 sellers), 86% match, 0.4% name an unlisted account and 10% declare the wrong seller type.
- Apps declaring it
- 49,495
- Sellers in sellers.json
- 860
- Lines verified
- 86%
- Lines with errors
- 2,086
- Avg. supply path score
- 50.3 / 100
23,914 DIRECT · 46,161 RESELLER
0% confidential
16,943 of 19,695 checked lines
19,695 lines in total
50,779 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 nexverse.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.
nexverse.ai, YOUR_ACCOUNT_ID, DIRECT
nexverse.ai, YOUR_ACCOUNT_ID, RESELLER
- Field 1:
nexverse.ai, the domain nexverse.ai uses in app-ads.txt. - Field 2: your account ID with nexverse.ai. It must equal the
seller_idin nexverse.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 nexverse.ai carry none, or different ones, so we do not suggest one.
sellers.json at a glance
- Status
- Published
- Sellers listed
- 860
- Confidential
- 0 (0%)
- Passthrough
- 0
- Removed, last 30 days
- 0
- Last read
- Oct 12, 2026
- PUBLISHER668
- INTERMEDIARY141
- BOTH51
Cross-check of lines naming nexverse.ai
- Verified 16,943
- Seller ID not found 86
- DIRECT but intermediary 663
- RESELLER but publisher 1,337
- Seller type BOTH 666
- Confidential seller 0
- No sellers.json 0
- Unchecked 0
Every line naming nexverse.ai is looked up in its sellers.json. What each status means
Common errors with nexverse.ai lines
-
RESELLER but publisher
1,337 lines
If the account is yours, declare it DIRECT. If a partner holds it, ask nexverse.ai why the account is listed as PUBLISHER.
-
Seller type BOTH
666 lines
The account is listed as BOTH, so sellers.json alone cannot tell a buyer which relationship applies. Nothing to fix on your side; buyers usually look at the seller's domain.
-
DIRECT but intermediary
663 lines
If a partner holds this account and resells your inventory, the line should say RESELLER. If the account is yours, ask nexverse.ai to list it as PUBLISHER.
-
Seller ID not found
86 lines
Ask nexverse.ai for the account ID it lists for you in its sellers.json, correct the line, or remove it if you no longer work with them. Buyers that check sellers.json drop these paths.
Intermediaries most declared as RESELLER
Accounts on nexverse.ai that its sellers.json lists as INTERMEDIARY or BOTH, by the number of app-ads.txt files declaring them. Confidential sellers are left out.
| Seller domain | Type | Files |
|---|---|---|
| mobupps.com | INTERMEDIARY | 3,745 |
| bidfuse.com | INTERMEDIARY | 3,691 |
| adscholars.com | INTERMEDIARY | 2,542 |
| rtb-useast.milkywase.com | INTERMEDIARY | 1,086 |
| bidmachine.io | INTERMEDIARY | 627 |
| vdo.ai | INTERMEDIARY | 560 |
| adbite.com | INTERMEDIARY | 384 |
| gadsme.com | BOTH | 376 |
Apps that declare nexverse.ai
| App | Store | Relationship | Status |
|---|---|---|---|
| Android | RESELLER | Live | |
| Android | DIRECT + RESELLER | Live | |
| Android | DIRECT + RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | DIRECT + RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | DIRECT | Live | |
| Android | RESELLER | Live | |
| Android | DIRECT + RESELLER | Live | |
| Android | DIRECT + RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | DIRECT + RESELLER | Live | |
| Android | DIRECT + RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live |
Questions about nexverse.ai
Does nexverse.ai publish a sellers.json?
Yes. Its file at https://nexverse.ai/sellers.json listed 860 sellers when we last read it on 12 October 2026: 668 publishers, 141 intermediaries and 51 listed as both; 0% are confidential.
How many apps declare nexverse.ai in app-ads.txt?
49,495 apps in Stoqlab's data (delisted apps included) declare nexverse.ai: 23,914 with at least one DIRECT line and 46,161 with at least one RESELLER line, across 5,232 app-ads.txt files, as of 12 October 2026 (recounted daily).
Why do nexverse.ai lines fail verification?
Of 19,695 lines naming nexverse.ai, 2,086 contradict its sellers.json. The most common case is "RESELLER but publisher", on 1,337 lines. If the account is yours, declare it DIRECT. If a partner holds it, ask nexverse.ai why the account is listed as PUBLISHER.
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 nexverse.ai. Something wrong? Tell us.