> ## 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 applicable storyboards for agent > Probe the agent's get_adcp_capabilities and resolve its declared supported_protocols and specialisms to the compliance bundles that will run. Requires authentication and ownership. ## OpenAPI ````yaml https://raw.githubusercontent.com/adcontextprotocol/adcp/v3.0.26/static/openapi/registry.yaml get /api/registry/agents/{encodedUrl}/applicable-storyboards 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: 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: 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. paths: /api/registry/agents/{encodedUrl}/applicable-storyboards: get: tags: - Agent Compliance summary: Get applicable storyboards for agent description: >- Probe the agent's get_adcp_capabilities and resolve its declared supported_protocols and specialisms to the compliance bundles that will run. Requires authentication and ownership. operationId: getApplicableStoryboards parameters: - schema: type: string description: URL-encoded agent URL required: true description: URL-encoded agent URL name: encodedUrl in: path responses: '200': description: >- Bundles the agent will be tested against, driven by its declared capabilities content: application/json: schema: type: object properties: agent_url: type: string agent_name: type: string supported_protocols: type: array items: type: string specialisms: type: array items: type: string capabilities_probe_error: type: string description: >- Agent-reported probe error. Untrusted — sanitized and truncated to 500 chars. Present when get_adcp_capabilities was advertised but failed; empty bundle list usually indicates this, not a v2 agent. bundles: type: array items: type: object properties: kind: type: string enum: - universal - domain - specialism id: type: string storyboards: type: array items: type: object properties: id: type: string title: type: string summary: type: string step_count: type: integer required: - id - title - summary - step_count required: - kind - id - storyboards total_storyboards: type: integer required: - agent_url - agent_name - supported_protocols - specialisms - bundles - total_storyboards '400': description: Invalid agent URL content: application/json: schema: $ref: '#/components/schemas/Error' '401': description: Authentication required content: application/json: schema: $ref: '#/components/schemas/Error' '403': description: Not authorized content: application/json: schema: $ref: '#/components/schemas/Error' '422': description: >- Agent requires authentication, or declares a specialism not in the local compliance cache content: application/json: schema: type: object properties: error: type: string needs_auth: type: boolean unknown_specialism: type: boolean declared_specialisms: type: array items: type: string description: >- Specialisms the agent declared, for unknown-specialism errors known_specialisms: type: array items: type: string description: >- Specialism ids present in this server's local compliance cache required: - error '500': description: Server error content: application/json: schema: type: object properties: error: type: string reason: type: string enum: - network - tls - timeout - protocol - unknown description: Coarse error classification for UI differentiation required: - error '504': description: Connection timeout content: application/json: schema: $ref: '#/components/schemas/Error' 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 ````