Skip to content
WAMP Cloud

What Cloud is

After this page you know whether WAMP Cloud is the right thing to build against, what the four nouns are, and which page to read next.

The product

Section titled “The product”

WAMP Cloud is a hosted HTTP API for running AI coding agents. You create a session, submit a turn to it, and the platform provisions a sandbox, runs the agent, and records everything it did as an ordered log of events plus a set of artifacts you can download. If the session is attached to a repository, the agent’s work can be landed as a pull request.

There is no agent to host, no sandbox to operate, and no model key to hold. Your backend makes ordinary JSON requests:

PUT  /v1/sessions/{sessionId}                  create the session (you choose the id)
PUT  /v1/sessions/{sessionId}/turns/{turnId}   give it work    (you choose the id)
GET  /v1/sessions/{sessionId}/events?after=N   follow the run
GET  /v1/sessions/{sessionId}/artifacts        read the results

The problem it solves

Section titled “The problem it solves”

An agent doing real work takes minutes, not milliseconds. It outlives the HTTP request that started it, the browser tab that triggered it, the process that called it, and sometimes the sandbox it started in. Cloud is built around that fact rather than against it:

  • A run is server-owned. PUT a turn and you get 202 Accepted as soon as the turn and its queued run are committed to the database — before any compute is provisioned. Nothing is lost if your caller disconnects one millisecond later.
  • A session outlives its sandbox. The workspace is a lease with a bounded lifetime. When it expires the session is still there, and the session’s continuation field tells you whether the next turn can resume the work and at what fidelity.
  • Retries are safe by construction. You mint the UUID for every session, turn, publication, and merge, and create it with PUT. Replaying the same id with the same body returns the same resource instead of starting a second run.
  • The event log is the repair authority. Events are totally ordered per session by a gap-free integer sequence, deduplicated before storage, and retained for the life of the session. A process that crashed mid-run resumes by replaying from the cursor it last persisted.

Who calls it

Section titled “Who calls it”

Backends. A CRM that starts an agent when a ticket is escalated, a chat bot that turns each message into a turn, a scheduler that runs a nightly maintenance task, a web app whose button handler queues work for a worker to follow.

The credential model matches that: /v1 accepts exactly one scheme, a short-lived bearer token bound to one app installation — which means one organization — and derived from a signing key that never leaves your process. It is not a per-user credential and it is not safe in a browser or a mobile app. Cookies are refused. See Authentication.

What it is not

Section titled “What it is not”
  • Not a streaming API. There is no Server-Sent Events endpoint and no public WebSocket. You follow a run by paging the event log with a cursor. Webhooks can wake your backend up, but the events themselves always come from the same endpoint. See Follow a run live.
  • Not a model API. You do not send prompts to a model and get completions. You give an agent a task and it decides what to read, run, and change inside a workspace. Choosing the model is one field on the session.
  • Not a client SDK. Everything here is server-to-server. There is no browser or mobile library, by design.
  • Not a repository host or a CI system. Cloud works in a checkout of a repository you grant it and opens a pull request against it. Review, checks, and branch protection stay where they already are.
  • Not the desktop platform. WAMP also ships a desktop product with extensions, apps, and a plugin API. That is a separate surface documented at docs.vampikez.fun.

Where to go next

Section titled “Where to go next”
  • Quickstart — a token, a session, a turn, and a finished run, with real curl calls.
  • Authentication — generate a keypair, sign an assertion, exchange it, and understand what your installation is allowed to do.
  • Sessions, turns, runs — the three nouns in detail, including why a turn id is also a run id and why only one run per session may be active.
  • Drive Cloud from a backend — where secrets live, what your database has to store, and how to map your objects onto sessions.
  • Sessions operations — the generated endpoint reference, straight from the OpenAPI contract the server serves.