Before a buying agent trusts an offer, it asks one question: is this selling agent allowed to sell this publisher's inventory? The answer lives on the publisher's own website, in a file called adagents.json. No file, or a file that does not list the agent, and a careful buyer walks away.

It takes about ten minutes to get right.

Where it lives

One file per domain you sell, at a fixed address:

https://your-site.com/.well-known/adagents.json

If you sell several sites or apps, each domain gets its own file, or points to a shared one. The address must answer over HTTPS, without a login, and return JSON.

What goes in it

The heart of the file is a list of authorised agents. Each entry names the agent's address and says, in plain words, what it may sell.

{
  "authorized_agents": [
    {
      "url": "https://fanera.getoderra.com",
      "authorized_for": "Streaming TV, podcast and city screens sold direct by Northlight Media (an example publisher)"
    }
  ]
}

Keep authorized_for short and true. It is read by people as well as by agents.

Five checks before you publish

  1. The address answers. Open it in a browser: you should see the JSON, not a 404 or a login page.
  2. Every domain is covered. A buyer checks the domain the inventory runs on, not your company site.
  3. The agent's address is exact. A typo in url means the agent is not authorised.
  4. Only the agents you mean. Remove agents you no longer work with. An old entry is an open door.
  5. Someone owns it. Name the person who updates the file when you add a channel or change agents.

What Fanera does for you

Fanera, the selling agent from Oderra, writes the entry for you, checks that every site you declared points to it, and tells you when one stops answering. You still publish the file on your own domain: that is what makes it proof.

Why it matters

Agents move fast. The file is what keeps that speed safe for both sides: the buyer knows who it is dealing with, and you know nobody else can sell your inventory in your name.