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://jentic.com/install.sh?src=apis&api=%2Fapis%2Frunway.team%2Frunway-team" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Frunway.team%2Frunway-team" | 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

List releases

Use Cases

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

GET STARTED

Start building with Runway REST API

Explore with Jentic One

View OpenAPI Document

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

GET

/app/{appId}/bucket

List all buckets

GET

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

Get a bucket's details

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Runway REST API by hand means minting its API key, attaching it to every request to api.runway.team, and handling your own retries. Through Jentic you install once, import the Runway REST API from the API Directory, store the key once, and your agent calls it.

Permission scoping

Runway puts the app id in the URL path (/app/{appId}/...), so a rule can pin your agent to one app: it can read that app and list its releases and buckets and nothing else. You choose the operations it may call, so creating a release or a bucket is not included unless you add it.

Credential isolation

Your Runway REST API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'get app details' or 'list releases for an app', and Jentic returns the matching Runway REST API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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.

Can I limit what my agent is allowed to do with the Runway REST API?

Yes. Jentic One is self-hosted by you, so your own rules decide which Runway operations and credentials the agent may use. Because Runway puts the app id in the URL path (/app/{appId}/...), you can pin the agent to a single app and allow only read operations such as GET /app/{appId}, GET /app/{appId}/release, and GET /app/{appId}/bucket. Write operations like POST /app/{appId}/release or POST /app/{appId}/bucket are not available to the agent unless you explicitly add them.

Runway Team Runway REST API

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

Official vendor OpenAPI document · agent-readyIdentity 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

Not supported: Does not handle payments, communications, or crm - use for identity and authentication only.

Runway (runway.team) is a release management platform for mobile app teams. The REST API allows you to access information about your releases in Runway. Authentication via X-API-Key header. The API exposes 15 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Connect the Runway REST API to your agent

Capabilities

Use Cases

Start building with Runway REST API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Runway Team Runway REST API