> 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/readme.md).

# Introduction

Post a snapshot of your data. Get a branded, grounded short video back. Run it as a show, embed a studio for your users, or both.

Monkeygun turns structured data into short vertical videos. Every number on screen comes from the payload you sent; the renderer draws the numerals itself, so a figure that is not in your data cannot appear in the video. Exchanges, yield protocols and data companies use it to put a video on every listing, pool, wallet and market move, and to let their own users make clips.

* [**Quickstart**](/monkeygun/start-here/quickstart.md) — A token snapshot to a playable MP4 in one call, in under ten minutes.
* [**Packages**](/monkeygun/start-here/packages.md) — Video API, Feed + Creator Studio, Data Shows, and the show kit catalog.
* [**For exchanges**](/monkeygun/start-here/for-exchanges.md) — the one-page brief for growth and product leads: what users see, what it takes, how a pilot runs.
* [**Authored scripts**](/monkeygun/guides/authored-scripts.md) — Write the scenes yourself: charts, stat cards, clips from a logo, Giphy loops, sound design, transitions.
* [**Embedded studio**](/monkeygun/guides/embedded-studio.md) — Put the full studio inside your app so your users create videos on your data.

Not only crypto: the same calls cut from [a URL](/monkeygun/use-cases/url-to-video.md), [your footage](/monkeygun/use-cases/footage-to-video.md) or [stocks, FX and weather](/monkeygun/use-cases/other-data.md).

## How it fits together

```mermaid
flowchart LR
  A[Your data<br/>snapshot, feed, or script] -->|POST /v1/videos/from-data| B[Monkeygun]
  B --> C[Script + voice + visuals]
  C --> D[Render]
  D -->|webhook video.rendered| E[Keyed MP4 URL]
  E --> F[Your feed, share page, socials]
  G[Your users] -->|embed token| H[Studio iframe]
  H --> B
```

Three ways in, one engine underneath:

| Surface             | What you send                                     | What you get                                                                                       |
| ------------------- | ------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
| **from-data**       | A JSON snapshot, a brief, or a full script        | A video, rendering in the background, with a webhook when the file is ready                        |
| **Tool catalog**    | `POST /v1/tools/{name}` with the tool's arguments | Everything the studio can do: sources, quotes, edits, channels, shows, series, library, publishing |
| **Embedded studio** | An embed token for one of your users              | The chat studio inside your page, billed to your account, tagged with your user id                 |

## Live examples

* [Six runnable examples](/monkeygun/examples/monkeygun-examples.md): exchange listing, yield rate split, portfolio recap with the embedded studio, your own footage indexed and cut, a weekly stocks brief, and URL to video. Each with a rendered sample and the script that made it.
* [tokenslop.fun](https://tokenslop.fun) runs a feed of token videos on Robinhood Chain: house shows on a schedule, user-paid promos, and an embedded creator studio, all on this API. See [the tokenslop example](/monkeygun/examples/tokenslop.md).
* [nansen-shows](https://github.com/arambarnett/nansen-shows) is an open-source starter that turns Nansen smart-money data into seven authored shows. See [the Nansen example](/monkeygun/examples/nansen-shows.md).

## Base URL and auth

```
https://api.monkeygun.com/v1
Authorization: Bearer mk_live_…
```

Make a key in the studio under **Settings → Developer**. New accounts start with 500 credits. One credit is one cent. Every paid call returns `charged`.


---

# 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/readme.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.