Property Resolution
Claim a domain for bind-on-verify
Changed onIssue a pending domain claim for the caller's organization and return a claim-specific authoritative_location URL (…/adagents.json?adcp_claim=<token>). The caller places that single pointer at their own origin /.well-known/adagents.json; a subsequent verify-origin reads the token and binds the domain to the caller's org. The token is the per-account artifact that proves WHICH account owns the domain — a plain domain-keyed pointer proves only that the origin endorses AAO hosting, not who the owner is.
The community write surface stays open; this does not gate writes — it establishes ownership on successful verification. Refused with 409 only when the domain is already verified and locked to a different owner.
post/api/properties/hosted/{domain}/claim
Request
- Base URLhttps://agenticadvertising.org
- URLhttps://agenticadvertising.org/api/properties/hosted/{domain}/claim
- Auth
- HTTP bearer
- or OAuth 2Authorization code: https://agenticadvertising.org/authorizeToken URL: https://agenticadvertising.org/token
Path parameters
domainstring required
Example:examplepub.com
Response
Claim issued
Changes
- info
endpoint added
- info