Rendley docs

Follow-up prompts

Every edit runs inside a thread. Pass the thread back and the agent builds on what it already did instead of starting over.

Follow-up edits

Send another request with the same project_id and thread_id. The agent keeps its full context, so “make the intro shorter” is enough.

curl -X POST https://api.rendley.com/v1/agent \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "prompt": "Make the intro shorter and add a call-to-action at the end.",
    "project_id": "3f0d5a4e-3d2a-4c1f-9b3e-2a1c4d5e6f70",
    "thread_id": "7e5b3c19-4d82-4a76-9f01-6c8d2b5a3e47"
  }'

project_id is required whenever you pass thread_id. A thread without its project is a 400.

Omit thread_id to start a new thread when the request is unrelated. A thread carries its whole history, so reusing one across videos misleads the agent.

One edit per project at a time. A second returns 409 AGENT_PROJECT_BUSY with the blocking job’s id and status. If that job is waiting_input, answer it instead of starting over. A new run abandons the paused one, re-plans, and re-charges the same steps.

Example Follow-Up prompts

Threads keep context, so follow-up instructions can be short and conversational:

GoalPrompt
Tighten the intro"Make the intro shorter: cut it to 5 seconds."
Add captions"Add auto-captions with a bold white style."
Change music"Replace the background music with something upbeat."
Adjust pacing"Speed up the middle section by 1.5x."
Add a CTA"Add a subscribe call-to-action card at the end."

The agent applies each change on top of the previous result, so edits accumulate.

Thread management

Threads are lightweight and do not expire on their own. Three rules cover most cases:

  • One thread per video project. Reuse the thread as long as changes relate to the same video.
  • New thread for a new video. Omit thread_id when you switch to a different project or an unrelated concept.
  • Do not fork threads. Sending the same thread_id in two parallel requests produces a race condition. Wait for one edit to finish before starting the next.