# Penny Army Research – Redact Fields

> Penny Army Research – Redact Fields is a paid API for AI agents from penny-army-reference-mainnet.spruceboundgranitestudio.workers.dev, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-11).

Recursively replaces values at exactly named object keys throughout a JSON payload, enabling field-level redaction by key name.

## Facts

- Endpoint: POST https://penny-army-reference-mainnet.spruceboundgranitestudio.workers.dev/v1/probes/redact-fields?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/penny-army-research-redact-fields-1904702b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-F-jDKvUSJ4iMbQZfaEZW

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 penny-army-research-redact-fields-1904702b -d '<json body>'
```

Example prompt: Take this JSON payload and redact the values for the fields 'email', 'ssn', and 'phone' everywhere they appear, no matter how deeply nested — replace those fields' values recursively throughout the object.

## When to prefer this

Choose this endpoint when you need to programmatically redact or replace values at specifically named keys throughout an arbitrarily nested JSON structure without writing custom recursive traversal logic. It is best suited for pipeline steps that must strip sensitive fields before logging, sharing, or storing JSON data. Unlike secret-detection services, this endpoint requires you to explicitly name the fields to redact rather than auto-detecting secrets.

## Known failure modes

- Payload or fields array missing — 400 validation error
- Field name exceeds 128 characters — rejected by schema
- More than 64 field names supplied — exceeds maxItems limit
- Malformed JSON payload — parse error returned
- Fields that don't exist in the payload are silently ignored — no error raised
- Non-object/non-array payload types may not be recursively processed

## How this service works

Replace values at exactly named object keys recursively; no secret detection and no guarantee that unlisted fields are safe to share.

## Output

A transformed JSON object identical in structure to the input payload, but with the values at every occurrence of the specified field names replaced (redacted). The replacement is applied recursively through all nested objects. Note: no secret detection is performed and fields not listed are not guaranteed safe.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "fields": {
   "type": "array",
   "items": {
    "type": "string",
    "maxLength": 128,
    "minLength": 1
   },
   "maxItems": 64
  },
  "payload": {
   "$ref": "#/properties/input/properties/body/$defs/__schema0"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/penny-army-research-redact-fields-1904702b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from penny-army-reference-mainnet.spruceboundgranitestudio.workers.dev](https://www.zero.xyz/host/penny-army-reference-mainnet.spruceboundgranitestudio.workers.dev/llms.txt)