# x402-hosting Delete Project

> x402-hosting Delete Project is a paid API for AI agents from api.x402-hosting.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-12).

Deletes an existing Next.js hosting project by project ID, paid per-call with USDC via x402.

## Facts

- Endpoint: DELETE https://api.x402-hosting.com/v1/projects/%7Bid%7D
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-hosting-delete-project-27782f1e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_lFVJIaPyCMlh6Ql74Y2Wr

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 x402-hosting-delete-project-27782f1e -d '<json body>'
```

Example prompt: Delete the x402-hosting project with ID 00000000-0000-4000-8000-000000000001 — I no longer need that deployment and want it fully removed.

## When to prefer this

Use this endpoint when you need to programmatically delete a specific hosted Next.js project on x402-hosting by its project ID, particularly in agent-driven workflows where deployments are spun up and torn down automatically and payment is handled via USDC over x402. Prefer this over manual teardown when automating project lifecycle management.

## Known failure modes

- Project ID not found — 404 with unknown project error
- Insufficient USDC balance for the $0.01 per-call fee — payment failure
- Malformed or missing project ID in path — 400 validation error
- Project already deleted or in terminal state — conflict or idempotency error
- x402 payment protocol handshake failure — HTTP 402 returned before deletion proceeds

## How this service works

Prepaid full-stack Next.js hosting operated by agents. One CLI command builds and deploys your app to a production URL; pay per project-day in USDC over the x402 protocol. No account, no dashboard.

## Output

Returns a JSON object confirming the deletion operation, including the project's current state (e.g. 'CREATED'), the projectId, an operationId, and an operationUrl where the agent can poll for the completed status of the delete operation.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "state": "CREATED",
  "projectId": "00000000-0000-4000-8000-000000000001",
  "operationId": "00000000-0000-4000-8000-000000000001",
  "operationUrl": "/v1/operations/00000000-0000-4000-8000-000000000001"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-hosting-delete-project-27782f1e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.x402-hosting.com](https://www.zero.xyz/host/api.x402-hosting.com/llms.txt)
