> ## Documentation Index > Fetch the complete documentation index at: https://docs.adcontextprotocol.org/llms.txt > Use this file to discover all available pages before exploring further. # Resolve identifiers to property_rids (and contribute them) > The primary fact-contribution path. Takes identifiers plus a provenance envelope and returns stable `property_rid`s. 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. ## OpenAPI ````yaml /static/openapi/registry.yaml post /api/registry/resolve openapi: 3.1.0 info: title: AgenticAdvertising.org Registry API description: >- REST API for the AgenticAdvertising.org registry. Resolve brands, discover properties, look up agents, and validate authorization in the AdCP ecosystem. Most endpoints are public and require no authentication. Endpoints marked with a lock icon accept either an organization API key or a user JWT obtained via the OAuth 2.1 flow — see [Authentication](https://agenticadvertising.org/docs/registry/index#authentication). **Base URL:** `https://agenticadvertising.org` version: 1.0.0 contact: name: AgenticAdvertising.org url: https://agenticadvertising.org servers: - url: https://agenticadvertising.org description: Production security: [] tags: - name: Onboarding description: >- Explicitly bootstrap a third-party integration into the AAO registry. Most callers don't need this tag — `POST /api/me/agents` auto-creates the org (for fresh users) and the member profile (for first-time agent registration) without a separate round trip. Use `POST /api/organizations` only when you need to override the auto-derived org name / company_type / revenue_tier. Tier transitions happen via the billing flow only; the Stripe webhook is the sole writer of `organizations.membership_tier`. - name: Member Agents description: >- Register, list, update, and remove agents on the caller's organization member profile. Authenticated programmatic surface for CI / scripts that don't want to round-trip the full member profile. - name: Brand Resolution description: Resolve advertiser domains to canonical brand identities. - name: Property Resolution description: >- Resolve publisher domains to their property configurations and authorized agents. - name: Agent Discovery description: >- Browse the federated agent network, search agent inventory profiles, publisher index, and registry statistics. - name: Change Feed description: Poll cursor-based registry change events for local sync. - name: Lookups & Authorization description: >- Look up agents by domain or property, and validate ad-serving authorization. - name: Validation Tools description: >- Validate publisher adagents.json files and generate compliant configurations. - name: Community Mirrors description: >- Publish, fetch, list, and retire catalog-only adagents.json mirrors for platforms that have not adopted AdCP. - name: Search description: Cross-entity search across brands, publishers, agents, and properties. - name: Agent Probing description: >- Connect to live agents and inspect their capabilities, formats, and inventory. - name: Brand Discovery description: Discover and crawl brand.json files across domains. - name: Agent Compliance description: Agent compliance status, storyboard test results, and compliance history. - name: Policy Registry description: >- Browse, resolve, and contribute governance policies for campaign compliance. - name: Property Catalog description: >- Contribute facts to the property fact-graph: resolve identifiers to stable property_rids (which also contributes them, with provenance) and dispute catalog claims. paths: /api/registry/resolve: post: tags: - Property Catalog summary: Resolve identifiers to property_rids (and contribute them) description: >- The primary fact-contribution path. Takes identifiers plus a provenance envelope and returns stable `property_rid`s. 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. operationId: resolveIdentifiers requestBody: content: application/json: schema: $ref: '#/components/schemas/ResolveRequest' responses: '200': description: Resolve/lookup result content: application/json: schema: $ref: '#/components/schemas/ResolveResponse' '400': description: >- Invalid request (bad identifiers, unknown provenance type, batch > 10,000) content: application/json: schema: $ref: '#/components/schemas/Error' '401': description: Authentication required for resolve mode content: application/json: schema: $ref: '#/components/schemas/Error' security: - bearerAuth: [] - oauth2: [] components: schemas: ResolveRequest: type: object properties: identifiers: type: array items: $ref: '#/components/schemas/CatalogIdentifier' minItems: 1 maxItems: 10000 description: >- Identifiers to resolve (and, in resolve mode, contribute). Max 10,000 per call for all callers. provenance: $ref: '#/components/schemas/FactProvenance' mode: type: string enum: - resolve - lookup default: resolve description: >- `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. required: - identifiers - provenance ResolveResponse: type: object properties: resolved: type: array items: $ref: '#/components/schemas/ResolvedEntry' summary: type: object properties: total: type: integer resolved: type: integer created: type: integer excluded: type: integer not_found: type: integer required: - total - resolved - created - excluded - not_found server_timestamp: type: string required: - resolved - summary - server_timestamp Error: type: object properties: error: type: string required: - error CatalogIdentifier: type: object properties: type: type: string example: domain value: type: string example: nytimes.com required: - type - value FactProvenance: type: object properties: type: type: string enum: - agency_allowlist - publisher_declaration - impression_log - ssp_inventory - deal_history - crawl - data_partner - member_assertion description: >- How the caller knows these identifiers — the trust/audit envelope on the fact. Determines the confidence the catalog assigns. `crawl` is reserved for server-side pipelines; callers use the others. context: type: string example: unilever_q3 description: Optional free-text annotation (campaign, dataset). required: - type ResolvedEntry: type: object properties: identifier: $ref: '#/components/schemas/CatalogIdentifier' property_rid: type: - string - 'null' description: >- Stable catalog handle for joining/dedup and TMP matching. NOT an authorization credential. `null` for excluded (ad_infra / publisher_mask) or unresolved-in-lookup identifiers. classification: type: string example: property status: type: string enum: - existing - created - excluded source: type: - string - 'null' required: - identifier - property_rid - classification - status - source securitySchemes: bearerAuth: type: http scheme: bearer description: >- 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-server` and the protected-resource metadata at `/.well-known/oauth-protected-resource/api`. oauth2: type: oauth2 description: >- OAuth 2.1 authorization code flow with PKCE. Users authenticate via AuthKit and clients receive a Bearer JWT that authorizes both the MCP endpoint and this REST API. Dynamic client registration is supported at `/register`. flows: authorizationCode: authorizationUrl: https://agenticadvertising.org/authorize tokenUrl: https://agenticadvertising.org/token refreshUrl: https://agenticadvertising.org/token scopes: openid: User identifier profile: User profile information email: User email address ````