# SignalDesk AI Deep Merge

> SignalDesk AI Deep Merge is a paid API for AI agents from x402-agent.kariguetoazul.workers.dev, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-12).

Recursively merges two JSON objects (left and right), with right-side values taking precedence over left-side values at each key level

## Facts

- Endpoint: POST https://x402-agent.kariguetoazul.workers.dev/api/json/deep-merge?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/signaldesk-ai-deep-merge-d5f90e41
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wYpqDwVGw2ZSXmCFvTRAe

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 signaldesk-ai-deep-merge-d5f90e41 -d '<json body>'
```

Example prompt: Can you deep merge these two JSON objects for me — take {"user":{"name":"Ana"}} as the left and {"user":{"age":30}} as the right, so the nested keys from both are combined into one object?

## When to prefer this

Choose this endpoint when you need to recursively merge two nested JSON objects and want right-side values to override left-side values at every depth level. It is appropriate for merging configuration files, combining partial API responses, or applying user overrides on top of defaults. Prefer it over shallow Object.assign-style merges when nested keys must be individually reconciled rather than replaced wholesale.

## Known failure modes

- Missing or malformed 'left' or 'right' fields returns an error
- Non-object values (e.g. arrays or primitives) passed as left/right may produce unexpected results
- Payment of 0.001 USDC via x402 required; missing payment header returns 402
- Network or worker execution limits may cause timeout on very large objects

## How this service works

Evidence-backed autonomous AI jobs and paid data tools. Queue/D1/cron run outside the chat; free quotas and bounded execution apply.

## Output

A single merged JSON object where all keys from both left and right inputs are present at every nesting level; when the same key exists in both, the right-hand value takes precedence. The result is returned as a JSON response under a 'data' key.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "left": {
   "description": "JSON object."
  },
  "right": {
   "description": "JSON object."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {
   "user": {
    "age": 30,
    "name": "Ana"
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/signaldesk-ai-deep-merge-d5f90e41/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-agent.kariguetoazul.workers.dev](https://www.zero.xyz/host/x402-agent.kariguetoazul.workers.dev/llms.txt)