> ## Documentation Index > Fetch the complete documentation index at: https://docs.haiqu.ai/llms.txt > Use this file to discover all available pages before exploring further. # List Jobs For Circuit > List jobs that reference a circuit directly or through derivatives. Use this tool when the caller has a ``circuit_id`` and needs the full job history tied to that circuit, including direct execution links plus compression and transpilation relations. When to Use: - Call this when the workflow starts from a known circuit and the next step is to inspect related execution, compression, or transpilation jobs. - Call this before ``get_job_results_and_status`` when the caller does not yet know the relevant ``job_id``. Constraints: - The route aggregates multiple relation paths and may therefore return heterogeneous job families. - The implementation does not deduplicate jobs that match more than one relation path. Notes: - Returned ``job.id`` values can be forwarded to ``get_job_results_and_status`` for detailed status or results. - Agent-facing summaries should group returned jobs by type and status before expanding full records. Args: circuit_id: Circuit identifier from a prior MCP response. user: Authenticated user resolved from the API key. db: Active database session. Returns: A list of job objects related to the circuit. Raises: HTTPException: Raised with ``404`` when the parent circuit or its experiment is not available to the caller. ## OpenAPI ````yaml https://api.haiqu.ai/openapi.json get /ai/circuit/{circuit_id}/jobs openapi: 3.1.0 info: title: Haiqu API summary: Haiqu RESTful API service. description: Cloud service providing the access to Haiqu cloud runtime contact: name: Haiqu Inc. url: https://haiqu.ai/ email: info@haiqu.ai version: 1.4.0 servers: [] security: [] paths: /ai/circuit/{circuit_id}/jobs: get: summary: List Jobs For Circuit description: >- List jobs that reference a circuit directly or through derivatives. Use this tool when the caller has a ``circuit_id`` and needs the full job history tied to that circuit, including direct execution links plus compression and transpilation relations. When to Use: - Call this when the workflow starts from a known circuit and the next step is to inspect related execution, compression, or transpilation jobs. - Call this before ``get_job_results_and_status`` when the caller does not yet know the relevant ``job_id``. Constraints: - The route aggregates multiple relation paths and may therefore return heterogeneous job families. - The implementation does not deduplicate jobs that match more than one relation path. Notes: - Returned ``job.id`` values can be forwarded to ``get_job_results_and_status`` for detailed status or results. - Agent-facing summaries should group returned jobs by type and status before expanding full records. Args: circuit_id: Circuit identifier from a prior MCP response. user: Authenticated user resolved from the API key. db: Active database session. Returns: A list of job objects related to the circuit. Raises: HTTPException: Raised with ``404`` when the parent circuit or its experiment is not available to the caller. operationId: list_jobs_for_circuit parameters: - name: circuit_id in: path required: true schema: type: string title: Circuit Id responses: '200': description: Successful Response content: application/json: schema: type: array items: $ref: '#/components/schemas/BaseJobModel' title: Response List Jobs For Circuit '422': description: Validation Error content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' security: - APIKeyQuery: [] - APIKeyHeader: [] components: schemas: BaseJobModel: properties: id: type: string title: Id name: anyOf: - type: string - type: 'null' title: Name description: anyOf: - type: string - type: 'null' title: Description user_id: type: integer title: User Id experiment_id: type: string title: Experiment Id status: $ref: '#/components/schemas/JobStatus' job_type: $ref: '#/components/schemas/JobType' device_id: anyOf: - type: string - type: 'null' title: Device Id default: Haiqu OS creation_date: type: string format: date-time title: Creation Date run_date: anyOf: - type: string format: date-time - type: 'null' title: Run Date finish_date: anyOf: - type: string format: date-time - type: 'null' title: Finish Date logs: anyOf: - type: string - type: 'null' title: Logs quality: anyOf: - type: number - type: 'null' title: Quality info: anyOf: - additionalProperties: true type: object - type: 'null' title: Info time: anyOf: - type: number - type: 'null' title: Time parameters: anyOf: - additionalProperties: true type: object - items: {} type: array - type: 'null' title: Parameters type: object required: - id - user_id - experiment_id - status - job_type - creation_date title: BaseJobModel description: |- Base schema for all jobs: data loading, execution, analytics, logged local jobs, etc. HTTPValidationError: properties: detail: items: $ref: '#/components/schemas/ValidationError' type: array title: Detail type: object title: HTTPValidationError JobStatus: type: string enum: - Submitted - Initializing - Queued - Validating - Running - Cancelled - Done - Error title: JobStatus description: Class for job status. JobType: type: string enum: - User local job - Analytics - Device specific analytics - Data Loading - Hybrid - Run - State Compression - Transpilation - Variational - Pretraining - SKQD title: JobType description: Class for job types. ValidationError: properties: loc: items: anyOf: - type: string - type: integer type: array title: Location msg: type: string title: Message type: type: string title: Error Type type: object required: - loc - msg - type title: ValidationError securitySchemes: APIKeyQuery: type: apiKey in: query name: HAIQU_API_KEY APIKeyHeader: type: apiKey in: header name: authorization ````