> ## 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. # Inputs and outputs of one trace step > Returns the inputs and outputs of one step of a trace, fetched on demand. Same permission as the trace (`agent-factory:traces:read`). The event must belong both to the given correlation and to an execution of the given agent. Known secret keys are stripped from `input` and `output`; the raw event is never served (open it in the Builder activity view, under workspace access control). ## OpenAPI ````yaml /api-reference/agent-factory/swagger.yml get /v1/agents/{agentId}/traces/{correlationId}/events/{eventId} 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: Traces description: >- Execution traces of agent turns (editor debugging, `agent-factory:traces:read`). - name: Evaluations description: Agent evaluation runs and results. - name: Admin description: | GDPR operations called by the AI Insights admin screens. They require elevated permissions: the caller must be a platform administrator (`platformRole` `superadmin` or `root`). The export route also lets a user export their own data. Each route is rate limited to 10 calls per hour per caller. paths: /v1/agents/{agentId}/traces/{correlationId}/events/{eventId}: get: tags: - Traces summary: Inputs and outputs of one trace step description: | Returns the inputs and outputs of one step of a trace, fetched on demand. Same permission as the trace (`agent-factory:traces:read`). The event must belong both to the given correlation and to an execution of the given agent. Known secret keys are stripped from `input` and `output`; the raw event is never served (open it in the Builder activity view, under workspace access control). operationId: getAgentTraceEvent parameters: - name: agentId in: path required: true schema: type: string maxLength: 64 - name: correlationId in: path required: true schema: type: string maxLength: 128 - name: eventId in: path required: true schema: type: string maxLength: 128 - name: x-draft-mode in: header required: false schema: type: string enum: - 'true' description: Resolve the agent as its editor does (draft configuration). responses: '200': description: Step detail. content: application/json: schema: $ref: '#/components/schemas/AgentTraceEvent' '401': description: Authentication required. content: application/json: schema: $ref: '#/components/schemas/Error' '403': description: Forbidden - `agent-factory:traces:read` is required. content: application/json: schema: $ref: '#/components/schemas/Error' '404': description: Agent or event not found for this trace. content: application/json: schema: $ref: '#/components/schemas/Error' '502': description: The event store could not be read (`SEARCH_FAILED`). content: application/json: schema: $ref: '#/components/schemas/Error' components: schemas: AgentTraceEvent: type: object properties: id: type: string type: type: string timestamp: type: string format: date-time automation: type: string appInstance: type: string workspaceId: type: string duration: type: number trigger: type: object additionalProperties: true expired: type: boolean description: >- True when the 14-day cleanup already removed this step's inputs and outputs. input: nullable: true description: Step inputs, known secret keys removed. output: nullable: true description: Step outputs, known secret keys removed. source: type: object properties: correlationId: type: string automationSlug: type: string appInstanceFullSlug: type: string appInstanceDepth: type: integer workspaceId: type: string userId: type: string sessionId: type: string serviceTopic: type: string Error: type: object required: - error - message properties: error: type: string description: >- Stable PascalCase or SNAKE_CASE error code (e.g. AgentNotFound, VALIDATION_ERROR, FORBIDDEN, METHOD_NOT_ALLOWED). message: type: string description: Human-readable error message. details: type: object description: Optional structured context for the error. additionalProperties: true 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_...`. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.