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

# Developer Documentation

> Public API, webhooks, export format schemas, and MCP server for Ozu — coming soon.

<Note>
  **Coming soon**

  Ozu's developer platform is in active development. These docs are here as a placeholder — detailed reference will land alongside each capability as it ships. If you're interested in early access, reach out via the Ozu website.
</Note>

The Dev section will document everything you need to integrate Ozu into a larger workflow, pipeline, or agent. It's the companion to the user docs for teams building on top of the product.

## What this section will cover

<Columns cols={2}>
  <Card title="Public REST API">
    Programmatic access to projects, assets, storyboards, and exports. Create projects, trigger generations, and pull results from your own systems.
  </Card>

  <Card title="Webhooks">
    Event notifications for generation lifecycle — pending, running, complete, failed. Wire Ozu into your own queue, dashboard, or notification system.
  </Card>

  <Card title="MCP Server">
    Model Context Protocol server for agent-driven workflows. Lets Claude, Cursor, and other MCP clients drive Ozu from their own conversational or automated pipelines.
  </Card>

  <Card title="Export schemas">
    Exact formats for every export type — PDF Storyboard layout, ZIP frame naming conventions, MP4 metadata. Useful when building tools that consume Ozu output.
  </Card>
</Columns>

## Timeline

We're shipping developer capabilities in phases. The public API and webhooks are the highest priority; the MCP server follows once the API surface stabilises; export schema documentation lands alongside each export format.

Specific dates aren't public yet — we'd rather ship docs that match real capabilities than publish a roadmap that slips.

## Early access

If you're building a product or workflow that would benefit from programmatic Ozu access before the public launch, we'd like to hear from you. Reach out via the contact channel on the Ozu website and describe what you're building.

## In the meantime

The [user documentation](/user/getting-started/) covers the full product end-to-end. Everything that'll eventually be available through the API is already available through the app — the API is an alternate surface, not new functionality.

## Related

<Columns cols={2}>
  <Card title="Getting Started" href="/user/getting-started">
    The user-facing walkthrough — what the API will eventually expose.
  </Card>

  <Card title="Pipeline and Nodes" href="/user/concepts/pipeline-and-nodes">
    The conceptual model the API will reflect.
  </Card>

  <Card title="Export Formats" href="/user/export/export-formats">
    The output formats whose schemas will be documented here.
  </Card>
</Columns>