> WEVERSE COMPANY Inc. publishes 1 app in this index that use the app-ads.txt at weverse.io; the file scores 66/100 (C). Every seller line checked against the ad systems' sellers.json.

Source: https://appsupplyindex.com/publisher/weverse-io · Updated: 2026-11-16 · License: CC BY 4.0 (App Supply Index)

---
C66 / 100

# WEVERSE COMPANY Inc.

weverse.io/app-ads.txt · 1 app
· Android + iOS · 103 seller lines · checked Nov 16, 2026

**5 lines to fix.** Two steps take this file from
C 66 to B 86.

103 seller lines in [weverse.io/app-ads.txt](https://weverse.io/app-ads.txt);
69 could be checked against the ad systems' sellers.json. Main finding: DIRECT lines inconsistent with public data.

app-ads.txtLines from steps 1–2

+OWNERDOMAIN=<your company domain>Add this line, with the domain your company uses in sellers.json.

49teads.tv, 13576, DIRECT, 15a9c44f6d26cbe1Confirm with the partner: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 100 different companies. If the account isn't yours, use RESELLER.

66onetag.com, 5adaad445a0a050, DIRECTConfirm with the partner: the same account is marked DIRECT by 99 different companies. If the account isn't yours, use RESELLER.

67onetag.com, 5adaad445a0a050-OB, DIRECTConfirm with the partner: the same account is marked DIRECT by 99 different companies. If the account isn't yours, use RESELLER.

+ 2 more DIRECT lines to confirm

## What to change

Easiest first. Points are estimates, assuming every line in a step is fixed.

1. Add OWNERDOMAIN=<your company domain> to the file.+2 → 68
2. Confirm 5 DIRECT lines with the partners that supplied them; use RESELLER where the account isn't yours.+18 → B 86
3. Ask partners about 12 seller IDs missing from their sellers.json; remove lines for closed accounts.+14 → A 100

[Re-check now](https://appsupplyindex.com/check?app=https%3A//apps.apple.com/us/app/id1456559188)

## Findings

Each finding lists the exact lines involved. Findings are automated observations of public files as of
Nov 16, 2026. They describe file contents, not the intent or conduct of any company.

warning

### DIRECT lines inconsistent with public data

5
−18 pts

The IAB ads.txt specification: "A value of ‘DIRECT’ indicates that the Publisher (content owner) directly controls the account." For these lines, either the ad system's own sellers.json lists the account as INTERMEDIARY, or the same account is marked DIRECT in the files of 3 or more companies with different owner domains. Either way, the public data does not support the DIRECT label. Buyers that use DIRECT labels in supply-path decisions may treat these lines differently.

**How to fix**Use DIRECT only for accounts your company controls. Confirm with each partner whether the account is yours; if it isn't, the specification calls for RESELLER.
[Full guide →](https://appsupplyindex.com/fix/inconsistent-direct)

Evidence (5)

```
line 49     teads.tv, 13576, DIRECT, 15a9c44f6d26cbe1
             → observed: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 100 different companies  name in sellers.json: Premium Publicidade e Marketing Ltda  domain in sellers.json: premiumads.com.br
line 66     onetag.com, 5adaad445a0a050, DIRECT
             → observed: the same account is marked DIRECT by 99 different companies
line 67     onetag.com, 5adaad445a0a050-OB, DIRECT
             → observed: the same account is marked DIRECT by 99 different companies
line 77     criteo.com, B-064291, DIRECT, 9fac4a4a87c2a44f
             → observed: the same account is marked DIRECT by 99 different companies
line 78     themediagrid.com, DKRL8Y, DIRECT, 35d5010d7789b49d
             → observed: the same account is marked DIRECT by 98 different companies
```

warning

### Seller IDs not listed in the ad system's sellers.json

12
−14 pts

The ad system's current sellers.json doesn't list these accounts, so buyers that validate the chain can't match them. Common causes are closed accounts or former partners.

**How to fix**Ask each partner whether the account is still active and request their current lines; remove lines for closed accounts.
[Full guide →](https://appsupplyindex.com/fix/seller-id-not-in-sellers-json)

Evidence (12)

```
line 46     pubmatic.com, 156378, RESELLER, 5d62403b186f2ace
             → sellers_json: https://pubmatic.com/sellers.json
line 59     themediagrid.com, 2BYX51, RESELLER, 35d5010d7789b49d
             → sellers_json: https://themediagrid.com/sellers.json
line 62     rubiconproject.com, 22824, RESELLER, 0bfd66d529a55807
             → sellers_json: https://rubiconproject.com/sellers.json
line 63     openx.com, 539372716, RESELLER, 6a698e2ec38604c6
             → sellers_json: https://openx.com/sellers.json
line 64     openx.com, 539417470, RESELLER, 6a698e2ec38604c6
             → sellers_json: https://openx.com/sellers.json
line 65     openx.com, 542117415, RESELLER, 6a698e2ec38604c6
             → sellers_json: https://openx.com/sellers.json
line 78     themediagrid.com, DKRL8Y, DIRECT, 35d5010d7789b49d
             → sellers_json: https://themediagrid.com/sellers.json
line 84     improvedigital.com, 1969, RESELLER
             → sellers_json: https://improvedigital.com/sellers.json
line 95     smartadserver.com, 4012, RESELLER
             → sellers_json: https://smartadserver.com/sellers.json
line 96     smartadserver.com, 4071, RESELLER
             → sellers_json: https://smartadserver.com/sellers.json
line 97     smartadserver.com, 4073, RESELLER
             → sellers_json: https://smartadserver.com/sellers.json
line 98     smartadserver.com, 4072, RESELLER
             → sellers_json: https://smartadserver.com/sellers.json
```

info

### No OWNERDOMAIN declared

1
−2 pts

app-ads.txt 1.1 recommends OWNERDOMAIN so buyers can match DIRECT accounts to the owner.

**How to fix**Add OWNERDOMAIN=<your company domain> to the file.
[Full guide →](https://appsupplyindex.com/fix/missing-ownerdomain)

info

### Ad systems whose sellers.json we couldn't read

19

We couldn't read a sellers.json for these ad systems at crawl time (no file, invalid JSON, empty, or automated access refused), so these lines weren't verified. No points are deducted.

**How to fix**Ask the partner to publish sellers.json; until then buyers can't verify that path.
[Full guide →](https://appsupplyindex.com/fix/sellers-json-not-available)

Evidence (19)

```
line 2      facebook.com, 1351773517098183, DIRECT, c3e20eee3f780d68
             → sellers_json: robots.txt of facebook.com disallows crawlers
line 6      contextweb.com, 562615, RESELLER, 89ff185a4c4e857c
             → sellers_json: robots.txt of projects.contextweb.com disallows crawlers
line 7      gamaigroup.com, 423056, RESELLER
             → sellers_json: file is not valid JSON
line 9      indexexchange.com, 211341, RESELLER, 50b1c356f2c5c8fc
             → sellers_json: robots.txt of cdn.indexexchange.com disallows crawlers
line 28     sharethrough.com, bXzzb1bR, RESELLER, d53b998a7bd4ecd2
             → sellers_json: robots.txt of sharethrough.com disallows crawlers
line 29     sharethrough.com, NNB0Zl76, RESELLER, d53b998a7bd4ecd2
             → sellers_json: robots.txt of sharethrough.com disallows crawlers
line 30     sharethrough.com, UbYLkrys, RESELLER, d53b998a7bd4ecd2
             → sellers_json: robots.txt of sharethrough.com disallows crawlers
line 37     yieldmo.com, 3591550211052216798, RESELLER, 6a92c77cfc3d2258
             → sellers_json: bot-check or captcha page (HTTP 202)
line 50     appnexus.com, 9794, RESELLER, f5ab79cb980f11d1
             → sellers_json: HTTP 403 to automated requests
line 68     advertising.com, 28246, RESELLER
             → sellers_json: HTTP 404
line 72     yahoo.com, 58905, RESELLER, e1a5b5b6e3255540
             → sellers_json: HTTP 429 to automated requests
line 73     aol.com, 58905, RESELLER, e1a5b5b6e3255540
             → sellers_json: HTTP 404
line 74     appnexus.com, 13099, RESELLER
             → sellers_json: HTTP 403 to automated requests
line 79     aol.com, 55681, RESELLER, e1a5b5b6e3255540
             → sellers_json: HTTP 404
line 80     yahoo.com, 55681, RESELLER, e1a5b5b6e3255540
             → sellers_json: HTTP 429 to automated requests
line 81     aol.com, 55032, RESELLER, e1a5b5b6e3255540
             → sellers_json: HTTP 404
line 82     yahoo.com, 55032, RESELLER, e1a5b5b6e3255540
             → sellers_json: HTTP 429 to automated requests
line 91     appnexus.com, 1019, RESELLER, f5ab79cb980f11d1
             → sellers_json: HTTP 403 to automated requests
line 102    appnexus.com, 3703, RESELLER, f5ab79cb980f11d1
             → sellers_json: HTTP 403 to automated requests
```

## Apps

1 app in this index; they all list a developer website on weverse.io, so buyers read this
app-ads.txt for all of them. 1 is in this week's US charts.

| App | Genre | Store | In the charts |
| --- | --- | --- | --- |
| [Weverse: Connect with Artists](https://appsupplyindex.com/app/ios-1456559188) | Social Networking | iOS + Android | #54 |

## About this file

app-ads.txt
:   <https://weverse.io/app-ads.txt> · 200

Score
:   C 66/100 · 103 lines · 69 checked against sellers.json

Grouping
:   One file: every app whose store listing points to weverse.io.
    Store names alone never group publishers.

Checked
:   Nov 16, 2026

### Is this your file?

Changed it? Check any of these apps live; this page updates weekly.
Think something here is wrong? [Request a correction](https://appsupplyindex.com/methodology#corrections).

[Check an app](https://appsupplyindex.com/check)
