> For the complete documentation index, see [llms.txt](https://monkey-gun.gitbook.io/monkeygun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://monkey-gun.gitbook.io/monkeygun/use-cases/overview.md).

# Use cases beyond data

The same API cuts from a URL, a PDF, a folder of footage, a stock ticker or a weather forecast. Here is what to send for each, and what you need set up.

Financial and on-chain data is where the show kits are, but the engine is source-agnostic. Every video starts from a **source pack**: verbatim facts, stills, footage and brand pulled from whatever you gave it. What changes per use case is only the first call.

| You have                          | First call                                              | Then                                    | Guide                                                        |
| --------------------------------- | ------------------------------------------------------- | --------------------------------------- | ------------------------------------------------------------ |
| A JSON snapshot                   | `from-data` with `data`                                 | done                                    | [Data to video](/monkeygun/guides/data-to-video.md)          |
| A web page or PDF                 | `POST /v1/sources { url }` or `from-data { sourceUrl }` | create, render                          | [URL to video](/monkeygun/use-cases/url-to-video.md)         |
| Footage, photos, audio            | `POST /v1/library/upload`, `index_footage`              | create with `libraryAssetIds`           | [Footage to video](/monkeygun/use-cases/footage-to-video.md) |
| A ticker, a city, a currency pair | `market_data`                                           | create with the returned `sourcePackId` | [Other data feeds](/monkeygun/use-cases/other-data.md)       |
| Pasted notes or a script          | `POST /v1/sources { text }` or `from-data { script }`   | create, render                          | [Authored scripts](/monkeygun/guides/authored-scripts.md)    |
| A Google Drive folder             | `import_drive`                                          | as footage                              | [Footage to video](/monkeygun/use-cases/footage-to-video.md) |

## Worked examples

Five shows built from public data, each with the payload, the call and the schedule:

| Show                                  | Data source                     | Page                                                                 |
| ------------------------------------- | ------------------------------- | -------------------------------------------------------------------- |
| Daily exchange movers                 | Kraken public ticker API        | [Exchange movers desk](/monkeygun/use-cases/exchange-movers.md)      |
| Live contest bulletins every 12 hours | A contest referee's public feed | [Live contest desk](/monkeygun/use-cases/contest-desk.md)            |
| Standings and the race of the day     | MLB Stats API                   | [Sports stat desk](/monkeygun/use-cases/sports-desk.md)              |
| Storms and warnings                   | NOAA National Hurricane Center  | [Weather desk](/monkeygun/use-cases/weather-desk.md)                 |
| One collectible a day                 | PriceCharting and TCGplayer     | [Collectible price show](/monkeygun/use-cases/collectible-prices.md) |

## What you need set up, by use case

<details>

<summary>Any use case</summary>

An API key, a webhook endpoint or a poller, and a place to store `renderUrl`. That is the whole integration for one-off videos.

</details>

<details>

<summary>Running shows</summary>

A channel and at least one show with defaults and a brand lock. Either your own scheduler calling `from-data`, or a series that listens. See [Channels, shows and kits](/monkeygun/concepts/channels-shows-kits.md).

</details>

<details>

<summary>Your users making videos</summary>

A backend route that mints embed tokens, a page that iframes the studio, and a webhook handler that attributes by `externalUserId`. See [Embedded studio](/monkeygun/guides/embedded-studio.md).

</details>

<details>

<summary>Footage</summary>

Storage on your side is optional; upload by URL and Monkeygun keeps the file in your library. Budget 20 credits per minute of footage for indexing, once.

</details>

<details>

<summary>Publishing</summary>

Nothing, if you host the file. Connect Buffer in Settings → Publishing to autopost, or use `publish` with `destination: "share-link"` for a hosted page. See [Publishing](/monkeygun/guides/publishing.md).

</details>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://monkey-gun.gitbook.io/monkeygun/use-cases/overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.