Cloud API documentation

WAMP Cloud

Start a session, send it work, and follow the run. The sandbox is ours to manage; the agent keeps working whether or not anyone is watching.

Integrate WAMP Cloud API reference

TURN=$(uuidgen | tr 'A-Z' 'a-z')

curl -sS -X PUT "$WAMP_API/v1/sessions/$SESSION/turns/$TURN" \
  -H "Authorization: Bearer $WAMP_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"message": "Fix the failing test in src/parser.ts, then open a PR"}'

# 202 Accepted — the turn id you minted is also the run id
{ "created": true, "turn": { "dispatch": "pending" }, "run": { "state": "queued" } }

You mint the id and PUT the resource at it, so re-sending a request that timed out cannot start a second run.

What you can build

Agents that outlive the request

A session and its event log survive a dropped connection or closed tab. Sandbox loss can end the current run; retained checkpoints determine whether a later turn can continue.

Driven from anything that speaks HTTP

No published SDK required and no client runtime to embed. A CRM webhook, a Telegram bot, a cron job, and a web app’s backend call the same HTTPS resources under /v1.

Real repositories, real pull requests

Grant access to specific private repositories, let an agent work in a checkout, and land the result as a reviewable pull request merged at an exact commit. Coding is a common vertical, not the only one.

Choice of agent runtime

The sandbox can run the native WAMP agent or a vendor or host ACP runtime. Selecting one is a field on the session, not a different integration. Read the live list from GET /v1/capabilities.

The same /v1 resources also back first-party products: Cloud Workspace (the web app; people sign in with cookies, not installation keys), Telegram Cloud (a bot that is itself a /v1 client), and native Cloud in Desktop (a delegation from the signed-in WAMP account). Humans never hold an installation credential. This site is the HTTP contract for backends.

Get oriented

Integrate WAMP CloudAuthenticate, discover compute, submit a task, and follow or recover its Run with a complete Shell or TypeScript example.

Sessions, turns, runsThe three nouns the whole API is built from, and which one owns what.

Follow a run livePage the ordered event log with a cursor as the agent works, and resume exactly where you left off after a disconnect.

AuthenticationWhich credential to use for which caller, how to get one, and how to rotate it.

Building the desktop platform instead?

WAMP Cloud is the hosted execution product. The desktop platform — extensions, apps, branded products, and the plugin API — is documented separately at docs.vampikez.fun.

Reading this with an agent

Every page here is also served as markdown, and the whole site is served as one file. Point an agent at the text instead of having it scrape the rendered pages.

This page, as markdownAdd .md to any page's path — /concepts/sessions-turns-runs.md. The Copy page button at the top of every page copies the same text.

The whole site, as one filellms.txt indexes every page with its summary; llms-full.txt is the entire corpus in one document. The OpenAPI contract is served live at /v1/openapi.json.