> ## 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. # Get publisher crawl request status > Return the durable lifecycle for a publisher recrawl. Requesters may read their own requests; registry administrators may read any request. ## OpenAPI ````yaml https://agenticadvertising.org/openapi/registry.yaml get /api/registry/crawl-request/{crawlRequestId} 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: >- Propose, review, 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/crawl-request/{crawlRequestId}: get: tags: - Agent Discovery summary: Get publisher crawl request status description: >- Return the durable lifecycle for a publisher recrawl. Requesters may read their own requests; registry administrators may read any request. operationId: getCrawlRequest parameters: - schema: type: string format: uuid required: true name: crawlRequestId in: path responses: '200': description: Durable crawl request lifecycle content: application/json: schema: type: object properties: crawl_request_id: type: string format: uuid domain: type: string status: type: string enum: - queued - running - deferred - retrying - completed - invalid - failed attempts: type: integer max_attempts: type: integer requested_at: type: string format: date-time started_at: type: - string - 'null' format: date-time last_attempted_at: type: - string - 'null' format: date-time completed_at: type: - string - 'null' format: date-time next_attempt_at: type: - string - 'null' format: date-time last_error_code: type: - string - 'null' required: - crawl_request_id - domain - status - attempts - max_attempts - requested_at - started_at - last_attempted_at - completed_at - next_attempt_at - last_error_code '400': description: Invalid crawl request ID content: application/json: schema: $ref: '#/components/schemas/Error' '401': description: Authentication required content: application/json: schema: $ref: '#/components/schemas/Error' '404': description: Crawl request not found content: application/json: schema: $ref: '#/components/schemas/Error' '503': description: Crawl status is temporarily unavailable headers: Retry-After: schema: type: string description: Seconds to wait before retrying required: true description: Seconds to wait before retrying content: application/json: schema: type: object properties: error: type: string code: type: string enum: - crawl_status_unavailable retry_after: type: integer required: - error - code - retry_after security: - bearerAuth: [] - oauth2: [] components: schemas: Error: type: object properties: error: type: string required: - error 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 ````