> ## Documentation Index > Fetch the complete documentation index at: https://docs.zespan.com/llms.txt > Use this file to discover all available pages before exploring further. # List evidence packs for a project > Paginated list, newest first. `evidenceIndex` (the citation list) is deliberately excluded from every row here — it can hold hundreds of entries per pack and this view never renders them; fetch a single pack to read it. **Authenticated with a dashboard session (browser cookie), not `x-api-key`**, and requires `compliance:read` plus the Pro plan or above. ## OpenAPI ````yaml /api-reference/openapi.yaml get /v1/projects/{id}/evidence-packs openapi: 3.1.0 info: title: Zespan Public API version: 1.0.0 description: > The Zespan Public API covers the endpoints that customers call directly or through the Zespan SDKs: trace ingestion (native and OpenTelemetry), prompt management, datasets and dataset runs, and the runtime guardrails check. All endpoints authenticate with a project API key sent in the `x-api-key` header. Create and manage API keys from the project settings in the Zespan dashboard. servers: - url: https://api.zespan.com description: Zespan production API security: - ApiKeyAuth: [] tags: - name: Ingestion description: Send traces and events to Zespan. - name: OpenTelemetry description: OTLP-compatible ingestion endpoints. - name: Prompts description: Manage versioned prompts and their labels, tags, and folders. - name: Datasets description: Read datasets and manage dataset runs used for experiments and scoring. - name: Guardrails description: Runtime guardrail evaluation. - name: SDK / CLI support description: > Small support endpoints consumed by the SDKs and @zespan/cli rather than called directly by application code. - name: Blast Radius description: > The prompt/agent/model/policy/evaluator/alert dependency graph backing the pre-release impact check and the evaluator-delete gate in the dashboard. Session-authenticated (dashboard cookie), not `x-api-key`. - name: Outcomes description: > Report business outcomes (a deflected ticket, an avoided refund, an SLA met) attributed to a trace, and read them back summarized by agent or model, joined to real trace cost. Backs the Value dashboard page. The ingest endpoint is `x-api-key`-authenticated like the rest of ingestion; the two read endpoints are session-authenticated (dashboard cookie) like Blast Radius. - name: Compliance description: > Generate audit-ready evidence documents (a per-agent Compliance Card, or SOC 2 control evidence) from recorded platform data, and re-verify a generated document's citations against live data. Session-authenticated (dashboard cookie), not `x-api-key`, gated by `compliance:read` / `compliance:generate` permissions and the Pro plan or above (the framework listing is the one exception — no project scope and no plan gate, since a customer deciding whether to upgrade needs to see what they'd get). - name: Models description: > Per-model usage, cost, latency, and error-rate rollups for a project, including the lifecycle overlay described under the Model Lifecycle tag. Session-authenticated (dashboard cookie), not `x-api-key`, gated by `dashboard:read`. - name: Model Lifecycle description: > Findings from the daily model deprecation scan, which matches models a project actually calls against a curated, bundled catalogue of provider-announced deprecation and retirement dates. Every figure on a finding (call volume, cost, affected agents/prompts, cost comparison against a named successor) is measured from real trace data — there is no quality-delta or regression-comparison endpoint, because nothing in this API invokes a model on the caller's behalf. Session-authenticated (dashboard cookie), not `x-api-key`: reading findings and the catalogue requires `dashboard:read`, dismissing a finding requires `alerts:manage`. paths: /v1/projects/{id}/evidence-packs: get: tags: - Compliance summary: List evidence packs for a project description: > Paginated list, newest first. `evidenceIndex` (the citation list) is deliberately excluded from every row here — it can hold hundreds of entries per pack and this view never renders them; fetch a single pack to read it. **Authenticated with a dashboard session (browser cookie), not `x-api-key`**, and requires `compliance:read` plus the Pro plan or above. operationId: listEvidencePacks parameters: - name: id in: path required: true schema: type: string format: uuid description: Project id. - name: kind in: query schema: type: string enum: - agent_card - control_evidence - name: framework in: query schema: type: string enum: - soc2 - name: status in: query schema: type: string enum: - pending - processing - completed - failed - name: page in: query schema: type: integer minimum: 1 default: 1 - name: pageSize in: query schema: type: integer minimum: 1 maximum: 100 default: 25 responses: '200': description: A page of evidence packs. content: application/json: schema: $ref: '#/components/schemas/EvidencePackListResponse' '403': description: >- Not authenticated with a dashboard session, lacks `compliance:read`, or plan below Pro. content: application/json: schema: $ref: '#/components/schemas/Error' security: [] components: schemas: EvidencePackListResponse: type: object properties: packs: type: array items: $ref: '#/components/schemas/EvidencePack' pagination: type: object properties: page: type: integer pageSize: type: integer total: type: integer totalPages: type: integer required: - page - pageSize - total - totalPages required: - packs - pagination Error: type: object properties: error: type: string description: Human-readable error message. example: Unauthorized code: type: string description: Machine-readable error code, when present. example: rate_limit_exceeded required: - error EvidencePack: type: object properties: id: type: string format: uuid kind: type: string enum: - agent_card - control_evidence framework: type: string nullable: true enum: - soc2 - null scope: type: object properties: agentName: type: string periodStart: type: string format: date-time periodEnd: type: string format: date-time format: type: string enum: - json - html status: type: string enum: - pending - processing - completed - failed error: type: string nullable: true description: Set when `status` is `failed`. sha256: type: string nullable: true description: >- SHA-256 of the stored document's exact bytes, once generation has completed. generatedBy: type: string description: User id that requested generation. generatedAt: type: string format: date-time completedAt: type: string format: date-time nullable: true required: - id - kind - framework - scope - periodStart - periodEnd - format - status - error - sha256 - generatedBy - generatedAt - completedAt securitySchemes: ApiKeyAuth: type: apiKey in: header name: x-api-key description: >- Project API key. Manage keys in the Zespan dashboard under project settings. ````