# ads.txt & app-ads.txt Checker + sellers.json (`scrapemint/ads-txt-checker`) Actor

Validate ads.txt and app-ads.txt in bulk: every seller line parsed, DIRECT vs RESELLER counts, ad systems, OWNERDOMAIN/MANAGERDOMAIN, spec errors and duplicates, plus optional sellers.json verification of each seller id. No API key.

- **URL**: https://apify.com/scrapemint/ads-txt-checker.md
- **Developed by:** [Ken M](https://apify.com/scrapemint) (community)
- **Categories:** Marketing, Developer tools, SEO tools
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-usage

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## ads.txt & app-ads.txt Checker + sellers.json

Check the ads.txt or app-ads.txt file of hundreds of publishers in one run. Every line is parsed and validated against the IAB Tech Lab spec, and you get DIRECT vs RESELLER counts, the ad systems each publisher works with, OWNERDOMAIN and MANAGERDOMAIN, syntax errors and duplicate lines. Turn on seller verification to check every seller id against each ad system's public sellers.json.

No API key, no login, no browser.

### Who uses it

- **Publishers and ad ops**: audit your own ads.txt for errors, duplicates and sellers that are no longer listed
- **SSPs and ad networks**: find publishers that list you, or that list competitors but not you
- **App developers**: validate app-ads.txt for mobile and CTV apps
- **Ad-tech sales teams**: build lead lists of publishers by ad stack and size of their monetization setup
- **Brand safety and fraud analysts**: spot unauthorized resellers and seller type mismatches

### What you get

One row per file:

- `found`, `finalUrl`, `sizeBytes`, `lastModified`
- `totalEntries`, `directEntries`, `resellerEntries`, `adSystemCount`
- `topAdSystems`: `[{ adSystem, direct, reseller }]`, and `hasGoogleDirect`
- `ownerDomain`, `managerDomain`, `contact`, `subdomains`, `inventoryPartnerDomains`
- `errorCount`, `duplicateCount`, `errors` (line number, text and what is wrong)
- `entries`: every line as `{ adSystem, sellerId, relationship, certId }`
- With verification on: each entry gains `sellerVerified`, `sellerType`, `sellerName`, `sellerDomain` and `typeMismatch` (DIRECT listed for an INTERMEDIARY seller, or RESELLER for a PUBLISHER), and the row gets a `sellerVerification` summary

A soft 404 (an HTML page served at /ads.txt) is reported as not found.

### Example input

```json
{
  "domains": ["cnn.com", "nytimes.com", "theguardian.com"],
  "fileType": "ads.txt",
  "verifySellers": true
}
```

### Example output

```json
{
  "domain": "cnn.com",
  "found": true,
  "totalEntries": 821,
  "directEntries": 221,
  "resellerEntries": 600,
  "adSystemCount": 136,
  "hasGoogleDirect": true,
  "ownerDomain": "wbd.com",
  "errorCount": 2,
  "duplicateCount": 125,
  "sellerVerification": { "checked": 336, "found": 315, "notFound": 21, "typeMismatch": 45 }
}
```

### Pricing

Pay per file found and parsed. Missing files, unreachable domains and invalid inputs are free, and the first 3 files of every run are free.

### Notes

- Verification downloads each ad system's sellers.json once per run. Google's is about 100 MB, so the first verified run takes longer. `maxSellersFiles` limits how many ad systems are verified (most-used first).
- Some ad systems block automated downloads of their sellers.json; their entries are marked unverifiable rather than not found.
- See what else a publisher's site runs on with [Website Tech Stack Detector](https://apify.com/scrapemint/website-tech-stack-detector).

# Actor input Schema

## `domains` (type: `array`):

Publisher domains (for ads.txt) or app developer domains (for app-ads.txt), e.g. cnn.com.

## `fileType` (type: `string`):

ads.txt for websites, app-ads.txt for mobile and CTV apps, or both.

## `verifySellers` (type: `boolean`):

Download each ad system's sellers.json once and check every seller id: found or not, seller type vs. DIRECT/RESELLER, seller name and domain. Slower: big files like Google's take 10-30 s to load.

## `maxSellersFiles` (type: `integer`):

How many ad systems to verify, most-used first. Entries beyond this are marked unverifiable.

## `includeEntries` (type: `boolean`):

Add the parsed entries (up to 3,000 per file) to each row. Turn off for summary-only rows.

## `concurrency` (type: `integer`):

Domains checked in parallel.

## `maxRows` (type: `integer`):

Cap on files checked. Controls cost.

## Actor input object example

```json
{
  "domains": [
    "cnn.com",
    "nytimes.com",
    "theguardian.com"
  ],
  "fileType": "ads.txt",
  "verifySellers": false,
  "maxSellersFiles": 25,
  "includeEntries": true,
  "concurrency": 10,
  "maxRows": 5000
}
```

# Actor output Schema

## `results` (type: `string`):

One row per ads.txt / app-ads.txt file: counts, ad systems, errors, seller verification, entries.

## `summary` (type: `string`):

Files found vs missing, most common ad systems, sellers.json files loaded.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "domains": [
        "cnn.com",
        "nytimes.com",
        "theguardian.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapemint/ads-txt-checker").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "domains": [
        "cnn.com",
        "nytimes.com",
        "theguardian.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("scrapemint/ads-txt-checker").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "domains": [
    "cnn.com",
    "nytimes.com",
    "theguardian.com"
  ]
}' |
apify call scrapemint/ads-txt-checker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapemint/ads-txt-checker"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/DRcgDdDCxbyzYZ5aK/builds/PusCW9qT71fhDhBci/openapi.json
