> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pnbr.io/llms.txt
> Use this file to discover all available pages before exploring further.

# List documents



## OpenAPI

````yaml /api-reference/openapi.json get /v1/documents
openapi: 3.1.0
info:
  title: Penumbra Platform API
  version: 1.0.0
  description: >-
    The Penumbra /v1 REST surface. Developer-intent nouns (memories, documents,
    submissions, connections, preflight, bridge) over a typed, governed
    knowledge graph. Every write stages through a reviewable delta; verdicts are
    dispositions and findings, never scores.
servers:
  - url: https://pnbr.io
security:
  - bearerAuth: []
tags:
  - name: Memories
    description: Store and recall agent memory as first-class REST.
  - name: Documents
    description: Add and search documents over the source/file substrate.
  - name: Submissions
    description: A generic capture door for app events, forms, and payloads.
  - name: Search
    description: Hybrid, graph, and retrieval search.
  - name: Ontology & Shapes
    description: Read the active ontology, types, and shapes.
  - name: Deltas
    description: 'The governed-write primitive: stage, plan, apply, revert.'
  - name: Graph
    description: >-
      Direct reads of the typed graph: nodes, edges, and counts. Scope:
      graph:read.
  - name: Extraction
    description: Coerce source material into typed entities through a shape.
  - name: Context & Slices
    description: >-
      Author reusable context scopes (slices) and compile them into context. A
      slice is a saved scope; the context verbs act on a scope or a saved slice.
  - name: Preflight
    description: >-
      Read-only decision-quality verdicts: is the graph fit to act on?
      Disposition plus findings, never a score.
  - name: Loops
    description: Bounded agentic extraction and hydration loops over your context.
  - name: Connections
    description: Headless integration connect for token-paste platforms.
  - name: Bridge
    description: Map an external API's type system onto your ontology.
paths:
  /v1/documents:
    get:
      tags:
        - Documents
      summary: List documents
      operationId: listDocuments
      parameters:
        - name: project_id
          in: query
          schema:
            type: string
        - name: search
          in: query
          schema:
            type: string
      responses:
        '200':
          description: Documents in the project.
          content:
            application/json:
              example:
                sources:
                  - id: 9784c0d0-13dc-4704-91a5-e32afc953e06
                    type: file
                    title: Untitled document.pdf
                    mimeType: application/pdf
                    sizeBytes: 178975
                    status:
                      stage: extracted
                      processing: false
                      pendingReview: false
                      outdated: false
                    ragReady: true
                    extractionCount: 1
                    entityCount: 91
                    addedByName: Shep Bryan
                    addedAt: '2026-01-10T04:52:54.471Z'
                    collections:
                      - id: 959e5b82-5af4-4bdb-b561-01693a8137d7
                        name: Collection-Test
                    governanceStatus: active
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: >-
        A `pnbr-` API key. Project-scoped keys make `project_id` implicit;
        org-scoped keys require it.

````