# GET /v1/deploy/{id} - Fetch Deploy Status

> GET /v1/deploy/{id} - Fetch Deploy Status 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).

Retrieves the current status and metadata of a specific disposable HTTPS backend deployment by its ID

## Facts

- Endpoint: GET https://zerohost.evmoore.workers.dev/v1/deploy/{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-get-v1-deploy-id-fetch-deploy-status-3f7073dc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_yIdHOFS3OsyfHiOBjgoSN

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-get-v1-deploy-id-fetch-deploy-status-3f7073dc
```

Example prompt: Check the status of my zerohost deployment with ID abc123 — I want to know if it's still running, what its URL is, and how much time is left on it.

## When to prefer this

Use this endpoint when you need to check whether a specific disposable backend is still live, retrieve its public URL, or inspect its remaining TTL before deciding to extend or delete it. Prefer this over the logs endpoint when you want metadata rather than runtime logs.

## Known failure modes

- Deployment ID not found or already expired — 404 response
- Invalid deployment ID format — 400 bad request
- Deployment has been deleted — 404 or 410 gone
- Authentication/payment issues — 401 or 403 response
- Service temporarily unavailable — 503

## Output

Returns a JSON object containing the deployment's current status, its public HTTPS URL, remaining TTL, runtime (Node/Bun/Python), and other metadata about the disposable backend.

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/zerohost-evmoore-workers-dev-get-v1-deploy-id-fetch-deploy-status-3f7073dc/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)