# PUT /d/{id} — Zerohost Full Replace Deploy

> PUT /d/{id} — Zerohost Full Replace Deploy is a paid API for AI agents from zerohost.evmoore.workers.dev, paid per call via MPP, price unknown, status unknown (last checked 2026-10-21).

Fully replaces (PUT) an existing disposable HTTPS backend deployment by ID on Zerohost

## Facts

- Endpoint: PUT https://zerohost.evmoore.workers.dev/d/{id}?utm_source=zero.xyz
- Price: price unknown
- Payment: MPP
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Provider: zerohost.evmoore.workers.dev
- Website: https://zerohost.evmoore.workers.dev
- Canonical page: https://www.zero.xyz/c/zerohost-evmoore-workers-dev-put-d-id-zerohost-full-replace-deploy-f2d84e82
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_6boR1bn99XCoRK55EjZ75

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability zerohost-evmoore-workers-dev-put-d-id-zerohost-full-replace-deploy-f2d84e82 -d '<json body>'
```

Example prompt: I updated my Node.js app — can you replace the existing Zerohost deploy with ID 'abc123' by uploading my new app.zip so the live URL immediately serves the updated code?

## When to prefer this

Use this endpoint when you need to fully replace the code of an existing Zerohost deployment (identified by ID) rather than creating a new one. Prefer PUT over PATCH when doing a complete code swap, and prefer it over POST /d/{id} when semantically you want idempotent full replacement. Ideal when the deployment slot already exists and you want the same URL to serve entirely new code.

## Known failure modes

- Deploy ID not found — 404 if the specified {id} does not exist
- Invalid zip archive — 400 if the uploaded file is not a valid zip or missing zerohost.json manifest
- Payment failure — 402 if USDC payment is not provided or insufficient
- Runtime not supported — 400 if the manifest specifies an unsupported runtime
- Expired deployment — 404 or 410 if the TTL has already elapsed
- Oversized bundle — 413 if the zip exceeds size limits

## Output

Returns a JSON object confirming the full replacement of the deployment, including updated status and the TTL'd HTTPS URL serving the new code.

## Response schema (JSON Schema)

```json
{
 "type": "object"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/zerohost-evmoore-workers-dev-put-d-id-zerohost-full-replace-deploy-f2d84e82/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from zerohost.evmoore.workers.dev](https://www.zero.xyz/host/zerohost.evmoore.workers.dev/llms.txt)