# GET /d/{id} — Fetch Deployed Zerohost Sandbox Response

> GET /d/{id} — Fetch Deployed Zerohost Sandbox Response 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-22).

Sends a GET request to a live, TTL'd disposable HTTPS backend deployed via Zerohost, returning whatever that sandbox responds with.

## Facts

- Endpoint: GET https://zerohost.evmoore.workers.dev/d/{id}?utm_source=zero.xyz
- Price: price unknown
- Payment: MPP
- Status: unknown
- Last checked: 2026-10-22
- 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-d-id-fetch-deployed-zerohost-sandbox-96cce9b6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_n8-kMsaGtyouoF96ISaWr

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-d-id-fetch-deployed-zerohost-sandbox-96cce9b6
```

Example prompt: Send a GET request to my Zerohost deploy with ID 'abc123' and show me what it responds with.

## When to prefer this

Use this endpoint when you need to invoke or test a previously deployed Zerohost ephemeral backend via GET. This is the right call when you have a deploy ID from a prior POST /v1/deploy and want to retrieve data or trigger logic from that sandbox. Prefer this over POST /d/{id} when the sandbox operation is read-only or idempotent.

## Known failure modes

- Deploy ID not found or expired (TTL elapsed) — likely 404 or similar error
- Deploy is not accepting GET requests (only other methods handled by sandbox code)
- Sandbox runtime error causing 500 from the deployed code
- Invalid or malformed deploy ID format
- Sandbox cold-start or resource limit exceeded on Cloudflare

## Output

Returns the HTTP response body from the live, TTL-scoped disposable backend identified by the given deploy ID. The response is whatever the uploaded code returns for a GET request — could be JSON, plain text, or any other content type the sandbox produces.

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/zerohost-evmoore-workers-dev-get-d-id-fetch-deployed-zerohost-sandbox-96cce9b6/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)