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.

Machine-readable Discovery

ReelForger exposes canonical machine-readable surfaces for agent discovery and contract validation.

Use these together so agents can orient quickly, then validate strictly:

• https://www.reelforger.com/llms.txt
• https://api.reelforger.com/v1/openapi.json
• https://www.reelforger.com/llms-full.txt (extended context)
• https://mcp.reelforger.com/mcp (agent-tool execution endpoint)

ReelForger also exposes a separate async Music API for prompt-driven music generation before render:

• POST https://api.reelforger.com/v1/music/generate
• GET https://api.reelforger.com/v1/music/jobs/{jobId}

For MCP clients, ReelForger also provides a thin remote MCP tool layer over those same API contracts.

Discovery surfaces

• https://www.reelforger.com/llms.txt Use this as the routing/orientation layer (what ReelForger is, main paths, where to go next).

• https://api.reelforger.com/v1/openapi.json
  Use this as the contract layer (strict endpoint/request/response schemas).

• https://www.reelforger.com/llms-full.txt Use this as the extended context layer when an agent needs broad docs recall in one file.

• https://mcp.reelforger.com/mcp Use this as the execution layer for tool-native agent calls (render_recipe, render_timeline, validate_request, get_job_status).

Surface responsibilities

• llms.txt: first stop for routing and path selection.
• OpenAPI (https://api.reelforger.com/v1/openapi.json): source of truth for contract validation.
• llms-full.txt: optional deep context for broader reasoning and fallback lookup.
• MCP remote tools (V1): thin JSON-RPC wrapper for agent execution ergonomics; not a separate logic platform.

How to use them together

1. Start with llms.txt for orientation.
2. If request intent is broad, route to docs:
   • Start Here for Agents
   • Supported Output Patterns
3. Choose the primary render authoring path:
   • Recipes for guided/common outcomes
   • Timeline API for full-manifest, maximum-control rendering
4. If the user needs ReelForger to create music first, route to Music API.
5. Use OpenAPI to validate exact payload shape and endpoint behavior.
6. Use llms-full.txt when a single-file, full-context fallback is needed.
7. Prefer canonical recipe route/field when working with recipes:
   • POST https://api.reelforger.com/v1/recipes/render
   • recipe_id
8. If executing via MCP, call https://mcp.reelforger.com/mcp with bearer auth and use the render -> status polling loop.

Practical guidance for agents

• Use Recipes first for common outcomes.
• Fall back to Timeline API when recipe controls are not enough or when the user needs full control over timing, layout, layering, and media behavior.
• Use Music API first when the user needs generated background music before the render request can be built.
• Validate payloads before render in production workflows.
• If using MCP, prefer pass-through per-user API key auth and treat MCP outputs as direct wrappers over ReelForger API behavior.
• Use raw API directly when you need direct HTTP integration or lower-level contract control.

Next links

• Start Here for Agents
• Supported Output Patterns
• Recipes Overview
• Timeline API Overview
• Music API
• MCP Remote Tools (V1)