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

# List Answer Agent runs

> List the caller's Answer Agent runs, newest first

## Notes

* Returns the authenticated caller's Answer Agent runs, newest first, as a list envelope: `{ "object": "list", "data": [ … ], "has_more": bool, "next_cursor": string | null }`.
* Each item is a trimmed `AnswerAgentRunSummary` (`run_id`, `status`, `created_at`, `completed_at`, `thread_id`, `usage`) — fetch full detail via [Poll an Answer Agent run](/api-reference/agent-answer-poll).
* Paginate with `cursor` (a prior response's `next_cursor`) and `limit` (default 20, max 100).


## OpenAPI

````yaml GET /v1/agent/answer/runs
openapi: 3.1.0
info:
  title: Knowledge Search API
  version: 1.0.0
servers:
  - url: https://tako.com/api/
    description: Tako Production API Server
security: []
paths:
  /v1/agent/answer/runs:
    get:
      tags:
        - agent
      summary: List answer agent runs
      description: >-
        List the authenticated caller's answer agent runs, newest first. Returns
        trimmed run summaries; fetch full detail via GET
        /v1/agent/answer/runs/{run_id}.
      operationId: listAnswerAgentRuns
      parameters:
        - description: Opaque pagination cursor from a previous response's next_cursor.
          required: false
          schema:
            type: string
          name: cursor
          in: query
        - description: Max runs to return (default 20, max 100).
          required: false
          schema:
            type: integer
            maximum: 100
            minimum: 1
          name: limit
          in: query
      responses:
        '200':
          description: A page of the caller's answer agent runs, newest first.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/AnswerAgentRunList'
        '400':
          description: Invalid pagination parameter (limit or cursor).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorObject'
        '401':
          description: Missing or invalid API key.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorObject'
      security:
        - apiKey: []
components:
  schemas:
    AnswerAgentRunList:
      properties:
        object:
          type: string
          const: list
          title: Object
          default: list
        data:
          items:
            $ref: '#/components/schemas/AnswerAgentRunSummary'
          type: array
          title: Data
        has_more:
          type: boolean
          title: Has More
          default: false
        next_cursor:
          anyOf:
            - type: string
            - type: 'null'
          title: Next Cursor
      type: object
      required:
        - data
      title: AnswerAgentRunList
      description: >-
        OpenAI/Exa-style list envelope for GET /v1/agent/answer/runs
        (TAKO-3384).
    ErrorObject:
      properties:
        code:
          type: string
          title: Code
        message:
          type: string
          title: Message
      type: object
      required:
        - code
        - message
      title: ErrorObject
    AnswerAgentRunSummary:
      properties:
        run_id:
          type: string
          title: Run Id
        status:
          $ref: '#/components/schemas/AgentRunStatus'
        created_at:
          type: string
          title: Created At
        completed_at:
          anyOf:
            - type: string
            - type: 'null'
          title: Completed At
        thread_id:
          anyOf:
            - type: string
            - type: 'null'
          title: Thread Id
        usage:
          anyOf:
            - $ref: '#/components/schemas/Usage'
            - type: 'null'
        object:
          type: string
          const: agent.run
          title: Object
          default: agent.run
      type: object
      required:
        - run_id
        - status
        - created_at
      title: AnswerAgentRunSummary
    AgentRunStatus:
      type: string
      enum:
        - queued
        - running
        - completed
        - failed
      title: AgentRunStatus
    Usage:
      properties:
        total_cost_usd:
          type: number
          title: Total Cost Usd
        compute:
          anyOf:
            - $ref: '#/components/schemas/UsageCompute'
            - type: 'null'
        data:
          anyOf:
            - $ref: '#/components/schemas/UsageData'
            - type: 'null'
      type: object
      required:
        - total_cost_usd
      title: Usage
      description: >-
        Cost-plus usage for one metered request. `total_cost_usd` is always
        present

        (the total quoted charge). `compute` / `data` are the additive breakdown
        and

        appear only where they apply. See module docstring for the
        quote-vs-drawdown

        caveat and the total == compute + data invariant.
    UsageCompute:
      properties:
        cost_usd:
          type: number
          title: Cost Usd
      type: object
      required:
        - cost_usd
      title: UsageCompute
      description: |-
        Cost of running the operation (agent COGS x multiplier, or the flat
        search/answer per-request rate). Absent on surfaces with no compute step
        (contents).
    UsageData:
      properties:
        cost_usd:
          type: number
          title: Cost Usd
        datasets:
          type: integer
          title: Datasets
      type: object
      required:
        - cost_usd
        - datasets
      title: UsageData
      description: >-
        Cost + quantity of inline data delivered in the response (agent
        per-dataset

        surcharge, search/answer include_contents charge, or the contents
        per-item

        cost). `datasets` is the count of billed data units. Absent when the
        surface

        did not / cannot emit inline data (e.g. the answer agent).
  securitySchemes:
    apiKey:
      type: apiKey
      name: X-API-Key
      in: header

````