curl --request POST \
--url https://agenticadvertising.org/api/registry/resolve \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"identifiers": [
{
"type": "domain",
"value": "nytimes.com"
}
],
"provenance": {
"context": "unilever_q3"
},
"mode": "resolve"
}
'{
"resolved": [
{
"identifier": {
"type": "domain",
"value": "nytimes.com"
},
"property_rid": "<string>",
"classification": "property",
"source": "<string>"
}
],
"summary": {
"total": 123,
"resolved": 123,
"created": 123,
"excluded": 123,
"not_found": 123
},
"server_timestamp": "<string>"
}Resolve identifiers to property_rids (and contribute them)
The primary fact-contribution path. Takes identifiers plus a provenance envelope and returns stable property_rids. In resolve mode (default) it auto-creates missing catalog entries and logs demand activity — so resolving your own identifier list IS the contribution. property_rid is a non-authoritative join/match handle, never an authorization credential. Re-resolving is idempotent on the identifier→rid mapping but additive on the activity log.
curl --request POST \
--url https://agenticadvertising.org/api/registry/resolve \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"identifiers": [
{
"type": "domain",
"value": "nytimes.com"
}
],
"provenance": {
"context": "unilever_q3"
},
"mode": "resolve"
}
'{
"resolved": [
{
"identifier": {
"type": "domain",
"value": "nytimes.com"
},
"property_rid": "<string>",
"classification": "property",
"source": "<string>"
}
],
"summary": {
"total": 123,
"resolved": 123,
"created": 123,
"excluded": 123,
"not_found": 123
},
"server_timestamp": "<string>"
}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.
Body
Identifiers to resolve (and, in resolve mode, contribute). Max 10,000 per call for all callers.
1 - 10000 elementsShow child attributes
Show child attributes
Show child attributes
Show child attributes
resolve (default) contributes the identifiers, auto-creates missing catalog entries, logs demand activity, and returns rids — requires authentication. lookup is a pure read: no write, no activity log, no auth.
resolve, lookup Was this page helpful?