Developer Documentation

The Dev section will document everything you need to integrate PrePrompt 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

Public REST API

Programmatic access to projects, assets, storyboards, and exports. Create projects, trigger generations, and pull results from your own systems.

Webhooks

Event notifications for generation lifecycle — pending, running, complete, failed. Wire PrePrompt into your own queue, dashboard, or notification system.

MCP Server

Model Context Protocol server for agent-driven workflows. Lets Claude, Cursor, and other MCP clients drive PrePrompt from their own conversational or automated pipelines.

Export schemas

Exact formats for every export type — PDF Storyboard layout, ZIP frame naming conventions, MP4 metadata. Useful when building tools that consume PrePrompt output.

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 PrePrompt access before the public launch, we’d like to hear from you. Reach out via the contact channel on the PrePrompt website and describe what you’re building.

In the meantime

The user documentation 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.

Getting Started The user-facing walkthrough — what the API will eventually expose.

Pipeline and Nodes The conceptual model the API will reflect.

Export Formats The output formats whose schemas will be documented here.