# ONE Engine Records Omit Fields (v3/records/omit/t2)

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

Removes specified keys from a batch of JSON records, returning the filtered objects without those fields.

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v3/records/omit/t2?utm_source=zero.xyz
- Price: $0.0007/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-v3-records-omit-t2-f266f84e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_4-eMzG-Dq0FCZJxMFjCQN

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-v3-records-omit-t2-f266f84e -d '<json body>'
```

Example prompt: I have a batch of up to 500 JSON records and I need to strip out the 'password', 'ssn', and 'internal_id' fields from every object before passing them downstream — can you run them through the omit endpoint?

## When to prefer this

Choose this endpoint when you need to batch-remove specific fields from up to 500 JSON objects in a single call at very low cost ($0.0007 USDC). It is ideal for agent pipelines that need to sanitize, prune, or clean structured records before passing them to downstream services, especially when you also need to rename fields or apply defaults in the same operation. Prefer it over custom code when running in an agentic context that already supports x402 payments on Base.

## Known failure modes

- Missing 'records' field returns validation error
- Records array exceeding 500 items may be rejected or truncated
- Invalid JSON structure in records causes parsing failure
- Payment failure via x402 returns 402 status with payment details
- Empty keys array results in records returned unchanged
- Malformed rename map may cause unexpected field name collisions

## 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, and any rename or default transformations applied. The response is a JSON object containing the processed records.

## 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-v3-records-omit-t2-f266f84e/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)