Runway
Connect Runway to make video, images and audio with its AI models, and manage your avatars, voices and published workflows.
You paste one value into PopMCP: a Runway API key, which starts with key_.
Paid plan required before this connector works
No one reviews you, but the API runs on credits bought in advance for your project. Runway's docs ask you to add credits before you start using the API.
- Typical wait
- None. There is no review, and buying credits is self-serve from the Billing tab.
- Cost
- Runway's setup guide asks for a first payment of at least $10, at $0.01 per credit. Each generation then spends credits by model and length, listed on Runway's pricing page. PopMCP adds nothing to this.
- Blocked until approved
- Generating video, images and audio, running workflows and uploading files.
- Works meanwhile
- Create the project and the API key, then connect it in PopMCP. PopMCP shows the project's credit balance when you connect.
Where to apply: No application. Sign in at dev.runway.com, open your project, go to the Billing tab and add credits. Adding credits needs the Admin or Billing admin role.
- Credits belong to one project, and so does an API key, so create the key in the project that holds the credits.
- A task refused by moderation for its input is not refunded, and repeated refusals can suspend an account.
- Each project has limits per model, set by its usage tier. Going over the number running at once only queues tasks, while going over the daily number is refused until the 24-hour window moves on.
- The workspace usage and audit log reports need an enterprise plan and a linked Runway web app workspace.
- Setup time
- 2 min
- Auth
- API credentials
- API base URL
- https://api.dev.runwayml.com/v1
- Rate limits
- Runway sets limits per model and per project, from the project's usage tier. Going over the number running at once only queues tasks as THROTTLED. Going over the daily number of generations answers 429, counted over a rolling 24 hours. There is no limit on requests per minute, apart from the workspace reports, which allow 10 calls every 10 seconds.
Before you begin
- A Runway developer account at dev.runway.com, with a project. You are asked to create a project after signing up
- Credits on that project, if your AI will generate anything. The Billing tab takes payment, and Runway's setup guide asks for a first payment of at least $10, at $0.01 per credit
- The Admin or Developer role on the project, to create a key. Adding credits needs the Admin or Billing admin role
Get your credentials
Open your project in the developer portal
Sign in at dev.runway.com and open the project you want your AI to use. If you just signed up, create a project when asked. A project holds its own keys and credits, so choose the right one now. You can connect another later with its own key.
Create an API key and copy it
Open the API Keys tab and create a new key. Give it a name like PopMCP, so you can disable this one later without touching your other apps. Runway shows the key only once, so copy it right away. If you lose it, disable it and create a new one.
API Keys
Keys let your apps call Runway's API for this project.
This view is a simplified sketch: the labels on your page may differ slightly. The key starts with key_ and is shown only once.
Add credits if the project has none
Open the Billing tab and add credits. Generations spend them, and uploading files also needs a project that has bought credits. You can do this later, but your AI cannot generate anything until you do.
Paste the key into PopMCP
In PopMCP, paste the key into API key and connect. PopMCP checks it by reading your credit balance from Runway. New connections start read-only, so your AI can read your balance, list models and check tasks but cannot generate anything or spend credits until an owner or admin allows write actions.
Connect in PopMCP
Open your workspace, choose Runway in the marketplace, and fill in the connect dialog:
| Field | What to enter |
|---|---|
| API keysecret | At dev.runway.com, open your project, go to API Keys and create a key. It starts with key_ and is shown only once. Stored encrypted and used only on our servers.Encrypted with AES-256-GCM on save and never shown again. |
PopMCP verifies the credential against Runway immediately. On success the connection flips to Verified and its MCP tools are provisioned.
Verify it worked
PopMCP marks the Runway connection Verified, labels it with the last four characters of your key, and shows the project's credit balance. Asking the AI for your credit balance, then for the video models it can use, returns real results at no cost.
Troubleshooting
"Runway did not accept this API key..."
Why: The key was copied incompletely or has been disabled.
Fix: Open your project at dev.runway.com, go to API Keys and create a new key. Runway shows a key only once, so copy it right away.
"This project has no credits yet..."
Why: The project has not bought any credits. The connection still saves.
Fix: Add credits on the Billing tab at dev.runway.com. This needs the Admin or Billing admin role.
The AI says it cannot generate anything
Why: The connection is read-only, which is how every new connection starts. Generating spends credits, so it counts as a write.
Fix: Have an owner or admin allow write actions on the connection in PopMCP.
"Nothing was started and nothing was spent..."
Why: A field does not fit the model. Ratio, duration and other fields change from model to model.
Fix: The message lists what that model takes. The AI can correct the request and try again.
A task ends as FAILED with a SAFETY code
Why: Runway's content moderation refused the input or the result. It is a failed task rather than an error, and a refusal of the input is not refunded.
Fix: Change the prompt or the media rather than retrying as it is. Repeated refusals can suspend an account.
A task sits at THROTTLED
Why: The project is running as many tasks as its usage tier allows, so this one is queued. It is not an error.
Fix: Wait. It starts on its own, and starting it again would pay twice.
A request is refused with a 429
Why: The project reached its daily number of generations for that model, counted over the last 24 hours.
Fix: Wait for the window to move on, or use another model. The AI can read the limits per model. Runway raises them as a project's spending grows.
An output link no longer opens
Why: Runway's output links expire within 24 to 48 hours.
Fix: Save what you want to keep as soon as a task ends. Past that, generate it again.
A workflow is not found
Why: A key only reaches workflows published to its own project.
Fix: Publish the workflow to this project, or connect the project it belongs to with that project's key.
The workspace usage or audit log reports answer that the key is not accepted
Why: These reports need an enterprise plan and a Runway web app workspace linked under Manage, Connections.
Fix: Link the workspace in the developer portal, which needs the Admin or Billing admin role, or leave these reports aside. Everything else works without them.