mcpField
F
fetch-api-reference

fetch-api-reference

github.com/runwaymlDevelopment7448 installsUpdated 2d ago
Repository

About fetch-api-reference

A workflow skill that instructs agents to fetch Runway's current API reference before advising on or implementing an integration. It uses the live documentation as the authority for endpoints, models, parameters, and version details.

Key features

  1. 01Fetches the live Runway API reference
  2. 02Uses current docs as the integration source of truth
  3. 03Prioritizes exact paths and parameter values
  4. 04Specifies when to fetch the reference again

Use cases

  1. 01Preparing a Runway API integration
  2. 02Checking an endpoint or parameter before coding
  3. 03Investigating errors caused by possible API changes
  4. 04Resolving conflicts with bundled API summaries

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/runwayml/skills --skill fetch-api-reference

After installing, type/fetch-api-referencein Claude Code to confirm it loaded.

Details

From the project README

Fetch Latest API Reference

Before guiding or implementing any Runway API integration, retrieve the current API reference and use it as the source of truth.

Why This Matters

The Runway API is the official reference. Models, endpoints, request/response shapes, and versioning can change. Using the live docs ensures integration guidance and code match the latest API.

Steps

1. Fetch the API Reference

Retrieve the contents of:

https://docs.dev.runwayml.com/api/

Use your available fetch tool (e.g. mcp_web_fetch or equivalent) to load this URL. The page contains the full API reference: endpoints, request bodies, accepted values, and examples.

2. Use It Before Integrating
  • Before writing or suggesting integration code for video, image, audio, uploads, characters, documents, or any other Runway API feature, use the fetched content as the authoritative reference.
  • Prefer exact endpoint paths, model IDs, parameter names, and header values from the fetched reference over any cached or local documentation.
  • If the fetched content conflicts with text in other skills (e.g. +api-reference or an integrate skill), the fetched docs take precedence for that session.
3. When to Re-Fetch
  • Re-fetch when the user asks to integrate a new capability or when you are unsure about an endpoint or parameter.
  • Re-fetch when the user reports errors that might be due to API changes (e.g. invalid model name, changed request shape).

After Fetching

Proceed with the relevant integrate skill (+integrate-video, +integrate-image, +integrate-audio, +integrate-uploads, +integrate-characters, +integrate-documents, +integrate-character-embed) using the retrieved reference to guide implementation.

Important Notes

  • Base URL for the API is https://api.dev.runwayml.com.
  • All requests require Authorization: Bearer <RUNWAYML_API_SECRET> and X-Runway-Version: 2024-11-06 (or the version stated in the fetched docs).
  • Do not rely solely on bundled or in-repo API summaries when the user is integrating; the live docs are the source of truth.

Comments

Markdown supported