CMO
One answer to “who speaks for us?”
The agents you operate and the partners you’ve hired, published from your own domain and owned by your team. Change agencies, and sellers that check see it on their next refresh.
trust.jsonEarly access · AdCP 3.3
AI agents are starting to buy media, make creative and do business in your company’s name. trust.json is a short file on your own website that names the agents you’ve hired and the agents you operate, so sellers can tell the real ones from impostors.
Nova Brands in-house buyer
buyer.nova-brands.example
Operated by Nova Brands · its own agent
Pinnacle Agency
buyer.pinnacle-agency.example
Hired by Nova Brands · media buying · US & UK · through June 2027
“Nova Motors buying team”
deals.quickmedia.example
Not on Nova Brands’ list
Checked against nova-brands.example/.well-known/trust.json
The problem
When an agent asks a publisher for inventory, it names the brand it’s buying for. That’s one line in a request. Without a public source of truth, sellers fall back on paperwork, email threads and good faith. That’s slow for your real partners and an open door for everyone else.
A reseller books a deal in your name, and you find out when the invoice arrives.
Ads generated for your brand by a team nobody briefed.
Your actual agency waits on letters of authorization while the flight date gets closer.
Who it’s for
CMO
The agents you operate and the partners you’ve hired, published from your own domain and owned by your team. Change agencies, and sellers that check see it on their next refresh.
Global head of media
Give each agency exactly the reach it needs: which brands, which markets, until which date. Sellers confirm the relationship from your file instead of waiting on a letter.
Global head of creative
Creative generation is its own permission, separate from buying. The studio you hired can make work for the brand. A stranger’s claim won’t check out.
How it works
Name the agents you operate yourself, then the agencies and platforms you’ve hired. For each partner, choose what it can do (buy media, generate creative, measure), for which brands, in which countries, and for how long.
The file lives at yourbrand.com/.well-known/trust.json, next to your brand.json. Your domain is the proof: only whoever controls your website can put it there.
When an agent shows up buying for you, the seller confirms who it really is, reads your list, and checks that it’s one of yours, or hired for this brand, market and date.
Brand portfolios
Publish once at your company’s domain. Each brand’s site names the parent company, and the parent lists the brand back. When both sides match, sellers use the parent’s list for every brand in the family.
A sub-brand without its own file isn’t a loophole. If nova-snacks.example never publishes a trust.json, sellers still check Nova Brands’ list. Skipping a brand in your rollout doesn’t leave it exposed.
Beyond advertising
Agents will soon book, buy, negotiate and answer customers in your company’s name. Every time, the other side needs to know the same thing: is this agent really yours, or really working for you? trust.json was built to answer that for any protocol, not just ads.
Commerce
A procurement agent places orders with a supplier. The supplier checks that it runs for your company before it ships.
Customer care
A support agent answers your customers inside a marketplace or messaging app. The platform checks it’s yours, or hired by you.
Travel and expenses
A booking agent reserves flights at your corporate rate. The airline checks your list instead of trusting the claim.
Data and partners
A partner’s agent asks for your data. You check its company against the grants you published.
How it stretches: the file’s core (agents you operate, partners you’ve hired, the limits on each) is protocol-neutral. Each protocol adds its own permissions under its own name, and verifiers ignore the ones they don’t understand. Advertising’s profile is the only one defined today; the examples above show where other protocols can take it.
Stay in control
Add one entry. Limit it to a single brand, a few markets or a fixed end date.
Delete a partner’s entry, or retire one of your own agents. Sellers that check pick up the change on their next refresh. No calls, no letters.
Make your list exclusive, and an agency that isn’t on it gets turned away, whatever it claims.
Your agency or platform can host the file. Your domain still points to it, so the authority stays yours.
Where it works today
trust.json is experimental, and advertising (AdCP 3.3) is the first protocol to use it. It protects you with sellers that check it, and support varies by seller today. Publishing now gives your team one current answer to “who’s authorized?”, and you’re covered as each seller turns checking on.
Ask every seller you work with
“Do you check trust.json before you accept a buy for our brand?”
Then ask them to show you one request they approved and one they turned down.
For ad ops and engineering
What your team needs to publish the file and test it with sellers. Examples use fictional companies on .example domains; replace them with your own domains and real agent origins.
The core is protocol-neutral: agents lists the agents you operate, grants lists the organizations you’ve authorized, and acknowledgements accepts grants made to you. Roles and scopes are namespaced tokens. AdCP defines the adcp: tokens and adcp profile used below; other protocols can define their own, and verifiers ignore namespaces they don’t implement.
Publish /.well-known/brand.json over HTTPS on a domain you control, or publish an authoritative_location pointer to a provider you control. Self-publishing needs no registry signup.
If you use the AgenticAdvertising.org registry, claim your brand with its DNS TXT check. The claim controls your hosted registry entry; your domain’s own publication is what other parties use to find your authoritative record.
Publish grants at https://{your-registrable-domain}/.well-known/trust.json. For a portfolio, publish them at the verified parent’s domain. Each grantee is an organization’s registrable domain.
Here, Nova Brands lets one Pinnacle agent buy media for Nova Motors in the US and UK until mid-2027. This authorizes the agency. It doesn’t say Nova Brands runs the agency’s agent.
https://nova-brands.example/.well-known/trust.json{
"$schema": "https://adcontextprotocol.org/schemas/latest/trust/v1/trust.json",
"exclusive_grants": true,
"grants": [
{
"grantee": "pinnacle-agency.example",
"scopes": ["adcp:media_buying"],
"agents": [{ "url": "https://buyer.pinnacle-agency.example" }],
"profiles": { "adcp": { "brands": ["nova_motors"] } },
"countries": ["US", "GB"],
"valid_until": "2027-06-30T00:00:00Z"
}
]
}
Leave out agents to allow any of the grantee’s agents. Leave out countries and the grant is global; leave out valid_until and it has no published expiry. Set each limit on purpose.
Pinnacle lists the agent origin it runs in its own trust record, with the buying role. That origin serves its Web Bot Auth key directory at /.well-known/http-message-signatures-directory. trust.json carries no signing keys. A hosted platform lists the agents it runs in its own record.
https://pinnacle-agency.example/.well-known/trust.json{
"$schema": "https://adcontextprotocol.org/schemas/latest/trust/v1/trust.json",
"agents": [
{
"url": "https://buyer.pinnacle-agency.example",
"roles": ["adcp:buying"]
}
]
}
One agent per origin; different paths on the same origin are not separate agents. A brand that only delegates can publish grants without running an agent.
With exclusive_grants: true, your grants are the complete list: an enforcing seller rejects any uncovered third-party claim, whatever the activity. Your own agents keep their first-party authority.
Without exclusivity, a seller may still authorize an uncovered claim from its own verified onboarding records. Once your trust record is published, legacy brand.json operator grants stop being a fallback, so move the complete list before you publish.
Ask each seller to demonstrate an authorized request and a rejected one, checking agent, brand, account operator, scope, country and expiry. Account approval, billing and credit checks still apply.
Nova Motors names Nova Brands as its parent, and Nova Brands lists Nova Motors in its portfolio. The seller verifies both, then evaluates grants in Nova Brands’ trust record. With a verified parent, that record is the only record that starts a delegation chain; a child’s own trust record cannot override it.
https://nova-motors.example/.well-known/brand.json{
"$schema": "https://adcontextprotocol.org/schemas/v3/brand.json",
"id": "nova_motors",
"names": [{ "en": "Nova Motors" }],
"house_domain": "nova-brands.example"
}
https://nova-brands.example/.well-known/brand.json{
"$schema": "https://adcontextprotocol.org/schemas/v3/brand.json",
"house": { "domain": "nova-brands.example", "name": "Nova Brands" },
"brand_refs": [
{ "domain": "nova-motors.example", "brand_id": "nova_motors" }
]
}
A one-sided parent claim establishes nothing, and neither does a website redirect or a registry’s inferred corporate hierarchy. A standalone brand omits house_domain and publishes its own trust record. Read the parent/child trust model →
Verify its signature or an established credential mapping. A name or URL in the request is a claim, not proof.
Read its domain-controlled brand.json. Verify a claimed parent against the parent’s portfolio entry.
Read the parent’s or standalone brand’s trust.json. Follow at most two grants to the agent’s operator.
Check activity, brand, countries, dates and any agent restriction before provisioning or spend.
If an agency uses a hosted platform, a chain can run brand → agency → platform. Every grant must cover the request, and the account operator must be the brand, its parent, or the agency. Your own agents can act without a third-party grant when both the agent’s operator and the account operator match the brand or its verified parent. The seller still verifies the agent and its operator listing. Read the grant evaluation rules →
First work out which organization holds authority, then read its record. A missing file on a child domain says nothing about its verified parent’s rules.
| What the seller finds | What it means |
|---|---|
| The authority has never published a record | In AdCP 3.x, a first 404 permits the legacy brand.json path, and verified seller onboarding can also establish authority. Absence never authorizes a caller on its own. |
| A valid record with a matching, active grant | The grant covers the claim, subject to the agent’s authenticated identity, every grant limit, and the seller’s commercial checks. |
| No matching grant in an exclusive record | Reject a third-party request that needs a grant. Naming an approved operator in the request isn’t enough. |
| An uncovered claim, no exclusivity | The seller may rely on its own verified onboarding records, but not on that authority’s legacy brand.json grants. |
| Timeout, server error or malformed record | Authorization is unavailable. Spend fails closed with a retryable error. An outage doesn’t make the brand unprotected. |
| A record that was read before and is now gone | No downgrade to legacy authorization. Deleting the file doesn’t undo adoption, so keep it published and complete. Sellers keep authority history across restarts. |
The lookup at the top of this page reads current public records, follows a verified parent, and shows published agents, grants and limits. It doesn’t authenticate a request, test a seller’s enforcement, or see a seller’s private onboarding approvals. Review these with your agency and sellers:
The builder validates brand.json. The registry viewer shows identity and parent-relationship evidence.
Open the brand.json builder →Check the JSON against the experimental schema, then confirm its meaning with your seller. A valid file isn’t proof of a valid permission chain.
Open the experimental schema →Publisher inventory permissions shown in the brand viewer come from adagents.json, a separate, sell-side relationship.
Claiming protects control of your registry entry. Stopping impersonation at the point of sale also needs a file on your domain, accurate grants, authenticated agents and a seller that checks. A registry badge or a brand name in a request is not permission to buy.
No. A verified parent publishes grants for all its brands in one record. The organization that runs an agent lists it in its own record. A brand that only delegates doesn’t need to run an agent or publish signing keys.
Remove or narrow the grant in your record. To retire an agent you run, remove its origin from your agents list. Keep the file published. Sellers recheck on their freshness schedule, so revocation lands within their cache lifetime rather than instantly. It doesn’t by itself cancel live buys or suspend an account.
Yes. Publish an authoritative_location pointer at your own domain’s well-known trust.json location. Verifiers follow one pointer and no HTTP redirects. You stay the authority, so keep control of the domain and the hosted contents.
An acknowledgement references a grant another organization published: its grantor, agent and source. The terms stay in the grantor’s record. An acknowledgement can’t authorize its author and doesn’t replace the seller’s grant checks.
It’s an experimental AdCP 3.3 surface, and SDK and seller support vary. The document name, path and schema may change. Confirm support and test the checks with each seller before relying on them. Existing 3.x integrations continue under their documented legacy rules until they adopt the trust record.
Stewarded by AgenticAdvertising.org.