> For the complete documentation index, see [llms.txt](https://docs.kickbot.com/dashboard/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kickbot.com/dashboard/api/reference/clips.md).

# Clips

KickBot API and MCP reference for Clips. Kick clip downloads and the clip library.

Kick clip downloads and the clip library. MCP area name: `clips`.

| Tool                                          | REST                    | Access |
| --------------------------------------------- | ----------------------- | ------ |
| [`list_clip_downloads`](#list-clip-downloads) | `GET /clips/downloads`  | Read   |
| [`get_kick_clip`](#get-kick-clip)             | `GET /clips/kick`       | Read   |
| [`start_clip_download`](#start-clip-download) | `POST /clips/downloads` | Write  |

## list\_clip\_downloads

**List Kick clip downloads.** List the Kick clips you asked KickBot to download, newest first, with their status (queued, in progress, complete, failed) and the download\_url when complete. Call it again to check the status of a new download.

`GET /api/v1/clips/downloads`

| Field            | Type    | Required | Description                              |
| ---------------- | ------- | -------- | ---------------------------------------- |
| `limit` (query)  | integer | No       | Max items to return (1-100, default 50). |
| `offset` (query) | integer | No       | Number of items to skip (default 0).     |

## get\_kick\_clip

**Look up a Kick clip.** Look up a clip on Kick (title, channel, length, views, thumbnail) before downloading it. Any public Kick clip works, not only clips of your channel.

`GET /api/v1/clips/kick`

| Field          | Type   | Required | Description                                                                                     |
| -------------- | ------ | -------- | ----------------------------------------------------------------------------------------------- |
| `clip` (query) | string | Yes      | The Kick clip URL (<https://kick.com//clips/>) or only the clip id (for example clip\_01HX...). |

## start\_clip\_download

**Download a Kick clip.** Start downloading a Kick clip as an MP4. KickBot looks the clip up on Kick itself, so send only its URL or id. The download usually takes under a minute; check list\_clip\_downloads for the status and download\_url.

`POST /api/v1/clips/downloads`

Needs a read and write key or connection. This has an effect outside your settings (for example on your live stream). Rate limit: 10 per minute, 100 per day.

| Field  | Type   | Required | Description                                                                                     |
| ------ | ------ | -------- | ----------------------------------------------------------------------------------------------- |
| `clip` | string | Yes      | The Kick clip URL (<https://kick.com//clips/>) or only the clip id (for example clip\_01HX...). |

## Need help?

Email <support@kickbot.com> or ask in the `#support` channel on [Discord](https://discord.gg/MAg3gBbc89).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.kickbot.com/dashboard/api/reference/clips.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.