Agents that outlive the request
A session is durable and a run is server-owned, so work survives a dropped connection, a closed tab, and a redeployed sandbox. Your caller reconnects and picks the transcript back up.
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.
What you can build
Section titled “What you can build”Driven from anything that speaks HTTP
No SDK required and no client runtime to embed. A CRM webhook, a Telegram bot, a cron job, and a web front end are all the same kind of caller.
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.
Choice of coding agent
The sandbox can run more than one coding harness. Selecting one is a field on the session, not a different integration.
Get oriented
Section titled “Get oriented”QuickstartAuthenticate, create a session, send a turn, and read the result — with real curl calls.
Sessions, turns, runsThe three nouns the whole API is built from, and which one owns what.
Follow a run liveStream events 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?
Section titled “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
Section titled “Reading this with an agent”Both documentation sites publish the llms.txt pair: /llms.txt indexes every page with its summary, and /llms-full.txt is the entire corpus as one markdown document. Point a coding agent at either instead of having it scrape the rendered pages.