Skip to main content
POST
Revalidate publisher adagents.json

Authorizations

Authorization
string
header
required

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-server and the protected-resource metadata at /.well-known/oauth-protected-resource/api.

Path Parameters

domain
string
required
Example:

"publisher.example"

Query Parameters

force
enum<string>

Accepted for tooling compatibility; live origin validation is always performed.

Available options:
1,
true

Response

Revalidation result

domain
string
required
adagents_valid
boolean
required
checked_at
string<date-time>
required
error
string
issues
object
properties_count
integer
Required range: x >= 0
authorized_agents_count
integer
Required range: x >= 0
status_code
integer
Required range: 100 <= x <= 599
response_bytes
integer
Required range: x >= 0
resolved_url
string
discovery_method
enum<string>
Available options:
direct,
authoritative_location,
ads_txt_managerdomain,
adagents_authoritative
manager_domain
string