# Cloud Simulation Traffic Spike Injector

> Cloud Simulation Traffic Spike Injector 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-13).

Injects a 2×–5× random traffic spike into a running cloud infrastructure simulation.

## Facts

- Endpoint: POST https://www.cloudworldmodel.ai/api/simulations/cc2c137c-d4d4-406e-8774-6813f9904848/inject-traffic
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/cloud-simulation-traffic-spike-injector-e7d9a1f3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-dpHsN-gQjBJZ9XWKE5JJ

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-traffic-spike-injector-e7d9a1f3 -d '<json body>'
```

Example prompt: Inject a random traffic spike into my running cloud simulation — I want to see how it handles a sudden 2x to 5x surge and what the simulation state looks like afterward.

## When to prefer this

Use this endpoint when you need to test how a cloud simulation responds to sudden, unpredictable traffic bursts — specifically a randomized 2×–5× multiplier. Prefer this over manual timestep advancement when the goal is chaos/resilience testing rather than deterministic progression. Complements the kill-node endpoint for comprehensive fault and load simulation scenarios.

## Known failure modes

- Simulation ID not found — returns 404 if the specified simulation UUID does not exist or has ended
- Simulation not in running state — returns 400/409 if the simulation is paused, completed, or not started
- Invalid request body — returns 422 if required fields are missing or malformed
- Payment required — returns 402 if no valid payment or session JWT is present
- Rate limiting — returns 429 if too many spike injections are attempted in rapid succession

## How this service works

Inject traffic into a running simulation — provide `targetRps` (absolute RPS) or `deltaPercent` (relative change, e.g. 75 for +75%); omit both only when a random uncontrolled spike is intentional.

## Output

Returns a JSON object containing a simulation event record describing the injected traffic spike and the updated simulation state after the spike has been applied, including affected nodes, new traffic levels, and any triggered autoscaling or failure events.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "targetRps": {
   "type": "integer",
   "maximum": 500000,
   "minimum": 1,
   "description": "Absolute traffic target in RPS. Takes precedence over deltaPercent. Deactivates any active traffic patterns so the level persists across steps."
  },
  "deltaPercent": {
   "type": "number",
   "description": "Relative traffic change in percent (e.g. 75 = +75% of current traffic). Ignored when targetRps is supplied.",
   "exclusiveMinimum": -100
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/cloud-simulation-traffic-spike-injector-e7d9a1f3/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)