Getting Started · RunningHub API Docs

Platform Overview

🎉

RunningHub API provides multimodal AI and large language model capabilities, allowing developers to integrate image, video, audio, AI Apps, workflows, and LLM models into products or automation pipelines.

RunningHub API mainly includes the following API types:

Type	Description	Call Pattern
Model API	Directly call image, video, audio, and other model capabilities	Submit a task, receive a `taskId`, then query the result
AI App API	Call packaged AI Apps with business-friendly input parameters	Submit a task, receive a `taskId`, then query the result
Workflow API	Call workflows composed of multiple nodes, suitable for complex creative pipelines	Submit a task, receive a `taskId`, then query the result
LLM API	Call large language model capabilities compatible with OpenAI / Anthropic / Gemini protocols	Send requests directly, with regular or streaming responses depending on the endpoint

Model API, AI App API, and Workflow API usually use a task-based flow:

Submit task → Get taskId → Query task status → Get result

LLM API uses compatible protocol endpoints:

Choose model → Send request → Get text or streaming response

Note: Model API and LLM API only support Enterprise-Shared API Keys.

Quick Start

1. Register an Account

Visit RunningHub Global Site

Visit RunningHub, then click Log in / Sign up.

Complete Registration

Get a Personal Account

After registration, you will get a personal account.

Your personal account is the basic identity for using RunningHub. Creating a team, joining a team, creating API Keys, and viewing Tasks & Billing or LLM Logs are all based on this personal account.

After registration, you use your personal account by default. Resources, tasks, balance, and API Keys under the personal account belong to the personal entity.

The personal account is the basic identity for using RunningHub API. Most RunningHub users primarily use personal accounts. Team accounts are built on top of personal accounts to provide unified management for companies or organizations.

2. Personal Account and Team Account

In RunningHub, a team account is not a separate login account. It is an enterprise collaboration and billing entity built on top of personal accounts.

Each user always logs in with their own personal account. After logging in, the user can use the personal account, or create or join a team account.

Personal accounts are suitable for most creators, developers, and individual commercial use cases. Tasks & Billing and LLM Logs are recorded at the personal level. Team accounts are mainly designed for companies or organizations that need member collaboration, team resource and quota allocation, unified billing, and team-level Tasks & Billing and LLM Logs with actual calling members retained.

Item	Personal Account	Team Account
Login	Log in with a personal account	Members still log in with their own personal accounts
Positioning	Default usage entity, suitable for most creators, developers, and individual commercial use	Company or organization entity for unified management and collaboration
Resource Ownership	Resources, tasks, balance, and API Keys belong to the personal account	Team resources, team wallet, member seats, and member quotas can be managed centrally; API Keys created or used under the team account belong to the team entity
API Key Ownership	Personal entity	Team entity
Wallet / Balance	Personal wallet and personal RH coins	Team resource pool, member wallet, and seat benefits
Tasks & Billing / LLM Logs	Recorded at personal level	Recorded at team level, with the actual calling member retained
Suitable For	Personal creation, development integration, individual commercial use	Enterprise calls, member collaboration, unified billing, member and resource management

You can understand it simply as:

Personal account = login identity + default usage entity
Team account = enterprise collaboration and billing entity built on top of personal accounts

Joining a team does not change your personal account, nor does it automatically migrate your personal resources. It only grants your personal account access to a specific team account.

3. Create or Join a Team Account

Create a Team Account

After registering and logging in, you can create a team account in the console.

Become Team Admin

The user who creates the team account automatically becomes the team admin and also a team member. The admin can manage team information, team members, team wallet, member seats, and team bills.

Invite Team Members

Team members join through invitation links. After joining, members still log in with their own personal accounts, but can use resources and permissions assigned under the team account.

Switch to Team Account

After switching to a team account, API Key creation, API consumption, Tasks & Billing, and LLM Logs are handled under the team entity.

If team approval is enabled, joining requires admin approval. If approval is not enabled, members can join directly through the invitation link.

4. Get an API Key

After logging in, visit the API Key page and create a key on the API Key management page.

When calling APIs, include your API Key in the request. The exact parameter location depends on the API and should follow the corresponding API documentation and examples.

Before creating or using an API Key, please confirm:

Whether you are using a personal account or team account

Whether the API Key type matches the target API

Whether your wallet or team balance is sufficient

Whether you need to call Model API or LLM API

Whether you have an Enterprise-Shared API Key

Enterprise-Dedicated API Key can be created only after purchasing a dedicated machine

RunningHub API Keys are mainly divided into three types:

API Key Type	Description
Consumer-Member	Membership API entitlement for personal accounts, suitable for most personal use cases
Enterprise-Shared	Pay-as-you-go enterprise API entitlement, supporting Model API, LLM API, AI App API, and Workflow API
Enterprise-Dedicated	Can be created after purchasing a dedicated machine, suitable for dedicated resource scenarios

Note: Model API and LLM API only support Enterprise-Shared API Keys for direct calls.

Choose an API Key Type

Different API types require different API Key types. Before making a call, confirm the API type you want to use and choose an available API Key.

API Type	Available API Key
Model API	Enterprise-Shared
LLM API	Enterprise-Shared
AI App API	Consumer-Member, Enterprise-Shared, Enterprise-Dedicated
Workflow API	Consumer-Member, Enterprise-Shared, Enterprise-Dedicated

Model API and LLM API only support Enterprise-Shared API Keys. Enterprise-Dedicated API Key can be created only after purchasing a dedicated machine.

For complete call benefits, concurrency quotas, and billing details, click API Key Call Benefit Comparison in the upper-right corner of the API Key page:

Go to API Key page

First API Call

1. Call Model API / AI App API / Workflow API

Model API, AI App API, and Workflow API usually use a task-based flow.

Submit Task

Call the target API and submit task parameters.

Get taskId

The API returns a taskId.

Query Task Result

Use the taskId to query task status and result.

Step 1: Submit a task:

Step 2: Query task result:

2. Call LLM API

LLM API is compatible with OpenAI / Anthropic / Gemini protocols. The following is a curl example:

Note: LLM API only supports Enterprise-Shared API Keys. Consumer-Member Keys and Enterprise-Dedicated Keys cannot call LLM API.

Recommended Starting Path

If this is your first time using RunningHub API, we recommend the following path:

Visit RunningHub, then register and log in.

Choose Account Entity

Use your personal account, or create / join a team account based on your usage scenario.

Create Enterprise-Shared API Key

If you need to call Model API or LLM API, create an Enterprise-Shared API Key.

Choose Target API

If you only need to call AI App API or Workflow API, choose Consumer-Member, Enterprise-Shared, or Enterprise-Dedicated Key based on your entitlement.

Complete Your First Call

Select a target API in the docs, copy the sample code, and complete the first call. Model API, AI App API, and Workflow API task records and consumption details can be viewed in Tasks & Billing; LLM API call records can be viewed in LLM Logs.

Instructions for Use

Getting Started · RunningHub API Docs#

Platform Overview#

Quick Start#

1. Register an Account#

2. Personal Account and Team Account#

3. Create or Join a Team Account#

4. Get an API Key#

Choose an API Key Type#

First API Call#

1. Call Model API / AI App API / Workflow API#

2. Call LLM API#

Recommended Starting Path#

Getting Started · RunningHub API Docs

Platform Overview

Quick Start

1. Register an Account

2. Personal Account and Team Account

3. Create or Join a Team Account

4. Get an API Key

Choose an API Key Type

First API Call

1. Call Model API / AI App API / Workflow API

2. Call LLM API

Recommended Starting Path