> ## 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. # List Datasets visible to the caller > Returns Datasets whose source sessions belong to workspaces the caller can access, newest first. ## OpenAPI ````yaml /api-reference/openapi.yaml get /v1/datasets 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/datasets: get: tags: - Datasets summary: List Datasets visible to the caller description: | Returns Datasets whose source sessions belong to workspaces the caller can access, newest first. operationId: listDatasets responses: '200': description: Dataset list content: application/json: schema: $ref: '#/components/schemas/DatasetListResponse' '401': $ref: '#/components/responses/Unauthorized' components: schemas: DatasetListResponse: type: object required: - data properties: data: type: array items: $ref: '#/components/schemas/Dataset' Dataset: type: object required: - id - tenant_id - session_id - run_id - name - output - row_count - source - created_at properties: id: type: string format: uuid tenant_id: type: string format: uuid session_id: type: string run_id: type: string name: type: string minLength: 1 maxLength: 120 output: $ref: '#/components/schemas/DatasetOutput' row_count: type: integer minimum: 1 source: type: string enum: - session created_at: type: string format: date-time ErrorResponse: type: object required: - error - message properties: error: type: string message: type: string DatasetOutput: type: object required: - schema - rows properties: schema: type: array description: > Column list. Entries are typed `{ name, type }` objects; bare strings are the older untyped form. The server infers a type for every untyped entry on any write that carries `output` (promote, cell edit, type override), so such a write migrates an untyped schema to typed form. A name-only update is metadata-only and deliberately leaves `output` untouched — rewriting it from the row snapshot read earlier in the request would revert a concurrent cell edit. Readers must therefore accept both forms. items: oneOf: - type: string - $ref: '#/components/schemas/DatasetColumn' rows: type: array minItems: 1 items: type: object additionalProperties: true DatasetColumn: type: object required: - name - type properties: name: type: string minLength: 1 type: $ref: '#/components/schemas/DatasetColumnType' DatasetColumnType: type: string enum: - text - number - boolean responses: Unauthorized: description: Authentication required or invalid credentials. 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.