Phase F · Step 10

Agentic Rights Discovery + Universal Resolver

Resolve an encountered publisher/resource to ContentDividend public rights infrastructure, then optionally request a live URVP use decision without inventing a second licensing authority.

Core rule: resolver discovery never grants rights. An authorized ContentDividend use decision still requires current authenticated exact-resource rights through live URVP verification.

Public resolver

GET /v1/public/rights/resolve?resource=https://example.com/article

Supported:
resource
url
domain
site_id
entry_id
fingerprint

Agent resolver + live verification

POST /v1/agent/rights/resolve
Authorization: Bearer <existing buyer credential>
Content-Type: application/json

{
  "resource":"https://example.com/article",
  "requested_use":"rag"
}

Machine manifest

GET /.well-known/contentdividend-rights-resolver.json
GET /v1/public/rights-resolver/manifest

What comes back

Public publisher identity, exact registered-page match when available, Rights Passport, Rights Adapter, licensing manifest, AI Rights Map record, ContentDNA provenance, provenance ledger, citation resolver, URVP verification path, integration manifest and licensing-request path.

Resolver semantics

resolved=true means the public resolver associated the query with an approved public ContentDividend Marketplace publisher. It does not mean the caller is authorized. resolved=false does not mean no rights exist; it means the public resolver did not resolve a public Marketplace record.

Live authorization

When requested_use is supplied with a concrete resource URL, the agent endpoint calls the existing live URVP engine. The result is not cached by F10. Current exact-resource scope, active grant state, revocation and publisher authorization remain authoritative.