Runway Team Runway REST API

Name: Runway REST API
Brand: Runway REST API
Availability: InStock

✓ Official Vendor SpecIdentity AuthAuthenticationapiKey15 EndpointsREST

For Agents

Programmatically api root, health check. Covers 15 operations with apiKey authentication.

Use for: I need to api root, I want to health check, Search for app details, Find all a new release

Install Jentic One Beta

Connect the Runway REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Runway REST API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Runway REST API.

API root

Health check

Get app details

Create a new release

GET STARTED

Start building with Runway REST API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Runway REST API for, with concrete tasks.

★ Identity and Authentication Operations

Use the Runway REST API to perform identity auth operations programmatically. The API provides 15 endpoints covering core functionality including api root, health check, get app details.

Call GET / to api root

Automated app Management

Automate app operations by combining multiple Runway REST API endpoints. Agents can health check and then get app details in a single workflow.

Call GET /status to health check, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Runway REST API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Search Jentic for 'api root', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

15 endpoints — runway (runway.

METHOD

PATH

DESCRIPTION

GET

API root

GET

/status

Health check

GET

/app/{appId}

Get app details

POST

/app/{appId}/release

Create a new release

GET

/app/{appId}/release

List releases

POST

/app/{appId}/bucket

Create a bucket

GET

/app/{appId}/bucket

List all buckets

GET

/app/{appId}/bucket/{bucketId}

Get a bucket's details

GET

API root

GET

/status

Health check

GET

/app/{appId}

Get app details

POST

/app/{appId}/release

Create a new release

GET

/app/{appId}/release

List releases

POST

/app/{appId}/bucket

Create a bucket

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Runway REST API apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'api root') and Jentic returns the matching Runway REST API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Runway REST API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Runway REST API through Jentic.

What authentication does the Runway REST API use?

The Runway REST API uses an API key passed in the `X-API-Key` header. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I api root with the Runway REST API?

Yes. Use the GET / endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Runway REST API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I api root through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'api root'. Jentic returns the matching Runway REST API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the Runway REST API have?

The Runway REST API exposes 15 endpoints covering app, approval, builddistro operations.

Runway Team Runway REST API

Connect the Runway REST API to your agent

Capabilities

Start building with Runway REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs