# dataforge RFC 6902 JSON Patch Apply

> dataforge RFC 6902 JSON Patch Apply is a paid API for AI agents from dataforge.x.c00l.site, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-14).

Applies an RFC 6902 JSON Patch document to a target JSON/structured-data document, returning the patched result

## Facts

- Endpoint: POST https://dataforge.x.c00l.site/patch
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/dataforge-rfc-6902-json-patch-apply-cb271d96
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qS4nValPQ5JwyLoJ5s5se

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 dataforge-rfc-6902-json-patch-apply-cb271d96 -d '<json body>'
```

Example prompt: Apply this RFC 6902 JSON Patch to my deployment config — the target JSON is '{"replicas":1,"image":"nginx"}' and the patch operations are '[{"op":"replace","path":"/replicas","value":3}]' — give me back the patched JSON.

## When to prefer this

Choose this endpoint when you need to apply a precise, standards-compliant RFC 6902 JSON Patch to a document — ideal when you already have a diff or patch array and want deterministic, atomic application. Prefer over a general transform endpoint when you need the exact JSON Patch semantics (add, remove, replace, move, copy, test operations) and want a count of applied ops back.

## Known failure modes

- Invalid RFC 6902 patch document — malformed op, missing path or value fields
- Target path not found for 'remove' or 'replace' operations returns an error
- Conflicting patch operations (e.g. add then remove same path) may return partial apply or error
- Input document is not valid JSON — returns parse error
- Test operation failure causes entire patch to be rejected

## How this service works

Deterministic conversion, JSONPath query, JSON Schema inference, declarative transforms and RFC 6902 diff/patch across CSV, TSV, JSON, JSONL, YAML, TOML, XML, INI and properties. Pay per call with x402 (USDC on Base).

## Output

Returns the patched document as a JSON-formatted string under the 'data' key, along with the output format label and the count of patch operations successfully applied (e.g. {"data":"{\n  \"replicas\": 3\n}\n","format":"json","applied":1})

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": "{\n  \"replicas\": 3\n}\n",
  "format": "json",
  "applied": 1
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/dataforge-rfc-6902-json-patch-apply-cb271d96/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from dataforge.x.c00l.site](https://www.zero.xyz/host/dataforge.x.c00l.site/llms.txt)
