Skip to main content
ModuleX is an AI workflow orchestration platform. You describe a process in plain language or draw it on a visual canvas, connect the tools and data you already use, and run it with any major AI model — from chat, the API, or an SDK. There are two ways to work with ModuleX, and you can mix them freely.

Use the app (no code)

Build workflows on a collaborative visual canvas, generate them from a prompt with the AI Composer, and chat with the agentic Assistant — no engineering required.

Use the API and SDKs (code)

Run the same workflows from your own software with the REST API or the official JavaScript and Python SDKs.

Start here

Pick the path that matches how you want to begin.

Quickstart

Create an account, get an API key, and make your first authenticated call.

Run your first workflow

Build a workflow in the canvas or with the Composer, then run it from the app.

Make your first API call

Trigger a workflow from code in cURL, Python, or JavaScript.

Explore the docs

Concepts

The mental model behind ModuleX: workflows and runs, the workflow engine and its nodes, the Composer and Assistant, knowledge and RAG, organizations, and credits.

API & SDKs

The request lifecycle, authentication, errors, and every operation shown once in cURL, Python, and JavaScript — plus a live endpoint playground.

Integrations

Connect ModuleX to 175 services and call their tools from workflows and the Assistant.

Build & Assistant

A tour of the app: chat, the workflow builder, knowledge bases, realtime collaboration, and the agentic Assistant.

What you can do with ModuleX

Describe a workflow in words

The AI Composer turns a plain-English description into an editable workflow graph — steps, tools, and logic laid out on the canvas for you to refine.

Build visually with your team

Multiple people can edit the same workflow builder canvas at once, with live cursors, presence, and node locks.

Answer from your own knowledge

Connect documents to a knowledge base and let workflows and chat retrieve the right context automatically with RAG.

Run an agent that uses your tools

The Assistant is an agentic chat that searches your connected tools, drafts outputs, and pauses for approval before sensitive actions — no workflow required.

Run a workflow from code

Every workflow you build in the app can be triggered programmatically. Each request authenticates with an API key in the Authorization header and selects your organization with the X-Organization-ID header.
Running a saved workflow requires an active deployment. Managed runs pass through ModuleX’s billing gate and can return a 402, 403, or 429 denial when your plan’s credits or limits are reached. See errors & status codes and usage gating & limits.
For the full walkthrough — authenticate, run, and stream the result in three languages — see Run a workflow (REST + SDK).

How billing works, in one line

Managed usage is metered in credits: 100 credits equal $1.00. Each plan includes a monthly credit allowance, and paid organizations can add a prepaid wallet for usage beyond it. If you bring your own model and tool keys (BYOK), that usage is billed directly by the provider and is not credited. See billing & credits overview and plans & pricing.

Get help

Help center

Short answers for getting going, using ModuleX, and troubleshooting.

Glossary

Canonical ModuleX terminology in one place.

Known limitations

Documented gaps and paths you should not rely on yet.