Revalidate publisher adagents.json
Authorization Lookups
Revalidate publisher adagents.json
Admin-only endpoint for support/operator tooling to synchronously fetch a publisher’s live /.well-known/adagents.json, run the registry validator, persist the refreshed verdict and fetch metadata, and return the validation result. force=true is accepted for operator tooling; the current validator always fetches the live origin.
Rate limits: 5 minutes per domain, 30 requests per user per hour.
POST
Revalidate publisher adagents.json
Authorizations
Bearer token in the Authorization header. Two token types are accepted:
- Organization API key (
sk_...) issued via the dashboard. Org-scoped, long-lived, for server-to-server use. - User JWT obtained via the OAuth 2.1 authorization code flow with PKCE. User-scoped, short-lived. Discover the authorization server at
/.well-known/oauth-authorization-serverand the protected-resource metadata at/.well-known/oauth-protected-resource/api.
Path Parameters
Example:
"publisher.example"
Query Parameters
Accepted for tooling compatibility; live origin validation is always performed.
Available options:
1, true Response
Revalidation result
Required range:
x >= 0Required range:
x >= 0Required range:
100 <= x <= 599Required range:
x >= 0Available options:
direct, authoritative_location, ads_txt_managerdomain, adagents_authoritative