> ## Documentation Index > Fetch the complete documentation index at: https://docs.prisme.ai/llms.txt > Use this file to discover all available pages before exploring further. # A2A task snapshot (per-agent, GET) > Per-agent A2A gateway snapshot endpoint. `GET ?taskId=xxx` validates the task belongs to this agent then forwards to `getTaskSnapshot`. Returns a JSON-RPC error envelope when the task does not belong to the agent. ## OpenAPI ````yaml /api-reference/agent-factory/swagger.yml get /v1/agents/{agentId}/a2a openapi: 3.0.3 info: version: 1.0.0 title: Agent Factory API description: | Public REST API for the Agent Factory workspace - agents, conversations, messages, tools, artifacts, sharing, ratings, and discovery. Powered by Prisme.ai's runtime; all endpoints are exposed under each workspace's webhook namespace. contact: name: Prisme.ai url: https://prisme.ai servers: - url: https://{host}/v2/workspaces/slug:agent-factory/webhooks description: Prisme.ai workspace webhooks variables: host: default: api.studio.prisme.ai description: API host (override for self-hosted or sandbox) security: - BearerAuth: [] - OrgApiKeyAuth: [] tags: - name: Agents description: Agent CRUD, discovery, AGENTS.md import/export. - name: Access description: Agent access bindings, sharing, and access requests. - name: ApiKeys description: Agent-scoped API key management (mint, revoke, rotate). - name: Publishing description: Publish or discard draft changes on an agent. - name: Ratings description: User ratings on published agents. - name: Profiles description: >- Agent profiles/presets catalog (simple, workflow, agent_light, agent_full, orchestrator). - name: Activity description: Activity feed for agents (events, errors, lifecycle changes). - name: Analytics description: Agent usage analytics (series + summary). - name: Conversations description: Conversations on an agent (CRUD, archive, star). - name: Messages description: Send messages to an agent (synchronous send + SSE stream). - name: Tasks description: Async task lifecycle (list, fetch, cancel, resolve, subscribe). - name: Artifacts description: Generated artifacts (files, code, content) attached to a task. - name: Shares description: Conversation, message, and artifact share-link snapshots. - name: A2A description: Agent-to-agent JSON-RPC 2.0 gateway (well-known agent.json + RPC). - name: Tools description: Per-agent tool catalogue (system tools, MCP servers, function tools). - name: Retention description: Per-agent and org-wide conversation retention policies. - name: Evaluations description: Agent evaluation runs and results. paths: /v1/agents/{agentId}/a2a: get: tags: - A2A summary: A2A task snapshot (per-agent, GET) description: | Per-agent A2A gateway snapshot endpoint. `GET ?taskId=xxx` validates the task belongs to this agent then forwards to `getTaskSnapshot`. Returns a JSON-RPC error envelope when the task does not belong to the agent. operationId: agentTaskSnapshotA2a parameters: - name: agentId in: path required: true schema: type: string maxLength: 64 - name: taskId in: query required: true schema: type: string maxLength: 128 responses: '200': description: Task snapshot. content: application/json: schema: $ref: '#/components/schemas/TaskSnapshot' '404': description: Task not found for this agent (JSON-RPC error envelope). content: application/json: schema: $ref: '#/components/schemas/JsonRpcErrorEnvelope' components: schemas: TaskSnapshot: allOf: - $ref: '#/components/schemas/Task' - type: object properties: terminal: type: boolean description: True when state is `completed`, `canceled`, or `failed`. JsonRpcErrorEnvelope: type: object description: | Bare JSON-RPC error envelope returned without a successful `result` (e.g. when the legacy gateway cannot resolve the target agent). properties: jsonrpc: type: string enum: - '2.0' error: type: object properties: code: type: integer example: -32000 message: type: string id: type: string nullable: true description: Echoes the request id (string or null per JSON-RPC 2.0). Task: type: object description: A2A task record. properties: id: type: string contextId: type: string status: $ref: '#/components/schemas/TaskStatus' history: type: array items: type: object additionalProperties: true artifacts: type: array items: type: object additionalProperties: true metadata: type: object additionalProperties: true createdAt: type: string format: date-time TaskStatus: type: object properties: state: $ref: '#/components/schemas/TaskState' timestamp: type: string message: type: object additionalProperties: true TaskState: type: string description: A2A task state. enum: - working - completed - canceled - failed - input-required securitySchemes: BearerAuth: type: http scheme: bearer bearerFormat: JWT description: | User-bound credential carrying an identity: either a session JWT or a user access token (`at:*`) generated from the user settings UI. Send as `Authorization: Bearer `. Org API keys (`iak_*`) are **not** accepted here - they carry no user identity. Use the `x-prismeai-api-key` header instead (see `OrgApiKeyAuth`). OrgApiKeyAuth: type: apiKey in: header name: x-prismeai-api-key description: | Organization API key (`iak_{orgSlug}_{uuid}`). Unlike `Authorization: Bearer`, this credential is **not** tied to a user identity - it is bound to the org and its effective access is defined by the scopes / permission rules attached to it (it can be restricted to a single project, or kept broader). For Agent Factory, these keys can be generated directly from the Agent Factory UI (in addition to the AI Governance settings). Send as `x-prismeai-api-key: iak_...`. ````