# Literal Redaction Plan Snapshot Compare

> Literal Redaction Plan Snapshot Compare is a paid API for AI agents from medien.halowerk.com, paid per call via x402, $0.031/call, status unknown (last checked 2026-10-16).

Compares caller-supplied literal redaction strings against a caller-provided previous snapshot to identify exact textual changes, with no semantic PII detection or baseline authentication.

## Facts

- Endpoint: POST https://medien.halowerk.com/v1/baumarkt/media/literal-redaction-plan/snapshot-compare?utm_source=zero.xyz
- Price: $0.031/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/literal-redaction-plan-snapshot-compare-f0934eaa
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_tGXFTIvMa6Yqq7TctU-1G

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 literal-redaction-plan-snapshot-compare-f0934eaa -d '<json body>'
```

Example prompt: Compare my current redaction plan snapshot against the baseline I captured last week and tell me exactly which literal redaction strings were added, removed, or changed — no semantic analysis, just exact literal diffs.

## When to prefer this

Choose this endpoint when you need exact, literal-only comparison of redaction plan snapshots — not semantic or PII-aware diffing. Ideal when you already have a caller-supplied baseline and want to detect precise string-level changes without re-authenticating historical output. Preferred over semantic redaction tools when audit trails require verbatim change witnesses and full current provider disclosure must be retained.

## Known failure modes

- Baseline snapshot not provided or malformed — returns validation error
- Current snapshot unavailable or provider call fails — returns provider error
- Redaction strings list is empty — may return empty diff with no witnesses
- Snapshot format mismatch between baseline and current — parse or schema error
- Rate limiting or payment failure via x402 — transaction rejected before execution

## How this service works

Compare Locate caller-specified literal redaction strings; no semantic PII detection. against a bounded caller-supplied previous snapshot and return exact change witnesses. Baseline is caller supplied and is never authenticated as historical server output. Pure bounded timing/source-quote validation runs before payment. Exactly one current motor call, zero baseline provider calls. Full current provider disclosure retained; baseline is not submitted to the provider.

## Output

Returns exact change witnesses — a structured diff of literal redaction strings that differ between the caller-supplied baseline snapshot and the current snapshot, including additions, removals, and modifications. No semantic PII inference is performed; only exact literal matches and mismatches are reported.

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/literal-redaction-plan-snapshot-compare-f0934eaa/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from medien.halowerk.com](https://www.zero.xyz/host/medien.halowerk.com/llms.txt)