docs: compose trim example + valid URL + drop filler

guides/webhooks.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Webhooks for job events"
-description: "Receive job status events via signed HMAC POST. Setup, payload format, signature verification, 3-attempt retry policy. Available on all plans."
+description: "Receive job status events via signed HMAC POST. Setup, payload format, signature verification, 3-attempt retry policy."
 sidebarTitle: "Webhooks"
 icon: "bell"
 keywords: ["webhooks", "hmac signature", "job status webhook", "rendobar webhook setup", "signed webhook"]
@@ -25,7 +25,7 @@
   }}
 />
 
-Rendobar POSTs JSON to your endpoint when a [job](/concepts/job) changes status. Available on all plans, including Free.
+Rendobar POSTs JSON to your endpoint when a [job](/concepts/job) changes status.
 
 ## Set up a webhook
 
@@ -87,7 +87,7 @@
         "meta": { "format": "mp4", "width": 1920, "height": 1080, "durationMs": 127500 }
       }
     ],
     "expiresAt": 1707440415000
   },
   "cost": { "amount": 50000000, "currency": "USD", "formatted": "$0.05" },
   "timing": {
@@ -201,7 +201,7 @@
 ## Best practices
 
 - **Return 200 fast.** Process asynchronously. Long handlers trigger retries → duplicate deliveries.
 - **Deduplicate** on `X-Rendobar-Delivery` or `jobId`. Same event can arrive more than once.
 - **Verify every signature** before reading the body.
 
 ## See also

jobs/compose.mdx

@@ -1,7 +1,7 @@
 ---
 title: "Compose: render from a timeline"
 sidebarTitle: "Compose"
-description: "Render a video from a declarative JSON timeline. Tracks, clips, transitions, text, and per-clip effects, in one API call."
+description: "Render a video from a declarative JSON timeline. Tracks, clips, transitions, text, and per-clip effects."
 icon: "film"
 keywords: ["video compose api", "json timeline to video", "video transitions api", "video editing api", "compose"]
 canonical: "https://rendobar.com/docs/jobs/compose"
@@ -15,7 +15,7 @@
       "@type": "TechArticle",
       "@id": "https://rendobar.com/docs/jobs/compose/#article",
       "headline": "Compose: render from a timeline",
-      "description": "Render a video from a declarative JSON timeline. Tracks, clips, transitions, text, and per-clip effects, in one API call.",
+      "description": "Render a video from a declarative JSON timeline. Tracks, clips, transitions, text, and per-clip effects.",
       "datePublished": "2026-06-21",
       "dateModified": "2026-06-22",
       "author": { "@type": "Organization", "@id": "https://rendobar.com/#organization" },
@@ -29,7 +29,7 @@
 
 ## Your simplest render
 
-The smallest timeline is one track with one clip. This trims three seconds of a video and renders it to MP4. The whole API call:
+The smallest timeline is one track with one clip. This renders the first three seconds of a video to MP4. The whole API call:
 
 <CodeGroup>
 
@@ -54,8 +54,7 @@
             {
               asset: {
                 type: "video",
-                src: "https://cdn.rendobar.com/assets/examples/a.mp4",
-                trim: { from: 0, to: 3 },
+                src: "https://cdn.rendobar.com/assets/examples/sample.mp4",
               },
               start: 0,
               length: 3,
@@ -93,8 +92,7 @@
                             {
                                 "asset": {
                                     "type": "video",
-                                    "src": "https://cdn.rendobar.com/assets/examples/a.mp4",
-                                    "trim": {"from": 0, "to": 3},
+                                    "src": "https://cdn.rendobar.com/assets/examples/sample.mp4",
                                 },
                                 "start": 0,
                                 "length": 3,
@@ -128,8 +126,7 @@
               {
                 "asset": {
                   "type": "video",
-                  "src": "https://cdn.rendobar.com/assets/examples/a.mp4",
-                  "trim": { "from": 0, "to": 3 }
+                  "src": "https://cdn.rendobar.com/assets/examples/sample.mp4"
                 },
                 "start": 0,
                 "length": 3
@@ -145,9 +142,11 @@
 </CodeGroup>
 
 <Info>
 **Assets:** video, image, text, audio, composition · **Output:** mp4 / webm / gif / mp3 (audio only) / jpg / png (still frame)
 </Info>
 
+Without `trim`, a clip plays its source from the start for `length` seconds. To use a specific segment instead, add `trim: { from, to }` (in source seconds) to the asset. `length` is always the timeline duration. `trim` only chooses which part of the source fills it.
+
 That is the shape of every render. Everything below is one more clip, one more track, or one more field.
 
 ## Join two clips
@@ -357,13 +356,13 @@
 
 | Field | What it does |
 | --- | --- |
 | `opacity` | `0`..`1`, or keyframes `[{ time, value, easing: step \| linear \| smooth }]` |
 | `transform` | `position {x,y}`, `scale`, `rotate`, `anchor` (`center` \| `topLeft`), `fit` (`contain` \| `fill`), `animateTo` (Ken Burns end state) |
 | `crop` | `top` / `right` / `bottom` / `left`, each a percent string like `"10%"` |
 | `speed` | playback rate (`0.5` = slow motion, `2` = fast, and pitch shifts with speed) |
 | `color` | `brightness` (-1..1), `contrast` (0..4), `saturation` (0..3), `gamma` (0.1..10), `hue` (-180..180), `temperature` (1000..40000 K) |
 | `filter` | `greyscale`, `negative`, `boost`, `muted`, `lighten`, `darken`, `contrast` (mutually exclusive with `color`) |
 | `blur` / `sharpen` | gaussian blur strength / unsharp amount |
 | `chromaKey` | `color` (hex), `similarity` (0..1) |
 | `blendMode` | `normal`, `multiply`, `screen`, `overlay`, `darken`, `lighten`, `add`, `difference` |
 | `pan` | stereo balance, `-1` (left) to `1` (right) |

support/faq.mdx

@@ -1,7 +1,7 @@
 ---
 title: "Frequently asked questions"
 sidebarTitle: "FAQ"
 description: "Get quick answers about Rendobar pricing, supported formats, AI agent access, rate limits, and what counts as a failed job."
 icon: "circle-question"
 keywords: ["rendobar faq", "video api faq", "rendobar pricing faq", "ffmpeg api questions"]
 canonical: "https://rendobar.com/docs/support/faq"
@@ -45,7 +45,7 @@
           "name": "Can I drive Rendobar from an AI agent?",
           "acceptedAnswer": {
             "@type": "Answer",
-            "text": "Yes. Connect any MCP-compatible agent to https://api.rendobar.com/mcp with your API key. Six typed MCP tools (submit_job, get_job, list_jobs, probe_media, get_account, upload_media). Available on all plans."
+            "text": "Yes. Connect any MCP-compatible agent to https://api.rendobar.com/mcp with your API key. Six typed MCP tools (submit_job, get_job, list_jobs, probe_media, get_account, upload_media)."
           }
         },
         {
@@ -100,15 +100,15 @@
 </Accordion>
 
 <Accordion title="What can I do with Rendobar today?">
   The live API is the `ffmpeg` job type, any whitelisted FFmpeg command against URLs you provide. That covers transcoding, trimming, filtering, overlays, audio extraction, frame extraction, and anything else FFmpeg does from the command line. More dedicated job types are on the roadmap.
 </Accordion>
 
 <Accordion title="What video formats are supported?">
   Every FFmpeg-compatible container and codec for input. Output defaults to the extension in your trailing filename (`output.mp4` → MP4). Override with `params.outputFormat`.
 </Accordion>
 
 <Accordion title="Can I drive Rendobar from an AI agent?">
-  Yes. Connect any MCP-compatible agent to `https://api.rendobar.com/mcp` with your API key. Six typed MCP tools: `submit_job`, `get_job`, `list_jobs`, `probe_media`, `get_account`, `upload_media`. Available on all plans. See [MCP overview](/mcp-server).
+  Yes. Connect any MCP-compatible agent to `https://api.rendobar.com/mcp` with your API key. Six typed MCP tools: `submit_job`, `get_job`, `list_jobs`, `probe_media`, `get_account`, `upload_media`. See [MCP overview](/mcp-server).
 </Accordion>
 
 <Accordion title="How long do jobs take?">
@@ -120,7 +120,7 @@
 </Accordion>
 
 <Accordion title="What happens if a job fails?">
   Failed jobs are charged for the compute they used. Rendobar has no auto-refund. If you believe a failure was caused by a Rendobar bug or platform issue, contact support and we will review for a discretionary refund. Successful and failed jobs are billed the same way: for the compute the job consumed. Inspect `error.code` and `error.message` on the job, and retry via `POST /jobs/{id}/retry` if appropriate. [Error codes](/support/errors).
 </Accordion>
 
 <Accordion title="Can I run custom FFmpeg commands?">
@@ -128,12 +128,12 @@
 </Accordion>
 
 <Accordion title="How do I get push updates instead of polling?">
   Configure a [webhook](/guides/webhooks) endpoint on your organization. Rendobar POSTs signed JSON when jobs change status. The dashboard uses a WebSocket internally. Programmatic push is webhook-only.
 </Accordion>
 
 </AccordionGroup>
 
 For more about what Rendobar can do, see [rendobar.com](https://rendobar.com) or [rendobar.com/pricing/](https://rendobar.com/pricing/). For head-to-head comparisons with other video APIs, see [rendobar.com/vs/](https://rendobar.com/vs/).
 
 ## Related