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

# Introduction

> One API for monitoring sources, running agents, and analyzing your library.

The **clipping API** is a single HTTP API, under `/v1`, for everything the
platform does: monitor sources (YouTube channels, videos, RSS, X), transcribe
and analyze them with agents, organize them into collections, and search over the
whole library.

## The model

<CardGroup cols={2}>
  <Card title="Items" icon="rss">
    A monitored source — a YouTube channel, a single video, an RSS feed. The
    atomic unit; everything else points back to items.
  </Card>

  <Card title="Collections" icon="folder">
    Groups of items. Private or public; can be **paid** (fans subscribe).
  </Card>

  <Card title="Reporters" icon="robot">
    Agents that process sources. A reporter runs **workflows** (ordered
    **steps**, each a tool + prompt) and can run on a **schedule**.
  </Card>

  <Card title="Executions" icon="diagram-project">
    Every run (transcript, workflow, schedule) creates an execution you can
    track to completion.
  </Card>

  <Card title="Transcripts & documents" icon="file-lines">
    Artifacts produced from items: transcripts (one per language) and documents
    (summaries and other workflow output).
  </Card>

  <Card title="Search & discover" icon="magnifying-glass">
    Semantic search over your library, plus a public catalog (`discover`) of
    collections, reporters and users.
  </Card>
</CardGroup>

How they relate:

```
item ──(grouped into)──▶ collection
item ──(produces)──────▶ videos · transcripts · documents
reporter ──(has)───────▶ workflow ──(has)──▶ steps (tool + prompt)
reporter ──(runs on)───▶ schedule ──(targets)──▶ collections
run (transcript / workflow / schedule) ──▶ execution
```

## Base URL

The whole API lives under `/v1`:

```
https://api.clipping.cc/v1
```

## Two credentials, one API

The same endpoints accept **either** credential — only the billing differs:

* **API key** (`ck_live_…`) — for integrators. Drawn per call from the key's
  balance (flat platform fee + pass-through). This is what these guides use.
* **Session JWT** — what the web app uses (from `POST /v1/auth/login`). No
  platform fee, only pass-through.

See [Authentication](/en/authentication) and [Billing](/en/billing).

<Card title="Next" icon="arrow-right" href="/en/quickstart">
  Make your first call in the [quickstart](/en/quickstart), then read
  [Core concepts](/en/concepts) — especially [asynchronous operations](/en/async-operations),
  which most write endpoints rely on.
</Card>