# trust.json > Experimental, protocol-neutral standard for publishing which agents an organization runs and who may act on its behalf. Stewarded by AgenticAdvertising.org. AdCP 3.3 defines the advertising profile. ## Claim and publish Self-publish brand.json and trust.json over HTTPS on domains you control; no registry signup is required. A DNS TXT claim in the AgenticAdvertising.org registry controls its hosted entry. Other parties discover authority through your own domain publication or authoritative_location pointer. Claiming a registry entry alone does not enable transaction protection. Publish trust.json at https://{registrable-domain}/.well-known/trust.json. A hosted trust record may use one authoritative_location document hop, with no HTTP redirects. The original organization remains the authority. ## Authenticate, resolve, and authorize The seller authenticates the actual calling agent using a signature or established credential mapping. Agent and operator names asserted in a request are not proof of identity. Resolve the brand through domain-controlled brand.json. For a distributed brand, verify both the child house_domain and the parent brand_refs entry. A one-sided claim or inferred registry hierarchy does not establish parent authority. Evaluate grants from the verified parent trust record, or from the standalone brand record. A delegation chain of at most two grants must reach the authenticated agent operator. The second grant comes from its grantor's own trust.json. The account operator must be the brand, the parent organization, or the grantee of the first grant. Every grant must cover the request. The protocol permits implicit authority when the signer operator and account operator both match the brand or its verified parent. No third-party grant is needed in that case; agent identity and operator listing checks still apply. ## Agents and grants agents[] lists origins operated by the publishing organization and their roles, such as adcp:buying. One agent per origin; different paths are not separate identities. Under Web Bot Auth, signing keys live at the agent origin in /.well-known/http-message-signatures-directory. trust.json carries no signing keys or jwks_uri. grants[] names grantee registrable domains. Check scopes, profiles.adcp.brands, countries, valid_from, valid_until, and optional agents[] origin narrowing. Omitted agent narrowing permits the grantee agents broadly; omitted countries are global; omitted validity bounds leave that end of the window unbounded. exclusive_grants: true makes grants exhaustive. Reject every uncovered third-party claim, whatever its scope. Implicit first-party authority still applies. Without exclusivity an uncovered claim may be authorized by verified seller onboarding records. acknowledgements[] references grants another organization published. Terms remain with the grantor; an acknowledgement alone does not establish permission. ## Parent domains and missing records A child with a verified parent does not need its own trust.json for the parent grants to apply. The parent record is the only record that starts a delegation chain; a child record cannot override it. For an authority that has never published trust.json, a first 404 permits legacy brand.json authorization in AdCP 3.x. Missing publication does not independently authorize a caller. Once the authority trust record is read, legacy brand.json grants are no longer a fallback. Nonexclusive uncovered claims use seller policy instead. Migrate the complete grant list before publishing. Timeouts, server errors, malformed records, and deletion after publication are not an unprotected state. Spend fails closed with a retryable availability outcome. Never downgrade a previously published authority to legacy authorization; seller authority history must survive restarts. ## Inspect and revoke Review the verified authority, operator agent listings, grant recipients, brand/country/activity/time limits, exclusivity, and freshness. Public files cannot reveal private seller onboarding approvals. Use the homepage domain lookup to inspect current public trust records, including a verified parent record, published agent origins, grants, scope limits, and validity windows. A missing child record does not bypass its parent. Missing files, unavailable/invalid records, and unverified parent claims are separate outcomes. The lookup does not authenticate requests or check seller enforcement, private onboarding approvals, or a seller adoption history. Publisher adagents.json sales permissions are a separate relationship. Revoke by removing or narrowing grants, or removing an agent origin from its operator listing. Keep the record published. Changes take effect on the seller freshness schedule, within the applicable cache lifetime. Revoking agent access does not itself cancel live buys or suspend the account. ## Adoption and references Publishing alone does not enable enforcement at every seller. trust.json is experimental; its document name, path, and schema may change. SDK and seller support vary. Confirm support and test both allowed and denied requests with each seller before relying on protection. Seller billing, credit, and account approval still apply. - [Brand protection guide](https://trustjson.org/#publish) - [Parent and child brands](https://trustjson.org/#portfolio) - [Missing records](https://trustjson.org/#missing-records) - [Check your setup](https://trustjson.org/#check) - [Public domain lookup](https://trustjson.org/#lookup): enter a domain; results include a link to claim the brand - Public read API: GET https://trustjson.org/api/trust/lookup?domain=yourbrand.com. Only confirmed missing files report not_found; unavailable/invalid records and unverified parent relationships are separate states. This API reports public declarations, not a transaction authorization decision. - [Reference](https://docs.adcontextprotocol.org/docs/reference/trust-json) - [Grant evaluation](https://docs.adcontextprotocol.org/docs/building/by-layer/L2/accounts-and-agents#grants-in-trust-records-experimental) - [Identity and migration](https://docs.adcontextprotocol.org/docs/reference/migration/agent-identity-3-3) - [Experimental development schema](https://adcontextprotocol.org/schemas/latest/trust/v1/trust.json) - [Build or validate brand.json](https://brandjson.org/builder) - [Experimental status](https://docs.adcontextprotocol.org/docs/reference/experimental-status)