> ## Documentation Index > Fetch the complete documentation index at: https://docs.julian.11x.ai/llms.txt > Use this file to discover all available pages before exploring further. # List organization agents > Returns active, paused, and archived agents belonging to an organization in fixed pages of up to 100 agents. The required `orgId` is the Stytch organization ID and must match the organization associated with the API key. ## OpenAPI ````yaml /openapi.json get /agents openapi: 3.1.0 info: title: Julian API version: 1.0.0 description: >- API for Julian, 11x's AI calling platform. Programmatically enroll contacts into agent calling sequences, manage sequences, and track credit usage. All requests are authenticated with an organization API key in the `x-api-key` header and rate limited to 10 requests per second per key (HTTP 429 when exceeded). servers: - url: https://julian.11x.ai/api/v1 security: - apiKeyAuth: [] tags: - name: Scheduling description: Enroll contacts into an agent's calling sequence. - name: Sequences description: Manage active sequences. - name: Agents description: Read agent configuration. - name: Conversation Meetings description: >- Manage the meeting booked during a conversation — list its attendees, add attendees before it starts, and cancel it. Every endpoint is addressed by an `entityId` that identifies the conversation. Today only voice calls are supported, with the form of the call prefix followed by the call ID (e.g. `call.abc123`). The meeting is resolved from the calendar booking created during the conversation, and the calendar provider remains the source of truth. - name: Conversation Metadata description: >- Retrieve completed conversation data asynchronously — designed for batch ingestion, backfills, and reconciliation jobs that pull conversation metadata instead of receiving it through a webhook. **Recommended batch ingestion flow:** 1. Call `GET /conversations/search/{agentId}` with the time window you want to ingest (e.g. yesterday or the last seven days). 2. Iterate through the returned `sequenceIds`. 3. For each sequence ID, call `GET /conversations/metadata/{sequenceId}`. 4. Store the returned `metadata` array in your warehouse. 5. Use `limit`, `offset`, and `hasMore` to paginate through larger backfills. - name: Credits description: Track credit utilization. - name: Webhooks description: Events Julian sends to your endpoint. paths: /agents: get: tags: - Agents summary: List organization agents description: >- Returns active, paused, and archived agents belonging to an organization in fixed pages of up to 100 agents. The required `orgId` is the Stytch organization ID and must match the organization associated with the API key. operationId: listAgents parameters: - name: orgId in: query required: true description: Stytch organization ID associated with the API key. schema: type: string minLength: 1 example: organization-test-123 - name: page in: query required: false description: One-based page number. Defaults to the first page. schema: type: integer minimum: 1 default: 1 responses: '200': description: A page of agents and pagination metadata. content: application/json: schema: type: object required: - agents - pagination properties: agents: type: array maxItems: 100 items: type: object required: - agentId - name - status properties: agentId: type: string description: Unique identifier of the agent. example: agent.abc123 name: type: string description: Display name of the agent. example: Outbound SDR status: type: string description: Current agent status. enum: - ACTIVE - PAUSED - ARCHIVED example: ACTIVE pagination: type: object required: - page - pageSize - totalItems - totalPages - hasMore properties: page: type: integer minimum: 1 description: Current one-based page number. pageSize: type: integer const: 100 description: Maximum number of agents returned per page. totalItems: type: integer minimum: 0 description: Total number of matching agents. totalPages: type: integer minimum: 0 description: Total number of available pages. hasMore: type: boolean description: Whether another page is available. '400': description: >- `MISSING_ORG_ID` — the required `orgId` query parameter is missing or empty. `INVALID_PAGE` — `page` is not a positive integer. content: application/json: schema: $ref: '#/components/schemas/Error' examples: missingOrgId: summary: Missing organization ID value: error: MISSING_ORG_ID message: The orgId query parameter is required. invalidPage: summary: Invalid page number value: error: INVALID_PAGE message: The page query parameter must be a positive integer. '401': description: >- `UNAUTHORIZED` or `INVALID_API_KEY` — the API key is missing or invalid, or it does not belong to the requested organization. content: application/json: schema: $ref: '#/components/schemas/Error' '500': $ref: '#/components/responses/InternalServerError' components: schemas: Error: type: object required: - error - message properties: error: type: string description: Machine-readable error code. example: INVALID_PHONE_NUMBER message: type: string description: Human-readable explanation. responses: InternalServerError: description: >- `INTERNAL_SERVER_ERROR` — unexpected server error. Retry with backoff and contact the 11x team if it persists. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: INTERNAL_SERVER_ERROR message: Internal Server Error. Please contact 11x team. securitySchemes: apiKeyAuth: type: apiKey in: header name: x-api-key description: Organization API key. Get it from the 11x team or from the platform. ````