> ## Documentation Index > Fetch the complete documentation index at: https://docs.lusor.ai/llms.txt > Use this file to discover all available pages before exploring further. # Read one older page of an agent's turn history > Cursor (keyset) pagination over the stable `(created_at, id)` session ordering, walking BACKWARDS from newest to oldest. Offsets are not supported on purpose: a turn arriving mid-scroll shifts every offset by one, so consecutive offset pages both duplicate and drop rows. The page unit is the session row, not the turn. A session bundles its markers and events, so a turn is never split across a page boundary; the turn count per page is therefore normally `limit` but can exceed it for older rows carrying several markers. Omitting `cursor` returns the newest page. `turns` is oldest-first, so a client prepends the array verbatim. `nextCursor` is null once history is exhausted. ## OpenAPI ````yaml /api-reference/openapi.yaml get /v1/agents/{id}/turns openapi: 3.1.0 info: title: Lusor API version: 0.1.0 description: | Run AI agents on real phones, or drive a phone directly with deterministic actions. ## Authentication Every `/v1/*` endpoint except `GET /v1/health` requires an API key. Create one in the Lusor dashboard under **Settings → API Keys**. A key is shown once and is bound to one workspace. Revoking it there stops it working immediately. Send it in either header: - `X-Api-Key: ` - `Authorization: Bearer ` Because a key is bound to its workspace, `workspaceId` query and body parameters are optional for API-key callers. A request that names a different workspace returns an opaque `404`. ## Runs Use `POST /v1/agents/{id}/turns` to start or continue an agent run. Read the run under `/v1/sessions/{id}`; poll `GET /v1/sessions/{id}/status` or `GET /v1/sessions/{id}/events` for progress. ## Errors Errors are JSON: `{ "error": "", "message": "" }`. A request that fails validation returns `400` in one of two shapes, depending on the endpoint: `{ "error": "validation_error", "details": { ... } }` (direct phone control actions, for example), or `{ "error": "bad_request", "message": "" }` (agent endpoints, for example). Branch on `error`. contact: name: Lusor url: https://lusor.ai license: name: Proprietary url: https://lusor.ai/terms servers: - url: https://api.lusor.ai description: Production security: - ApiKey: [] - BearerAuth: [] tags: - name: Agents description: Persistent agents, the phone each one uses, and their turns (runs). - name: Secrets description: | Secrets saved in a workspace (passwords, sign-in details). A run uses them by name through `secrets`; values never travel in a request. - name: Sessions description: | Run records: list, inspect, stop, and read events and artifacts. Start a run with `POST /v1/agents/{id}/turns`, or without an agent through `POST /v1/workspaces/{workspaceId}/devices/{deviceId}/sessions`. - name: LiveView description: | View-only WebRTC live view of a session's phone: signaling, ICE servers, and stream control. API keys get live view only on the customer's own phone, not on a Lusor Phone. - name: Devices description: | The phones in your workspace, and reads of their current screen and UI tree. - name: DeviceVerbs description: | Direct phone control: deterministic actions (tap, swipe, type, key, clear, back, home, recent, screenshot, apps/start, apps/stop) and chains of them. On a Lusor Phone, API-key calls meter phone minutes. - name: Shell description: | Restricted shell escape hatch. Commands are checked against a denylist and audit-logged. No command output is returned. - name: Datasets description: Lists a run produced, saved as reusable Datasets. - name: Skills description: Reusable automation skills (Markdown documents). - name: PhoneNumbers description: | Workspace phone numbers and their stored SMS messages. Read-only for API keys. - name: Emails description: | Workspace Agent Mail addresses and stored inbound mail. Read-only: there is no compose, reply, or send endpoint, and message bodies are returned as raw plain text without HTML execution, remote asset fetches, or code extraction. - name: Workspaces description: The workspace an API key is bound to. - name: Catalog description: The catalog of apps that can be installed on a Lusor Phone. - name: Health description: Service health check. paths: /v1/agents/{id}/turns: get: tags: - Agents summary: Read one older page of an agent's turn history description: | Cursor (keyset) pagination over the stable `(created_at, id)` session ordering, walking BACKWARDS from newest to oldest. Offsets are not supported on purpose: a turn arriving mid-scroll shifts every offset by one, so consecutive offset pages both duplicate and drop rows. The page unit is the session row, not the turn. A session bundles its markers and events, so a turn is never split across a page boundary; the turn count per page is therefore normally `limit` but can exceed it for older rows carrying several markers. Omitting `cursor` returns the newest page. `turns` is oldest-first, so a client prepends the array verbatim. `nextCursor` is null once history is exhausted. operationId: listAgentTurns parameters: - $ref: '#/components/parameters/AgentId' - $ref: '#/components/parameters/WorkspaceIdQuery' - name: cursor in: query required: false description: >- Opaque anchor from the previous page, or `turnsCursor` from the agent detail. schema: type: string maxLength: 512 - name: limit in: query required: false description: Sessions per page. Defaults to 20. schema: type: integer minimum: 1 maximum: 100 default: 20 responses: '200': description: One page of history, oldest-first content: application/json: schema: $ref: '#/components/schemas/AgentTurnPageResponse' '400': $ref: '#/components/responses/ValidationError' '401': $ref: '#/components/responses/Unauthorized' '404': $ref: '#/components/responses/NotFound' components: parameters: AgentId: name: id in: path required: true schema: type: string format: uuid description: >- Agent UUID. Missing, inaccessible, and malformed IDs return an opaque 404. WorkspaceIdQuery: name: workspaceId in: query required: false schema: type: string format: uuid description: | Workspace the request is scoped to. Optional for API keys: a key is bound to one workspace when it is created, and naming any other workspace returns an opaque 404. schemas: AgentTurnPageResponse: type: object required: - data properties: data: $ref: '#/components/schemas/AgentTurnPage' AgentTurnPage: type: object required: - turns - nextCursor - hasMore properties: turns: description: Oldest-first, so the client prepends the array verbatim. type: array items: $ref: '#/components/schemas/AgentTurn' nextCursor: type: - string - 'null' hasMore: type: boolean ValidationErrorResponse: type: object required: - error - details properties: error: type: string example: validation_error details: type: object additionalProperties: true ErrorResponse: type: object required: - error - message properties: error: type: string message: type: string AgentTurn: type: object required: - id - sessionId - prompt - status - deviceId - summary - recording - queued - createdAt - startedAt - completedAt properties: id: type: string description: Turn id. For older turns this is the session id. sessionId: type: string prompt: type: string status: type: string deviceId: type: - string - 'null' summary: type: - string - 'null' recording: type: boolean queued: type: boolean createdAt: type: string format: date-time startedAt: type: - string - 'null' format: date-time completedAt: type: - string - 'null' format: date-time responses: ValidationError: description: | Request validation failed. Either `validation_error` with per-field `details`, or `bad_request` with a `message`, depending on the endpoint. content: application/json: schema: anyOf: - $ref: '#/components/schemas/ValidationErrorResponse' - $ref: '#/components/schemas/ErrorResponse' Unauthorized: description: Authentication required or invalid credentials. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' NotFound: description: Resource not found. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' securitySchemes: ApiKey: type: apiKey in: header name: X-Api-Key description: Workspace API key, created in the dashboard under Settings → API Keys. BearerAuth: type: http scheme: bearer description: >- The same workspace API key, sent as `Authorization: Bearer `. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.