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

# Introduction

> Turn code into a narrated video walkthrough — programmatically.

## What is pull/story?

Pull/story turns a structured code brief into a **narrated video walkthrough** — complete with auto-generated architecture diagrams, code panels, and scene-by-scene narration explaining how the system works.

The API lets you generate and retrieve pull stories without leaving your terminal, CI pipeline, or editor.

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Generate your first pull story in under 2 minutes.
  </Card>

  <Card title="Claude Code" icon="terminal" href="/integrations/claude-code">
    Ask Claude Code "make a video explaining this feature" and get a pull story link back automatically.
  </Card>

  <Card title="Authentication" icon="key" href="/authentication">
    Mint an API key from the dashboard.
  </Card>

  <Card title="API Reference" icon="code" href="/api-reference/stories/create-story">
    Every endpoint, every parameter, every response.
  </Card>
</CardGroup>

## Three ways to use pull/story

<AccordionGroup>
  <Accordion title="1. GitHub App (zero-setup, automatic)">
    Install the pull/story GitHub App on any repo to auto-generate pull stories from PR activity where supported.

    No API calls required.
  </Accordion>

  <Accordion title="2. REST API (programmatic)">
    Use the REST API to generate pull stories from CI, scripts, internal tools, or anywhere you write code. Authenticate with a bearer token, `POST /api/v1/stories`, poll until ready.

    [Jump to the Quickstart →](/quickstart)
  </Accordion>

  <Accordion title="3. MCP server (for agents)">
    Pull/story exposes an [MCP server](/integrations/mcp-setup) that Claude Code, Claude Desktop, Cursor, or any MCP-compatible agent can call as a tool.

    Ask the agent "make a video explaining this feature" and it reads the relevant files, builds the brief, then calls our API to generate and return the story link.
  </Accordion>
</AccordionGroup>

## How billing works

Pull/story is metered by **video length**, not request count.

| Plan     | Included                     | Overage                             |
| -------- | ---------------------------- | ----------------------------------- |
| **Free** | 10 minutes of video / month  | Generation blocked until next cycle |
| **Pro**  | 120 minutes of video / month | `$19 / month`, overage blocked      |

A typical brief generates 1-3 minutes of video. Most developers on the free plan never hit the limit.

## Base URL

All requests are served from:

```
https://pullstory.com/api/v1
```

## SDK & MCP

<CardGroup cols={2}>
  <Card title="MCP Server" icon="plug" href="/integrations/mcp-setup">
    `@pullstory/mcp` — drop-in tool for Claude Code, Cursor, Windsurf.
  </Card>

  <Card title="Claude Code workflow" icon="terminal" href="/integrations/claude-code">
    Ask Claude Code to create the pull story from your editor.
  </Card>
</CardGroup>

## What reviewers get

Pull/story should make review feel lighter, not add another noisy bot. A good story gives reviewers:

* the intent of the change
* the runtime flow
* the risky files and behaviors
* code-linked chapters
* a transcript they can skim instead of watching

## Support

<CardGroup cols={2}>
  <Card title="X / Twitter" icon="twitter" href="https://x.com/echomosh_">
    Fastest: DM @echomosh\_
  </Card>

  <Card title="Email" icon="envelope" href="mailto:moshikarim@proton.me">
    [moshikarim@proton.me](mailto:moshikarim@proton.me)
  </Card>
</CardGroup>