Build a Genspark-style agent

What you’re building: a super-agent that plans, researches, and produces finished work (documents, slides, sites) for the user.

Primitives you’ll use: Organization, Sandboxes, Computers, Agents, Deployments, Custom domains

What you’re building

A “super-agent” is an orchestrator: it takes one request, plans the steps, and delegates each step to the right tool, then assembles the result into something a person can use (a report, a deck, a page).

MIOSA gives the orchestrator two kinds of workers: Sandboxes for code, files, and data work, and Computers for browser and desktop steps. The orchestrator can run several in parallel, stream progress to the UI, and collect every file an agent produced as an artifact.

The design rule from the docs: the agent works in a MIOSA machine; the reasoning and the UI stay yours.

What you need on MIOSA

Architecture

Step 1: Create an account and an API key

Install the CLI, sign in, and mint a key for your product. The secret is printed once; store it as an environment variable, never in code.

npm i -g @miosa/cli
miosa login
miosa whoami
miosa api-key create super-agent-key --preset agent     # prints the secret once
export MIOSA_API_KEY="msk_u_..."

Both SDKs read MIOSA_API_KEY from the environment, so a server or a worker needs nothing else. See API keys for scopes and how to create keys in the console.

Step 2: Create the resources

Step 3: Wire the agent loop

Collect the finished files as artifacts and publish the site with the deploy step below.

Step 4: Preview

A Preview is a throwaway public URL for a port inside the machine. Start the app as a background process so it survives the CLI disconnecting, then expose its port.

Open the exact Preview URL MIOSA returns.

Step 5: Deploy

Publish the machine to an immutable Deployment. Give it the source machine, the path the app lives at inside it, and the command that serves it.

Publishing the same deployment name again creates a new immutable version and keeps the same URL. Roll back with miosa deploy rollback super-agent --to <version-id>, and inspect a live app with miosa deploy logs super-agent -n 100. See Publishing and Rollback.

Step 6: Custom domain

Attach a domain your customer owns to the deployment. The platform URL keeps working while DNS propagates.

miosa deploy domain-add super-agent app.example.com
miosa deploy domains super-agent          # shows the DNS record and verification target
miosa deploy domain-verify super-agent <domain-id>

Copy the exact DNS record MIOSA shows into the customer’s DNS provider; for a subdomain it is normally a CNAME. Once verified and TLS is active, MIOSA routes the domain to the deployment’s active version. In code, read the URL from the publish response instead of building it: the SDK method is miosa.deployments.domains.add(deploymentId, { domain }) (TypeScript) or miosa.deployments.domains(deployment_id).add(domain=...) (Python). See Domains.

Costs and limits

Everything bills while it runs: machines (sandboxes and computers) by the second, managed databases while running, and deployments when they serve. Pausing a machine stops compute billing but keeps disk. Set an --idle-timeout or a --ttl so a forgotten machine cannot run forever, and cap spend with rate limits and per-workspace quotas.

• Pricing - plans, the published rate card, and the free Developer grant.
• Sizing and limits - machine sizes and what each costs to run.
• Timeouts and auto-stop - --ttl, --idle-timeout, and pause/resume.

Next steps