AgentSky for enterprise
Standardize how your company runs agents.
Give teams and products one managed way to use Claude Code, Codex, Hermes, OpenClaw and more. AgentSky runs the persistent cloud computers, model routes, tools, connectors, channels, state, recovery and usage records behind one Agent API.
Why enterprises choose AgentSky
One Agent API
Integrate one contract for agents and sessions instead of maintaining a separate runtime adapter for every agent your teams want to use.
The complete runtime
Each session includes an isolated cloud computer, persistent workspace, state, streamed events and recovery. AgentSky operates the execution layer around the model call.
Choice without a rewrite
Agent and model are explicit choices. Evaluate compatible combinations, add a new stack and keep the same product integration and operating boundary.
Browser and API
Internal teams can start in the hosted workspace. Product and platform teams can run the same agents through the API under their own interface and workflow.
One usage system
Model tokens, active computer time, paid tools and connector operations are recorded in one place. Parked agents do not accrue compute charges.
Apps and channels included
Connect authorized business applications and let people reach the selected agent from supported team channels without building each adapter yourself.
Three adoption paths
A managed agent workspace
Give people access to approved agents and models in the browser, with the projects, tools, connectors and channels each workflow needs.
- Start without an internal platform build
- Use eligible Claude or ChatGPT subscriptions
- Keep work in a persistent agent session
Agents behind your own experience
Call the Agent API from your product while your application keeps ownership of users, authorization, workflow policy and the final customer experience.
- One API across supported agents
- Normalized session and event contract
- Optional AgentSky-hosted workspace
An execution layer for every job
Your orchestrator chooses the agent, model, budget and task. AgentSky provisions an isolated runtime and keeps the session available for follow-up work.
- Parallel isolated sessions
- Per-workflow agent and model choice
- Persistent state and recovery
One clear platform boundary
Your systems own the business. AgentSky owns the agent runtime.
Adopting AgentSky does not require moving your workflow graph or product logic into another orchestration system. Call an agent when the work needs one; keep the business decision in the system that already owns it.
Your company
Owns users, roles, workflow policy, approvals, business outcomes and the decision to accept or reject the work.
AgentSky
Runs the selected agent, model interface, isolated computer, persistent session, event stream, recovery and usage accounting.
Connected applications
Remain separate permission boundaries. Each connector uses the account, scopes, organization policy and resources your team authorizes.
Model providers
Remain visible choices with their own data terms. Your team can restrict the combinations it evaluates and uses.
Running in real products
Tycoon
Tycoon reports 150,000 agents launched while its AI CEO routes work across Claude Code, Codex and Hermes through one AgentSky API integration.
HeyBoss AI
HeyBoss AI reports 250,000 agents launched and prewarms AgentSky runtimes so a user's first prompt reaches a ready worker.
WebJourney
WebJourney reports 50,000+ agents launched and changed its agent and model stack while keeping the product API and backend in place.
Cost control
Pay for execution, with the cost components visible.
AgentSky uses prepaid usage instead of per-seat packaging. Measure the cost of an accepted result across the complete task, including the model, active computer, tools, connectors and human review.
Nothing while parked
Compute is metered while an agent is active. A parked session can retain its state without continuing to accrue active-computer charges.
Bring eligible subscriptions
Connect a Claude or ChatGPT plan for supported agents and AgentSky records $0 for eligible model usage; compute and paid capabilities remain separate.
One bill across the stack
The same balance covers AgentSky model routing, runtime and paid capabilities, with current rates published before the workflow is expanded.
Security and procurement
Match the data path and contract to the workflow.
The public privacy policy and terms describe the standard service. An enterprise agreement can add a data processing addendum and Zero Data Retention for Content; provider-level Zero Data Retention is passed through where the selected provider offers it. Review security and data handling
Available to evaluate
- An explicit model provider, isolated agent session and separately authorized connector accounts.
- Published retention and data-handling terms, plus an enterprise DPA and Content Zero Data Retention option.
- Permission review and revocation for the accounts, repositories, applications and channels in the workflow.
Confirm for your contract
- Required SSO, SCIM, role design, audit exports or administrator workflows.
- Required deployment region, dedicated infrastructure or restrictions on model and compute providers.
- Certifications, custom support, incident terms, volume commitments or service-level agreements.
From evaluation to rollout
Prove one workflow, then standardize the path.
The first evaluation should answer a purchasing decision: whether AgentSky produces an acceptable result with the access, cost, controls and recovery your real workflow requires.
Choose a workflow that matters
Name the recurring task, its owner, the systems it touches, the actions that need approval and one observable definition of an accepted result.
Compare agent + model combinations
Run the same representative work across compatible choices. Record completion quality, elapsed time, failures, recovery, human review and total AgentSky usage.
Integrate the winning path
Use the browser for an internal workflow or the Agent API for a product and software factory. Keep authorization, routing and business policy in their existing owners.
Expand with evidence
Add teams, permissions and workflows only after the owner accepts the result and procurement confirms the terms required for the next scope.
Common questions
Enterprise AgentSky questions
What does an enterprise buy from AgentSky?
AgentSky is the managed execution platform behind the agent: one API and hosted workspace for supported agents, models, isolated cloud computers, persistent sessions, tools, connectors, channels, recovery and usage accounting. Your company keeps its application, workflow policy and business decisions.
Why use AgentSky instead of calling a model API directly?
A model API returns model output. An AgentSky session also runs the selected agent's work loop, tools and computer, keeps its files and state available, streams normalized events and supports follow-up work. Use a direct model call when the task needs only inference; use AgentSky when it needs a complete agent runtime.
Can one platform support several agents and models?
Yes. The same Agent API supports the currently offered AgentSky agents and their compatible models. Your team can compare combinations on representative tasks and choose per workflow without building another product integration.
Can we use AgentSky for both employees and customers?
Yes. Internal teams can use the hosted browser workspace and supported channels. Product teams can call the same agent platform through the API under their own user experience, authentication, routing and approval policy.
Does each agent run in an isolated environment?
Each AgentSky session runs in its own cloud computer and persistent workspace. The connected accounts, project access and task instructions still determine what that session is authorized to read or change.
Can our company use existing Claude or ChatGPT subscriptions?
Eligible Claude Code and Codex model usage can run through a connected Claude or ChatGPT subscription and is recorded at $0 model cost by AgentSky. Active computer time, paid tools and connector operations remain separately metered.
How does enterprise AgentSky pricing work?
The standard product uses prepaid usage instead of seats or minimums. Active computer time, model tokens and paid capabilities are itemized; parked sessions do not accrue active-computer charges. Discuss volume or contractual requirements separately.
Does AgentSky offer a DPA or Zero Data Retention?
The published terms provide a path to an enterprise agreement with a data processing addendum and Zero Data Retention for Content. Where the selected model provider offers its own Zero Data Retention option, AgentSky passes that option through. Confirm the exact agreement and provider route before submitting regulated data.
Does enterprise AgentSky include SSO, SCIM, certifications or an SLA?
Treat those as procurement requirements to confirm for the proposed contract. Bring the exact identity, audit, certification, region, support and service-level requirements to the enterprise conversation before relying on them.
What should we evaluate first?
Choose one recurring workflow with a named owner, representative inputs and an observable accepted result. Compare the relevant agent + model combinations, record failure recovery and human review, and calculate the complete cost of accepted work before expanding access.
Related resources
Agent API
Review the integration contract for agents and sessions.
Software factories
See how an orchestrator can route work while AgentSky operates execution.
Security and data
Trace model, connector, runtime and retention boundaries.
Pricing
Review every current usage component and rate.
Tycoon
See a multi-agent software factory built on one Agent API.
HeyBoss AI
See how a product prewarms AgentSky runtimes for customer work.
WebJourney
See a product change its agent stack without replacing its backend.
Bring us the workflow you want to standardize.
We will map the agent, model, runtime, access, cost and procurement path needed to put it into production.