AI agent hosting API: deploy and run agents from a CLI or SDK

What you can do from the command line

The CLI does from a terminal what the console does in a browser. Every command takes --json, prints only the payload on stdout, and exits with a code a script can branch on, so it slots into shell scripts and CI without screen scraping.

• Environments: list, create, resize, rename and remove, with region and size chosen for you or pinned.
• Agents: deploy from a template with a model and runtime, message them, run a command on them, read logs and status.
• Operations: follow long jobs to completion, run a health check with repair, and read usage and spending.
• An escape hatch: qoren api reaches any control-plane endpoint with the same credential and rules.

qoren login
qoren env ls
qoren agent create --env "$ENV_ID" --template inbox-manager --name "Inbox" --json
qoren agent message "$AGENT_ID" "Summarize what arrived overnight"
qoren agent logs "$AGENT_ID" --limit 50

• The Qoren command line
• Qoren CLI command reference

Drive it from TypeScript

The SDK is the same surface as a typed client. Everything expensive is asynchronous: a create returns a job id, and the SDK can wait on the job, report each step, ride out a transient outage and throw the job's own error if it fails.

import { Qoren } from "@qoren/sdk";

const qoren = new Qoren({ token: process.env.QOREN_TOKEN });
const [env] = await qoren.environments.list();
const { jobId } = await qoren.agents.create({
  machineId: env.id,
  slug: "inbox-manager",
  name: "Inbox",
  runtime: "hermes",
  model: "anthropic/claude-sonnet-4",
  presetName: "inbox-manager",
});
await qoren.jobs.await(jobId, (job) => console.log(job.status));

• The Qoren TypeScript SDK

Run it from CI

Create a token in the console under Settings, CLI tokens, and set it as QOREN_TOKEN in your pipeline. It overrides any stored login, so a build never picks up a developer's profile. Exit codes separate a revoked token (3) from a plan without API access (4) from a failed request (1).

• Create and revoke CLI access tokens

Which plans include API access

The CLI, the SDK and access tokens are API access, which the Ultimate, Business and Enterprise plans include, and a free trial of one of those counts. On Starter and Pro every token request is refused, and the CLI exits with code 4 and names the plans that include it. The web console works on every plan, so nothing else about running agents changes.

• Qoren pricing

Not a side door around the platform

The CLI, the SDK and the console all reach your environments through the same gate, which checks who you are and what your plan allows before anything runs. A token can do what your account can do in a browser, and nothing more. It cannot change your password or billing details, and you can revoke it from the console at any time.

When a plain VPS or your own stack is the better fit

If you need root on the host, a custom kernel, or a runtime Qoren does not run, rent a server and operate it yourself. The API is for teams who want agents in their scripts without also running the machines, the secret storage, the updates and the restarts underneath them.

• Self-Hosted vs Managed AI Agents