Revalidate publisher adagents.json
curl --request POST \
--url https://agenticadvertising.org/api/registry/publisher/{domain}/adagents/revalidate \
--header 'Authorization: Bearer <token>'{
"domain": "<string>",
"adagents_valid": true,
"checked_at": "2023-11-07T05:31:56Z",
"error": "<string>",
"issues": {
"errors": [
{
"field": "<string>",
"message": "<string>",
"severity": "error"
}
],
"warnings": [
{
"field": "<string>",
"message": "<string>",
"suggestion": "<string>"
}
]
},
"properties_count": 1,
"authorized_agents_count": 1,
"status_code": 349,
"response_bytes": 1,
"resolved_url": "<string>",
"manager_domain": "<string>"
}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
/
api
/
registry
/
publisher
/
{domain}
/
adagents
/
revalidate
Revalidate publisher adagents.json
curl --request POST \
--url https://agenticadvertising.org/api/registry/publisher/{domain}/adagents/revalidate \
--header 'Authorization: Bearer <token>'{
"domain": "<string>",
"adagents_valid": true,
"checked_at": "2023-11-07T05:31:56Z",
"error": "<string>",
"issues": {
"errors": [
{
"field": "<string>",
"message": "<string>",
"severity": "error"
}
],
"warnings": [
{
"field": "<string>",
"message": "<string>",
"suggestion": "<string>"
}
]
},
"properties_count": 1,
"authorized_agents_count": 1,
"status_code": 349,
"response_bytes": 1,
"resolved_url": "<string>",
"manager_domain": "<string>"
}Authorizations
bearerAuthoauth2
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
Show child attributes
Show child attributes
Required range:
x >= 0Required range:
x >= 0Required range:
100 <= x <= 599Required range:
x >= 0Available options:
direct, authoritative_location, ads_txt_managerdomain, adagents_authoritative Was this page helpful?
⌘I