# ONE Engine – Records Omit Fields

> ONE Engine – Records Omit Fields is a paid API for AI agents from one-search.one-engine.workers.dev, paid per call via x402, $0.0065/call, status unknown (last checked 2026-10-02).

Removes specified keys from an array of JSON records, returning the records with those fields omitted

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v3/records/omit/t7?utm_source=zero.xyz
- Price: $0.0065/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/one-engine-records-omit-fields-ecfa2b97
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-Kk2LTQTCDCYVpmW8uv1l

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 one-engine-records-omit-fields-ecfa2b97 -d '<json body>'
```

Example prompt: Take these 50 user records and remove the 'password', 'ssn', and 'internalId' fields from every one before I send them to the reporting dashboard.

## When to prefer this

Use this endpoint when you need to bulk-strip or filter specific fields from up to 500 JSON records in a single call. Prefer it over manual field deletion when working inside an agent pipeline that already uses x402 micropayments on Base, or when you need a fast, low-cost, stateless transformation without spinning up custom ETL logic. Particularly suited for data sanitization, PII redaction, and API response cleaning before forwarding records downstream.

## Known failure modes

- Missing required 'records' field returns a validation error
- Records array exceeds 500-item limit causes rejection
- Malformed JSON in records causes parse error
- Keys array references non-existent field names (silently ignored — field not present, no error)
- Payment failure via x402 returns 402 status before processing begins

## How this service works

Low-cost pay-per-call utility APIs for autonomous agents using x402 on Base.

## Output

An array of JSON objects identical to the input records but with the specified keys removed. Each record has the omitted fields stripped, any renames applied, and any missing values filled with the provided defaults.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "records"
 ],
 "properties": {
  "keys": {
   "type": "array"
  },
  "rename": {
   "type": "object"
  },
  "records": {
   "type": "array",
   "description": "Up to 500 JSON objects"
  },
  "defaults": {
   "type": "object"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "additionalProperties": true
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/one-engine-records-omit-fields-ecfa2b97/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from one-search.one-engine.workers.dev](https://www.zero.xyz/host/one-search.one-engine.workers.dev/llms.txt)