Skip to content

feat(registry): expose requestManagerRevalidation on RegistryClient #2292

Description

@bokelley

Gap

The registry exposes a manager-revalidation operation at POST /api/registry/manager-revalidation-request — it re-validates every publisher delegating to a manager domain via the ads.txt MANAGERDOMAIN one-hop (the right tool after a manager rotates its adagents.json). It's present in the generated OpenAPI types, but RegistryClient does not expose a typed method for it in @adcp/sdk@9.1.0 — the only typed crawl/freshness primitives are requestCrawl(domain) and getFeed(). To trigger a manager-wide revalidation today, a consumer has to call the REST path directly, bypassing the typed client.

Ask

Add RegistryClient.requestManagerRevalidation(managerDomain: string) mirroring requestCrawl, returning the 202 enqueued-count response. This gives parity with the REST surface and a typed way to refresh all publishers under a manager (e.g. a CafeMedia/Raptive-style network) in one call instead of N per-domain requestCrawls.

Context: we're building publisher-identity refresh in a reference implementation (Scope3 / Interchange) and need manager-level revalidation as part of an SLA-driven freshness loop; per-domain requestCrawl doesn't scale to large managed networks.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions