framefields vs Runway API

framefields

A free Apache-2.0 library that renders video from TypeScript on the GPU, with lint and QA codes an agent can act on. It is fifteen days old, called beta, and its Claude Code install command names a plugin directory entry that was not found on 20 October 2026.

Runway API

OpenAPI 3.1, llms.txt and Markdown copies of every docs page. Gen-3 Alpha Turbo and Gen-4 Aleph were removed on 2026-07-30 with no prior notice in the changelog.

framefields

1. Add the plugin with /plugin marketplace add gatewai-dev/framefields first; the official-directory install was not found on 20 October 2026.
2. Approve only the skia-canvas install script, as the getting-started page shows, or imports fail with a missing skia.node.
3. Check with comp.lint() and renderFrameGrid before a full renderVideo encode.
4. Call process.exit() after rendering; native GPU threads keep the script alive.
5. Preload vision models into FRAMEFIELDS_MODELS_DIR for offline or CI renders.

Runway API

1. Send X-Runway-Version: 2024-11-06 on every request or it fails
2. Use the SDK's wait-for-output helper or poll GET /v1/tasks/{id} until SUCCEEDED or FAILED
3. Don't retry a SAFETY.* failure unchanged. It's moderation, not an outage
4. Take model IDs from the models page, not memory. Two were removed without notice on 2026-07-30
5. Copy outputs to your own storage. URLs expire within 24 to 48 hours