> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cloudservices.ecowestern.net/llms.txt
> Use this file to discover all available pages before exploring further.

# ClearLake overview

> Understand buckets, objects, visibility, and transfers

ClearLake provides private and public object storage.

**Base path:** `/v1/clearlake`

<CardGroup cols={3}>
  <Card title="Buckets" icon="archive" href="/services/clearlake/buckets">
    Choose private or public storage and manage bucket lifecycle.
  </Card>

  <Card title="Objects" icon="folder-tree" href="/services/clearlake/objects">
    Organize, list, inspect, and delete objects by key.
  </Card>

  <Card title="Transfers" icon="arrow-up-down" href="/services/clearlake/transfers">
    Move bytes through short-lived upload and download URLs.
  </Card>
</CardGroup>

## Typical workflow

1. Create a bucket and choose its visibility.
2. Request an upload URL for each object key.
3. Upload directly to the returned URL.
4. List objects or request metadata to verify the upload.
5. Request a download URL when an object needs to be read.
6. Delete objects or the bucket when the data is no longer needed.

## Permissions

| Capability                          | Permission         |
| ----------------------------------- | ------------------ |
| Create bucket or request upload URL | `clearlake:write`  |
| List or inspect buckets and objects | `clearlake:read`   |
| Request download URLs               | `clearlake:read`   |
| Delete buckets or objects           | `clearlake:delete` |

## Data isolation

Each API key can access only the account and resources associated with its scope. Clients do not provide an account selector in ClearLake requests.