generated: '2026-08-28' method: probed source: https://docs.x.com/.well-known/agent-card.json description: >- A2A Agent Card published by X on its documentation host. Found by direct probe; saved verbatim to a2a/x-agent-card.json. Never authored or derived. discovery: path: /.well-known/agent-card.json canonical: true host: docs.x.com x-evidence: fetched: '2026-08-28' url: https://docs.x.com/.well-known/agent-card.json http_status: 200 content_type: application/json bytes: 860 card: name: X url: https://docs.x.com/ version: 1.0.0 protocolVersion: '0.3' preferredTransport: HTTP+JSON provider_organization: X documentationUrl: https://docs.x.com/ skills_count: 1 grade: conformant grade_basis: capabilities_is_object: true protocol_version_present: true skills_is_array: true preferred_transport_present: true default_input_modes_present: true default_output_modes_present: true deviations: - field: protocolVersion value: '0.3' note: >- The card declares A2A protocol 0.3, which predates A2A 1.0.0. It passes every hard conformance check, but a client pinned to 1.0.0 semantics should not assume 1.0-only fields are present. - field: skills[].tags value: [] note: The single skill declares an empty tags array, so the card carries no skill taxonomy. - field: capabilities value: {streaming: false, pushNotifications: false} note: >- Both optional A2A transport capabilities are declared false. The card is a discovery/documentation surface pointing at docs.x.com, not an A2A task endpoint — the callable agent surface X actually ships is the MCP server at https://api.x.com/mcp (see mcp/x-mcp.yml). - field: url value: https://docs.x.com/ note: >- url, provider.url and documentationUrl all resolve to the docs site rather than to a distinct A2A message endpoint. skills: - id: x name: X url: https://docs.x.com/.well-known/agent-skills/x/skill.md saved_as: ../skills/x-x-skill.md description: >- Use when building applications that interact with X (formerly Twitter) data and functionality — search posts, manage user accounts, stream real-time data, publish content, manage direct messages, or analyze trends through REST API endpoints.