TOOLS

Reusable Tools
for you, your team, and your applications.

Define a function, its inputs, and its execution configuration. Use your own code or prepare it with your AI. Call the Tool remotely through MCP, an SDK, or an API, and publish versions to reuse or share with authorized people.

I want to create my ToolsSee how to integrate with your product ↗

One function,
with defined inputs.

A Tool brings together a function, its inputs, and its execution configuration. Users provide arguments; runvibe_ checks authorization before starting the Execution.

Use your Tools with the AI you already use.

Connect an MCP-compatible client to create and call your Tools on runvibe_. They remain available in other sessions and connected clients.

Claude

Gemini

ChatGPT

DeepSeek

Grok

Mistral

Your functions, available
for the next task.

Runs outside your machine.

Calls run in the cloud, so they don't depend on your computer staying on.

Prepared environment.

The manifest defines the code, dependencies, and resources, which are reused for later runs.

Available across conversations.

The Tool stays saved for future use with new arguments.

Integrate a function into your product.

Call a Tool through an SDK or API, send arguments, and retrieve the result in your application.

Your application sends order data to a Tool that generates a document. Then, it consults the result to make it available to the user.

Defined inputs.

Define function inputs, defaults, and validation.

Configurable execution.

Define the code, dependencies, resources, and network access for execution.

Share functions with authorized people.

Define who can use or maintain the Tool. Use does not grant direct access to the Image or implementation Secrets. The consumer enters the inputs and consults the results that they are authorized to access.

Versions and composition

A Tool can call other Tools to complete a task. Each dependency uses a defined version and must be authorized. You can evolve a function without silently replacing the versions used by others.

“Monthly active users” calls an authorized version of “Query usage metrics.” The first organizes the report; the second centralizes the data access allowed by engineering.

Pay for time
in use.

Each Tool call starts an Execution. The dollar cost depends on the configuration and processing time. Execution charges end with the task; image storage has a separate rate.

Your plan balance renews each month and does not roll over. Add a top-up when you need one.

Estimate my usage ↗

Call the Tool

Send arguments to start an Execution.

Run in the cloud

Usage depends on the selected resources and runtime.

Execution complete

Execution charges stop. The Tool stays available for new calls.

Frequently asked questions.

Do I need to create a Workspace first?

No. You can create a Tool with code and an execution configuration without creating a Workspace first. Use a Workspace when you want to prepare and test your project in a development environment.

Can I use my own code?

Yes. Prepare the code and execution configuration for the function.

Can I share a Tool with other people?

You can share Tools with authorized collaborators. Account membership conditions depend on your plan.

Can I edit a Tool after creating it?

Edit the definition and publish a new version. Integrations pinned to a version stay on that version until explicitly updated.

Does sharing give access to credentials?

Sharing use does not grant direct access to the Image or Secrets. Execution configuration determines access and available results.

How does access revocation work?

Revoking access blocks new starts that depend on that access. Executions already running continue; an authorized person can cancel them separately. New calls to dependencies also require authorization.

Do I need to keep my computer on during execution?

No. Once started, the Execution runs on runvibe_ infrastructure. Reconnect to check progress and results.

How is usage calculated for composed Tools?

Usage depends on the executions and resources used.

Keep exploring runvibe_.

Request access
to create your Tools.

Use them with your AI or integrate them into your product through the SDK and API.

I want to create my Tools