> ## 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.

# Core concepts

> The objects the Lusor API works with, and how they fit together.

| Concept | What it is |
| - | - |
| **Workspace** | Holds your phones, agents, sessions and API keys. Every API key belongs to exactly one workspace. |
| **API key** | A secret starting with `lusor_` that authenticates every request. See [Authentication](https://docs.lusor.ai/authentication.md). |
| **Phone** | A phone in your workspace. The API calls it a **device** (`/v1/devices`). See [Phones](https://docs.lusor.ai/phones/overview.md). |
| **Lusor Phone** | A cloud phone Lusor runs for you. Agent time on a Lusor Phone uses Lusor Phone minutes. |
| **Your own phone** | A phone you own and connect to your workspace, such as your iPhone or Android phone. It uses no Lusor Phone minutes. |
| **Agent** | A persistent assistant with a name, a model, a history, and at most one phone. See [Create an agent](https://docs.lusor.ai/agents/create-an-agent.md). |
| **Turn** | One task you send to an agent. Each turn creates a **session**. See [Send a turn](https://docs.lusor.ai/agents/send-a-turn.md). |
| **Session** | The record of work on a phone: its status, its step-by-step events, its recording, and its output. You can also start a session on a phone without an agent. See [Follow a session](https://docs.lusor.ai/agents/follow-a-session.md). |
| **Follow-up message** | A new message sent into an existing session, on the same conversation. See [Follow-up messages](https://docs.lusor.ai/agents/follow-up-messages.md). |
| **Credits** | What model usage costs. Every session uses credits, on any phone. See [Credits and minutes](https://docs.lusor.ai/billing/credits-and-minutes.md). |
| **Lusor Phone minutes** | Your plan's monthly allowance of agent time on Lusor Phones. |

## How they fit together

1. A **workspace** holds your **phones** and **agents**.
2. You attach a phone to an agent, then send the agent a **turn**.
3. The turn creates a **session**. The agent works on the phone, and the session records every step.
4. You follow the session until it ends, answer the agent if it asks a question, and read its output.
5. To keep going in the same conversation, send a **follow-up message** to the session, or send the agent its next turn.

You can also skip the agent: start a one-off session on a phone, or [control the phone directly](https://docs.lusor.ai/phones/direct-control.md) with taps, swipes and typing.

## Identifiers

| Id | Where you get it | Where you use it |
| - | - | - |
| Device id | `id` in `GET /v1/devices` | Attaching a phone to an agent, direct control, one-off sessions |
| Agent id | `data.id` of `POST /v1/agents` or `GET /v1/agents` | `/v1/agents/{id}/…` |
| Session id | `sessionId` of a turn, `id` of a one-off session | `/v1/sessions/{id}/…` |
| Workspace id | `workspaceId` of any agent | Endpoints with `{workspaceId}` in the path |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.