It is code you own
Your agent is real TypeScript in a private repo you own, shown back as an editable graph. The manager is code, not an LLM.
one command to start
Launch agent.studio from your terminal.
Run agent.studio locally and open its browser workspace to shape and inspect agents beside your code.
agent.studio
npx @sapiom/agent-studio@latest
Starts locally and opens the agent.studio workspace in your browser.
why developers pick sapiom
You build the agent. Sapiom runs everything it needs.
One integration, every capability
Search, scraping, browser automation, compute, data, storage, messaging, images and audio through one Sapiom key, without separate vendor keys.
Inspect every attempt
Input, output, directive, error, retry state, timing, and cost stay attached to each recorded step attempt.
One server to build with, one to call.
Both speak MCP and answer to the same account. What differs is where each one runs.
The authoring server
Scaffolds, validates the graph offline, runs it on stubs, and deploys when it is green.
$ claude mcp add sapiom -- npx -y @sapiom/mcp
The capability server
Every capability as a direct tool over HTTP, and the only way in for a hosted client.
$ claude mcp add sapiom --transport http https://api.sapiom.ai/v1/mcp
agent.studio · authoring contract
Two functions, and every capability hangs off ctx.
An agent is defineAgent({ name, entry, steps }). Each step calls capabilities on ctx.sapiom and returns the step that runs next.
agent runtime · durable execution
The gate is in the graph, not in a comment.
The gate step approve? parks until digest.approved arrives, then resumes on the same state, in the same trace. Both arms end in a recorded state.
sapiom runtime
Planned sequenceresearch-brief · 4 steps · 1 waitstepsub-agentwaits
01collect-sourcessearch
02read-sourcesextract
typeCapability callinputweb.scrapedurationAt run timeest. cost$0.010 / extraction
03approve?wait
04publish-digestsend
capabilities · one entry point
Every capability, available through one account.
Discover and call Sapiom capabilities from remote MCP or a typed agent step, with usage attributed to the agent and trace.
Web and search
search the webremote MCP
Search the web and return answers with sources or raw results.
sapiom_searchReference
web scrapingremote MCP
Scrape, crawl, map, or extract structured content from the web.
sapiom_scrapeReference
deep researchremote MCP
Research across sources and return a structured, cited result.
sapiom_deep_searchReference
Browser and compute
extract contenttyped step
Extract structured fields from a page.
crawl a siteremote MCP
Follow a site and return its relevant pages.
run coderemote MCP
Execute code through the Sapiom compute surface.
sapiom_run
create a sandboxremote MCP
Start an isolated environment for agent work.
sapiom_sandbox_create
No capabilities match.
Your first agent, running in minutes
Start in your coding agent, terminal, or agent.studio. Sapiom handles the setup.
01
Start from a template
Clone an agent and run it locally.
02
Bring your own agent
Check, link, and deploy the TypeScript you have.
03
Start from intent
Describe the job and scaffold a typed agent.
/plugin marketplace add sapiom/sapiom-js /plugin install sapiom Registered the sapiom-dev MCP server. Added the sapiom-agent-authoring skill. Run sapiom_authenticate once to sign in.
{
"mcpServers": {
"sapiom": {
"command": "npx",
"args": ["-y", "@sapiom/mcp"]
}
}
}
codex mcp add sapiom -- npx -y @sapiom/mcp Added MCP server "sapiom". Restart Codex to load its tools.
claude mcp add sapiom \ --transport http \ https://api.sapiom.ai/v1/mcp The hosted capability server. Use it when the client cannot run npx, including ChatGPT.
docs and community
Everything you need to go deeper.
Read the docs
Quickstart, capabilities, Runtime, schedules, and signals, kept current with what ships.
Open the docsSDK reference
Every argument of defineAgent and defineStep, every directive, and the full ctx.sapiom surface.
Read the referenceGitHub
The packages, the MCP server, and the template gallery. Read the source, file an issue, send a patch.
Star on GitHubQuestions, answered.
Claude Code takes the plugin pair, /plugin marketplace add sapiom/sapiom-js then /plugin install sapiom, or the direct claude mcp add sapiom -- npx -y @sapiom/mcp. Codex takes codex mcp add sapiom -- npx -y @sapiom/mcp. Cursor and Claude Desktop take the JSON block with "command": "npx" and "args": ["-y", "@sapiom/mcp"]. Hosted clients take claude mcp add sapiom --transport http https://api.sapiom.ai/v1/mcp.
/plugin marketplace add sapiom/sapiom-jsclaude mcp add sapiom -- npx -y @sapiom/mcpNo. Scaffolding, offline graph validation, and local runs with stubbed Sapiom capability calls work signed out and cost nothing. Authenticate once in the browser when you want to deploy or run against real capabilities.
sapiom_dev_agents_run_localAuthor with the local one. @sapiom/mcp registers as sapiom-dev, speaks stdio, and drives the whole build loop from a checkout. Reach for the hosted server at https://api.sapiom.ai/v1/mcp for a single capability call with no agent around it, or when the client cannot run npx.
claude mcp add sapiom --transport http https://api.sapiom.ai/v1/mcpOne defineAgent({ name, entry, steps }) and a defineStep({ name, next, run }) per step, both from @sapiom/agent. A step calls capabilities on ctx.sapiom, keeps anything the next step needs on ctx.shared, and returns a directive that names where the run goes next.
npm install @sapiom/agentA gate step can pause until a named signal arrives. The runtime keeps the execution state, then resumes on the branch selected by that signal.
npx @sapiom/cli agents signal execution-id --name approved --correlation-id review-idYes. Your agent lives in a private git repository Sapiom provisions and you own. It is ordinary TypeScript built on @sapiom/agent, so you can read it, review it in a pull request, and leave with it.
npx @sapiom/cli agents init my-agentShip your first agent today.
Build and validate locally for free. Production capability calls are metered by their published units.