ReelForge DocsAgent-First API
OpenAPIllms.txtSign inMain site

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.

Machine-readable Discovery

ReelForge 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)

Discovery surfaces

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.

How to use them together

  1. Start with llms.txt for orientation.
  2. If request intent is broad, route to docs:
  3. Use OpenAPI to validate exact payload shape and endpoint behavior.
  4. Use llms-full.txt when a single-file, full-context fallback is needed.
  5. Prefer canonical recipe route/field when working with recipes:
    • POST https://api.reelforger.com/v1/recipes/render
    • recipe_id

Practical guidance for agents

  • Use Recipes first for common outcomes.
  • Fall back to Timeline API when recipe controls are not enough.
  • Validate payloads before render in production workflows.