Compare approaches

A model API returns tokens. AgentSky runs the agent.

Choose the layer your team actually needs—from model access to a complete agent and its cloud computer.

Model accessModel APIAgent logicAgent SDKYour infrastructureDIY runtimeComplete cloud agentAgentSky
What you get
Tokens and model responses
An agent loop and primitives
Exactly what your team builds
A running agent and computer
Agent harness
You build it
One SDK or framework
You install and maintain it
Choose a supported harness
Cloud computer
Not included
You provide it
You operate it
Included and isolated
State and recovery
Application-defined
Application-defined
You design and operate it
Managed with the session
Tools and apps
You integrate them
You integrate them
You own every connection
Enable through the same API
Ongoing harness upgrades
Not applicable
You absorb SDK changes
You absorb every change
AgentSky absorbs them

This compares infrastructure layers, not time-sensitive vendor plans or feature counts.

The decision

Buy the layer you do not want to maintain.

01

Choose a model API

when your product needs model output and your team already owns the agent loop, computer, state, and integrations.

02

Choose an agent SDK

when you want to build the agent behavior yourself and are ready to supply the runtime and operations around it.

03

Choose a DIY runtime

when infrastructure control is the product advantage and your team wants to maintain every harness, sandbox, and recovery path.

04

Choose AgentSky

when your product needs the working agent and its computer through one API, while keeping the freedom to choose the supported harness and model.

Complete agent infrastructure

The agent and its computer. One API.

Open the Playground