The Skribby TypeScript SDK is class-based, so most of what you work with are object instances behind the scenes.
You do not need to instantiate classes manually; use the helper functions to create them.

The SDK is organized around two API shapes:

- **Functions (`F`)** are entry points and factory helpers.
- **Classes (`C`)** are long-lived objects returned by those helpers.

## Functions (`F`)

Start here when creating clients.

- **createClient** (./createClient.md) - Create a `SkribbyClient` for bot creation, lifecycle control, and recordings.
- **createRealtimeClient** (./createRealtimeClient.md) - Create a `RealtimeClient` for low-latency streaming transcription workflows.

## Classes (`C`)

These are the core SDK objects you work with after initialization.

- **SkribbyClient** (./SkribbyClient.md) - Primary API client for creating bots and accessing platform resources.
- **RealtimeClient** (./RealtimeClient.md) - Realtime transport client for receiving live transcription and event updates.
- **MeetingBot** (./MeetingBot.md) - Bot instance API for status checks, lifecycle actions, and bot-specific data.
- **Recording** (./Recording.md) - Recording API for retrieval, metadata access, and transcript-oriented flows.