generated: '2026-09-19'
method: probed
source: https://luminarylane.app/.well-known/agent-card.json
card:
  file: a2a/luminarylane-app-agent-card.json
discovery:
  path: /.well-known/agent-card.json
  canonical: true
  host: luminarylane.app
  note: >-
    Served identically (same 5,915-byte body, application/json, cache-control public max-age=3600)
    from the apex luminarylane.app and from www.luminarylane.app. The legacy /.well-known/agent.json
    404s on both hosts, and neither app.luminarylane.app nor mcp.luminarylane.app serves a card. The
    provider names this exact URL in its own robots.txt ("A2A Agent Card for AI agent discovery")
    and in the "Technical" section of its llms.txt, and the apex DNS carries an
    a2a-registry-verify TXT record, so ownership is not in question. A negative-control probe of
    /.well-known/luminarylane-app-negative-control-4b7d2e.json returned a real 404 on every host,
    so the 200 is not a catch-all.
x-evidence:
  fetched: '2026-09-19'
  url: https://luminarylane.app/.well-known/agent-card.json
  http_status: 200
  content_type: application/json
  body_bytes: 5915
  body_parses_as: JSON object with AgentCard shape (name, url, version, capabilities, skills, provider)
  corroborating_probes:
  - url: https://www.luminarylane.app/.well-known/agent-card.json
    http_status: 200
  - url: https://luminarylane.app/.well-known/agent.json
    http_status: 404
  - url: https://www.luminarylane.app/.well-known/agent.json
    http_status: 404
  - url: https://app.luminarylane.app/.well-known/agent-card.json
    http_status: 404
  - url: https://mcp.luminarylane.app/.well-known/agent-card.json
    http_status: 404
  - url: https://www.luminarylane.app
    method: POST (JSON-RPC)
    http_status: 405
    note: >-
      The card's url field is the marketing site root. A JSON-RPC POST to it, to /a2a and to /a2a/
      returns 405 Method Not Allowed; the card therefore declares no callable A2A endpoint — it is a
      discovery document describing the Lane agent's skills, not an invocable service.
  - url: https://www.luminarylane.app/a2a/
    http_status: 200
    note: >-
      The card's documentationUrl resolves to a marketing page about "AI discoverability and A2A"
      that describes the provider's discovery consulting, not an A2A protocol reference.
agent_card:
  name: Lane
  description: >-
    AI CMO that never sleeps. Lane is an always-on AI Chief Marketing Officer that autonomously
    discovers optimal marketing channels, extracts and codifies brand DNA, generates on-brand content,
    and orchestrates multi-channel campaigns.
  version: 1.0.0
  url: https://www.luminarylane.app
  documentation_url: https://www.luminarylane.app/a2a/
  provider:
    organization: Luminary Lane
    url: https://www.luminarylane.app
  capabilities:
    streaming: false
    pushNotifications: false
    stateTransitionHistory: false
  authentication:
    schemes: []
    credentials: null
  default_input_modes:
  - text/plain
  default_output_modes:
  - text/plain
  - application/json
  skill_count: 6
  skills:
  - id: cmo_strategy
    name: CMO Strategy & Advisory
  - id: brand_analysis
    name: Brand Analysis
  - id: channel_discovery
    name: Channel Discovery
  - id: content_generation
    name: Content Generation
  - id: campaign_orchestration
    name: Campaign Orchestration
  - id: a2a_readiness
    name: A2A Readiness Assessment
conformance:
  spec: A2A 1.0.0
  grade: flavored
  protocol_version: null
  preferred_transport: null
  hard_checks:
    capabilities_is_object: true
    protocol_version_present: false
    skills_is_array: true
  optional_fields:
    default_input_modes: true
    default_output_modes: true
    preferred_transport: false
  grade_basis: >-
    Two of three hard checks pass — capabilities is an object of booleans and skills is an array of six
    fully populated skills (id, name, description, tags, examples, inputModes, outputModes) — but the
    card carries NO protocolVersion anywhere: not at the top level (A2A 0.2/0.3 shape) and there is
    no supportedInterfaces[] (A2A 1.0.0 shape) to carry it either. Failing any hard check grades the
    card flavored. defaultInputModes and defaultOutputModes are both present.
  deviations:
  - field: protocolVersion
    observed: absent
    note: No protocol version is declared in any A2A-shaped location, so a client cannot tell which revision of the protocol the card was written against.
  - field: authentication
    observed: 'object {schemes: [], credentials: null}'
    note: authentication is the pre-0.2 field name; current revisions use securitySchemes + security. The declared scheme list is empty.
  - field: url
    observed: https://www.luminarylane.app
    note: The url is the marketing site root, which answers 405 to a JSON-RPC POST. The card declares no invocable A2A endpoint.
  - field: capabilities.stateTransitionHistory
    observed: false
    note: Declared with the 0.2-era key set (streaming, pushNotifications, stateTransitionHistory); extensions and extendedAgentCard are not declared.
  - field: preferredTransport / supportedInterfaces / additionalInterfaces
    observed: absent
    note: No transport binding is declared under any revision's field name.
surface_relationship:
  note: >-
    Luminary Lane publishes two agent surfaces that are not projections of each other. The A2A card
    describes six advisory skills of the Lane agent with no callable endpoint. The remote MCP server
    at https://mcp.luminarylane.app/mcp (see mcp/luminarylane-app-mcp.yml) exposes 46 workspace tools
    behind OAuth 2.1 / API-key auth, and is the surface an agent can actually call.