Ad system
metabits.cc
metabits.cc is the domain an ad system uses in app-ads.txt and ads.txt files. 41 apps in our data declare it.
- Apps declaring it
- 41
- Sellers in sellers.json
- 0
- Lines verified
- —
- Lines with errors
- 0
- Avg. supply path score
- 49.3 / 100
41 DIRECT · 0 RESELLER
Not found
no line checked yet
21 lines in total
41 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 metabits.cc 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.
metabits.cc, YOUR_ACCOUNT_ID, DIRECT
metabits.cc, YOUR_ACCOUNT_ID, RESELLER- Field 1:
metabits.cc, the domain metabits.cc uses in app-ads.txt. - Field 2: your account ID with metabits.cc. It must equal the
seller_idin metabits.cc'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 metabits.cc carry none, or different ones, so we do not suggest one.
sellers.json at a glance
- Status
- Not found
- Sellers listed
- 0
- Confidential
- 0 (0%)
- Passthrough
- 0
- Removed, last 30 days
- 0
- Last read
- Oct 11, 2026
Cross-check of lines naming metabits.cc
- 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 21
- Unchecked 0
Every line naming metabits.cc is looked up in its sellers.json. What each status means
Common errors with metabits.cc lines
-
No sellers.json
21 lines
metabits.cc has no sellers.json we can read, so these lines cannot be checked by anyone.
Apps that declare metabits.cc
| App | Store | Relationship | Status |
|---|---|---|---|
| Android | DIRECT | Live | |
| Android | DIRECT | Live | |
| Android | DIRECT | Live | |
| Android | DIRECT | Live | |
| Android | DIRECT | Live | |
| Android | DIRECT | Live | |
| Android | DIRECT | Live | |
| iOS | DIRECT | Live | |
| Android | DIRECT | Live | |
| Android | DIRECT | Live | |
| iOS | DIRECT | Live | |
| Android | DIRECT | Live | |
| Android | DIRECT | Live | |
| iOS | DIRECT | Live | |
| Android | DIRECT | Live | |
| Android | DIRECT | Live | |
| Android | DIRECT | Live | |
| iOS | DIRECT | Live | |
| iOS | DIRECT | Live | |
| iOS | DIRECT | Live |
Questions about metabits.cc
How do I add metabits.cc to app-ads.txt?
Add one line for each account metabits.cc gives you: "metabits.cc, YOUR_ACCOUNT_ID, DIRECT". Use DIRECT when you hold the account yourself and RESELLER when a partner holds it and sells your inventory through metabits.cc. The account ID must be the seller_id metabits.cc lists for you in its sellers.json; metabits.cc 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 metabits.cc publish a sellers.json?
We found no sellers.json at https://metabits.cc/sellers.json when we last looked on 11 October 2026. Lines naming metabits.cc cannot be checked against it.
How many apps declare metabits.cc in app-ads.txt?
41 apps in Stoqlab's data (delisted apps included) declare metabits.cc: 41 with at least one DIRECT line and 0 with at least one RESELLER line, across 21 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 metabits.cc. Something wrong? Tell us.