Sois documentation

Welcome to the Sois docs. This is the reference for connecting an agent to a Sois workspace, building and publishing apps, and running the platform day to day. If you want the product overview and pricing, that lives on sois.ai; everything here is the practical detail you need once you are actually building or operating.

Start here

Pick the path that matches what you are doing right now.

  • Running a business on Sois. Open Getting started to set up your workspace, then connect the agent you already use through the MCP server. Prefer to send a single instruction without wiring anything up? The Chat Agent Gateway takes a plain-English request and replies by webhook.
  • Building an app. Read the build guide. You connect your own agent to the Sois build tools, describe what you want, and ship it from your machine. When you are ready to sell it, monetise walks through review, metering, and payouts.
  • Integrating an outside service. Accounting, e-commerce, and messaging integrations are a first-class app category. See Integrations and Extensions.
  • Operating a network. If you run your own branded network on top of Sois, the security and data protection pages cover the trust model, key handling, and tenant isolation.

How Sois works, in brief

You do not have to read this section to get going, but it explains the model the rest of the docs assume.

A Sois workspace is a full MCP server. Every action a person can take in the interface is exposed as a tool an agent can call, subject to the same permissions. So instead of clicking through screens, you tell your agent what you need and it carries out the work inside Sois on your behalf: reading context, filling forms, applying policy, routing approvals, and reporting back in plain language. The screens are still there for when a person wants them, but they are no longer where the work has to happen.

Three ideas run through the platform:

  • The agent is the primary user. Tools, permissions, and context are designed for an agent to operate the whole system, not for an API bolted onto a product built for clicks. See the MCP server reference for the full tool surface.
  • Apps extend everything. The core modules cover what most businesses run on; anything else is an app. Apps are agent-native by default, so the moment one is installed your agent can use it. Browse what that looks like in Apps.
  • The marketplace is open. Developers build apps with their own agent and publish them; businesses install what they need and pay per use against a credit balance. Start at Build.

Two ways an agent connects

There are two entry points, and the right one depends on whether you bring your own agent.

  1. MCP server. Your own agent (any MCP-capable client) connects directly to your workspace and does the reasoning. This is the primary path. Full detail in MCP server, with the routing and fan-out options in MCP gateway.
  2. Chat Agent Gateway. No agent of your own? Send one plain-English message and the Sois agent does the work, then replies by webhook. See Chat Agent Gateway and the task interface reference.

Either way you describe the outcome, and Sois handles the steps in between. There are no schemas to learn, no field mapping, and no connectors to maintain.

Reference map

Ready to connect an agent? Getting started is the shortest path from a new workspace to your first completed task.