# Cloud Simulation Node Failure Injection

> Cloud Simulation Node Failure Injection is a paid API for AI agents from www.cloudworldmodel.ai, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Kills a random healthy compute node in a running cloud simulation to test fault tolerance and resilience.

## Facts

- Endpoint: POST https://www.cloudworldmodel.ai/api/simulations/64acab96-325e-4a59-b356-6b4a25deb044/inject-failure
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/cloud-simulation-node-failure-injection-ebac9306
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_N5dGNEPFOmFeom-n3Ws6n

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 cloud-simulation-node-failure-injection-ebac9306 -d '<json body>'
```

Example prompt: Inject a random compute node failure into my cloud simulation 21a35fd3-c0bf-4cae-a478-ddc9232d7dae — kill one of the healthy nodes so I can see how the system responds.

## When to prefer this

Use this endpoint when you need to test fault tolerance or resilience within the cloudworldmodel.ai simulation environment specifically, particularly when you want to observe how a simulated cloud deployment reacts to sudden compute node loss. Prefer this over traffic spike injection when the failure mode you want to test is node loss rather than load increase.

## Known failure modes

- Simulation ID not found or already completed — returns 404
- No healthy nodes available to terminate — returns error indicating no eligible targets
- Payment not authorized or insufficient balance — returns 402
- Invalid input schema — returns 400 with validation errors
- Simulation in a non-running state — returns conflict error

## How this service works

Fail a specific compute node by `resourceId` or `resourceName`; omit both only when random selection is explicitly intended (non-deterministic).

## Output

Returns a failure event object describing which node was killed and an updated simulation state object reflecting the new topology after the node termination.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "resourceId": {
   "type": "string",
   "description": "**Recommended** — ID of the resource to fail. Takes precedence over resourceName. Use this for reproducible, deterministic fault injection."
  },
  "resourceName": {
   "type": "string",
   "description": "**Recommended** — Human-readable name of the resource to fail (exact match preferred; unambiguous prefix accepted). Ambiguous names return 400 with a candidate list. Omit both fields for a random healthy node (non-deterministic)."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/cloud-simulation-node-failure-injection-ebac9306/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.cloudworldmodel.ai](https://www.zero.xyz/host/www.cloudworldmodel.ai/llms.txt)