# Cloud World Model – Recover Simulation Resource

> Cloud World Model – Recover Simulation Resource 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-15).

Clears a reversible failure state (instance_down or database_overload) from a single simulated cloud resource so the simulation engine restores it to healthy status over subsequent steps.

## Facts

- Endpoint: POST https://www.cloudworldmodel.ai/api/simulations/2338441e-1300-4abe-9a79-98e3645c5790/recover-resource
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/cloud-world-model-recover-simulation-resource-e3c56180
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_v1v88b2vHlV93f1uuHBkJ

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-world-model-recover-simulation-resource-e3c56180 -d '<json body>'
```

Example prompt: In my Cloud World Model simulation 2338441e-1300-4abe-9a79-98e3645c5790, the resource named 'web-server-01' is in an instance_down state — can you recover it so the simulation engine brings it back to healthy?

## When to prefer this

Use this endpoint when a simulated resource has entered a reversible failure state (instance_down or database_overload) and you want the simulation engine to automatically heal it over the next few steps. Do not use it for instance_kill states, which are permanent. Prefer this over re-provisioning when the goal is simulating real-world incident recovery workflows within an existing simulation run.

## Known failure modes

- Resource not found by ID or name — returns error indicating no matching resource in the simulation
- Resource is in an instance_kill state (permanent) — endpoint cannot recover permanently killed resources
- Simulation ID does not exist or is inaccessible — returns 404 or authorization error
- Neither resourceId nor resourceName provided — returns validation error
- Payment failure (x402) — call rejected if USDC micropayment is not processed

## How this service works

Clear a single failed resource's reversible failure state (instance_down / database_overload; instance_kill is permanent) so the engine restores it to healthy over the next few steps.

## Output

The endpoint returns confirmation that the reversible failure state has been cleared for the specified resource. On success, the simulation engine will automatically restore the resource to a healthy state over the next few simulation steps. Note: instance_kill failures are permanent and cannot be recovered via this endpoint.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "resourceId": {
   "type": "string",
   "description": "ID of the failed resource to recover. Provide this or resourceName."
  },
  "resourceName": {
   "type": "string",
   "description": "Name of the failed resource to recover (case-insensitive exact match). Provide this or resourceId."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/cloud-world-model-recover-simulation-resource-e3c56180/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)