Let your AI agent guide the implementation

Copy this prompt into ChatGPT, Claude, or another AI agent. It will start by reading the ReelForger docs from llms.txt, then ask you the right questions about what you want to create, what assets you have, and what constraints matter before helping you build the correct API request.

You are my ReelForger implementation assistant.

Start by reading the ReelForger machine-readable docs here:
https://www.reelforger.com/llms.txt

Your role is to help me work out how to create what I want with the ReelForger API.

Important instructions:
- Read the docs first before recommending anything.
- Do not assume I have already provided everything you need.
- Lead the conversation step by step.
- Ask me what I am trying to create.
- Ask me what assets I already have available.
- Ask me about any important constraints or preferences such as format, dimensions, style, branding, timing, captions, overlays, logos, motion, voiceover, platform, or automation tool.
- Help me identify what is missing.
- Recommend the best ReelForger endpoint or workflow based on the docs.
- Once you have enough information, produce the exact JSON request body I should send.
- Where useful, use placeholders like {{video_url}}, {{audio_url}}, {{logo_url}}, {{image_1}}, {{image_2}} so I can use it in Make.com or another automation tool.
- Prefer practical implementation guidance over abstract explanation.

How to respond:
1. First, briefly confirm you have read the ReelForger docs.
2. Then ask me the most useful questions needed to understand:
   - what I want to create
   - what assets I have
   - what constraints or preferences I have
3. After I answer, recommend the best endpoint or workflow.
4. Then tell me if anything is missing or needs transforming first.
5. Then give me the final JSON request body.
6. Then give me a short implementation note for Make.com if relevant.

Please begin by reading the docs and then briefly asking me your first questions.

Overview

Page role: this page explains what ReelForge is and gives a high-level model before path selection.

ReelForge is an AI-agent-native media engine and the easiest video API for AI agents.

In plain English: your agent gives ReelForge structured media inputs (URLs + JSON), and ReelForge handles the annoying parts of video assembly - timing, layering, motion, captions, rendering, and async job delivery.

What ReelForge is designed for

Programmatic short-form video generation from public media URLs
Agent-driven workflows where reliability and predictable request shapes matter
Fast iteration: validate payloads, render asynchronously, retrieve output URLs

What you can build

You can create almost anything from social explainers to listicles, slideshows, talking-head caption clips, and fully custom compositions.

The docs are organized so you can choose the right level of control:

Recipes: higher-level, guided path for common outcomes
Timeline API: lower-level custom composition control

If you are unsure, start with Recipes.

Orientation boundaries

Use this page when

You need a high-level model of ReelForge before choosing an API path.
You need quick navigation to canonical docs and machine-readable surfaces.

Do not use this page when

You already know your target request shape and need field-level detail.
You need immediate implementation examples for a specific pattern.

Switch paths from here

Go to Start Here for Agents for practical orientation flow.
Go to Supported Output Patterns when the user request needs capability matching.
Go to Recipes Overview or Timeline Overview once you choose a path.

Recommended path

Use Start Here for Agents as the canonical decision tree and execution flow owner:

choose path (Recipes or Timeline)
validate payload
render asynchronously
retrieve via jobs polling or webhooks

Recipes vs Timeline (quick version)

Use Recipes when you want speed and a clear request shape (POST https://api.reelforger.com/v1/recipes/render, canonical field: recipe_id)
Use Timeline API when you need explicit, low-level control over layers, timing, layout, and media behavior

Recipes Overview: /docs/recipes
Timeline Overview: /docs/timeline-api

Machine-readable discovery (quick links)

Use https://www.reelforger.com/llms.txt and https://api.reelforger.com/v1/openapi.json for agent discovery and contract parsing.

https://www.reelforger.com/llms.txt - agent-oriented discovery and docs context
https://api.reelforger.com/v1/openapi.json - machine-readable API contract

For details, see the Machine-readable Discovery page.