Skip to content
WAMP Cloud

What Cloud is

WAMP Cloud runs agents in managed workspaces. Your backend submits a task over HTTPS; Cloud provisions compute, starts the agent and retains its outcome. The same durable resources support Cloud Workspace, Telegram Cloud and native Cloud in Desktop. This site documents the public /v1 integration API.

The resources you use

Section titled “The resources you use”
Resource Your action
Session Create the durable conversation and choose its workspace source
Turn / Run Submit immutable input; observe its execution under the same ID
Event / Interaction Follow ordered progress and answer requests for input
Artifact Download retained, user-visible output
Publication / Merge Deliver an exact reviewed Git revision and optionally merge its PR head

Create a session and submit turns with caller-owned UUIDs. Save each command before sending: replaying its exact ID and immutable input returns existing work. A Turn’s 202 response means it was committed, before compute necessarily exists.

A session survives its sandbox. A lost sandbox can end a Run; retained conversation and workspace checkpoints determine whether another Turn can continue. Read Session continuation instead of inferring recoverability from visible history.

Who calls the API

Section titled “Who calls the API”

Call from a backend holding an App installation credential, scoped to one organization. Use an installation API key for one organization’s integration or short-lived installation tokens for a product installed by many organizations. Do not put either in browser or mobile code. Authentication explains the setup and the separate first-party human credentials.

The public API uses JSON requests and cursor-paged Events. There is no public SSE or WebSocket endpoint. Clients page the event log from their last committed cursor. The first-party browser workspace has a separate cookie BFF and private live connection, outside the integration contract.

Cloud supplies the agent runtime and compute policy. Your organization still needs configured capacity and model access, or an enrolled vendor subscription for subscription-funded agents. Discover the available choices with GET /v1/capabilities.

Start with one task

Section titled “Start with one task”

Integrate Cloud provides complete Shell and TypeScript examples: discover, submit, observe and read output. Then choose the guide for your next requirement:

Extensions, apps and the platform SDK are documented separately at docs.vampikez.fun. Cloud is a hosted execution surface of that platform; repository work is one supported task, not a required workspace type.