generated: '2026-09-12'
method: probed
source: https://docs.afterquery.com/.well-known/agent-card.json
card: a2a/afterquery-agent-card.json
discovery:
  path: /.well-known/agent-card.json
  canonical: true
  host: docs.afterquery.com
  note: >-
    The card is served only from the documentation host. The apex (afterquery.com, which 308s to
    www), www.afterquery.com, api.afterquery.com (DNS resolves but Vercel answers
    DEPLOYMENT_NOT_FOUND on every path), appbench.ai and experts.afterquery.com were all probed on
    2026-09-12 for both /.well-known/agent-card.json and the pre-0.3 /.well-known/agent.json, and
    none serves a card (404 everywhere except experts.afterquery.com, which answers 429 with a
    Vercel Security Checkpoint interstitial to any non-browser client). docs.afterquery.com is a
    host AfterQuery controls - it is the AfterQuery Experts Help Center named from
    www.afterquery.com's own llms.txt - and the card's provider.organization is
    "AfterQuery Experts Help Center", so ownership is not in question.
x-evidence:
  fetched: '2026-09-12'
  url: https://docs.afterquery.com/.well-known/agent-card.json
  http_status: 200
  content_type: application/json
  body_parses_as: JSON object with AgentCard shape
  also_probed:
  - {url: 'https://www.afterquery.com/.well-known/agent-card.json', http_status: 404}
  - {url: 'https://www.afterquery.com/.well-known/agent.json', http_status: 404}
  - {url: 'https://docs.afterquery.com/.well-known/agent.json', http_status: 404}
  - {url: 'https://api.afterquery.com/.well-known/agent-card.json', http_status: 404}
  - {url: 'https://appbench.ai/.well-known/agent-card.json', http_status: 404}
  - {url: 'https://experts.afterquery.com/.well-known/agent-card.json', http_status: 429}
agent_card:
  name: AfterQuery Experts Help Center
  url: https://docs.afterquery.com/
  version: 1.0.0
  protocol_version: '0.3'
  preferred_transport: HTTP+JSON
  provider:
    organization: AfterQuery Experts Help Center
    url: https://docs.afterquery.com/
  documentation_url: https://docs.afterquery.com/
  capabilities:
    streaming: false
    push_notifications: false
  default_input_modes:
  - text/plain
  default_output_modes:
  - text/plain
  skill_count: 1
  skills:
  - id: afterqueryexperts
    name: Afterqueryexperts
    url: https://docs.afterquery.com/.well-known/agent-skills/afterqueryexperts/skill.md
    saved_as: skills/afterquery-experts-support.md
conformance:
  spec: A2A 1.0.0
  grade: conformant
  hard_checks:
    capabilities_is_object: true
    protocol_version_present: true
    skills_is_array: true
  optional_fields_present:
    preferred_transport: true
    default_input_modes: true
    default_output_modes: true
grade: conformant
grade_basis: >-
  Graded against the A2A 1.0.0 AgentCard hard checks - capabilities is an OBJECT (pass),
  protocolVersion is present (pass), skills is an ARRAY (pass) - and the three optional fields
  that usually separate near-conformant from conformant (preferredTransport, defaultInputModes,
  defaultOutputModes) are all declared.
deviations:
- field: protocolVersion
  observed: '0.3'
  note: >-
    Declares A2A protocol 0.3 rather than 1.0.0. A version statement, not a shape failure;
    recorded, not penalised.
- field: supportedInterfaces
  observed: present
  note: >-
    Uses supportedInterfaces[] rather than A2A 1.0.0's additionalInterfaces[]. Same information,
    the pre-1.0 spelling.
- field: description
  observed: absent
  note: >-
    The card carries no top-level description; the only prose describing what the agent does lives
    on the single skill.
- field: skills[].tags
  observed: empty array
  note: Every published skill declares an empty tags[], so the card is not self-categorising.
x-notes:
  generator: >-
    The card is machine-generated by Mintlify for the AfterQuery Experts documentation project
    (the response carries Mintlify CSP headers and an x-matched-path of
    /_sites/[subdomain]/.well-known/agent-card.json), not hand-authored by AfterQuery. It is real,
    it is served from a host AfterQuery controls, and it describes AfterQuery's own contributor
    help centre - but it is a documentation-platform surface, not a product API agent.
  scope: >-
    The agent it describes is a support/help-centre agent for AfterQuery Experts contributors
    (onboarding, payments, work guidelines), not an interface to AfterQuery's data or research
    products, which have no public API.