mosoo documentation

Use a Project API key (msp_) to choose a harness, model and instructions, then send input and files to a durable Session. An Agent is an optional reusable preset. Configure your own model-provider credentials in the Project.

The execution model

• A Project owns credentials, Sessions, optional Agent presets and usage.
• A harness runs the selected model with tools inside a Session workspace.
• A Session keeps the admitted configuration, conversation and working files. Follow-up uses the same public Thread ID.
• A Run is one turn, with its own outcome, events and recorded usage.

Each Session owns its execution state; there is no Assistant/Task type choice. Formal Sessions do not expire because they are idle. Cloud debug Previews have a separate 30-day inactivity policy.

Configure and operate

• Add model-provider credentials.
• Reuse optional Agent configuration, Skills and MCP, and Environments.
• Preview a preset and inspect Runs, files and usage.
• Read the Project and Session concepts.

API versions and sources

New integrations use the v2 API reference. Existing published-Agent integrations retain the v1 quickstart, v1 reference, and their Thread/Run IDs. Publishing is required only for flows that select a published configuration.

Check that the target deployment supports the documented v2 routes; this release guide does not establish current Cloud production availability. Keep the Project API key (msp_) on your backend, which authenticates your application users.

The source repository, llms.txt and llms-full.txt provide the implementation and documentation indexes.

The deployed v1 contract is available as OpenAPI.