Docs / Capability guide
Supply transparency, verification and privacy
Verify seller authorization and apply consent and invalid-traffic policy.
All capabilities · Related guide · Agent prompt for this capability
When to use this example
Before enforcing seller authorization, check that your inventory records and published supply documents describe the same relationships. This helps distinguish a stale or missing document from an unauthorized selling path.
What the example gives you
The inspector exports inventory domains and demand routes as review inputs. Document verification, seller checks and privacy-policy tests use the API operations below; the export alone does not establish authorization.
Before you start
Published ads.txt/app-ads.txt and sellers.json for domains you control; verified vendor configuration and tenant permissions.
Run the example
Extract the archive and follow README.md for setup, commands, and expected results. Start with workspace_inspect.py. Local tests use sample data.
Python tools accept --help. To connect to your workspace, supply the deployment URLs, credentials and resource IDs required by the tool.
Connect it to your application
Preview the expected ads.txt and sellers.json entries, publish the correct documents at their standard locations, then run verifySupplyDocument and inspect persisted checks.
Verify downstream partner sellers.json and domain approvals before enforcing authorization. A successful crawl is different from an authorized seller relationship; review both.
Read the deployment's IVT and privacy policy. Preserve GPP/TCF/COPPA signals on requests, and test a consent-denied case. Verification samples cannot certify legal compliance or third-party vendor conformance.
Check the result
Authorized and unauthorized supply behave differently under the configured REQUIRE policy; consent-denied requests do not gain identifiers through enrichment.