# ONE Engine Records Omit (t3)

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

Filters specified keys out of an array of JSON records, optionally renaming fields and applying defaults before returning the cleaned objects.

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v3/records/omit/t3?utm_source=zero.xyz
- Price: $0.001/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-t3-aa356eeb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_--PNoR76_e_S8Fh3Q6BjZ

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-t3-aa356eeb -d '<json body>'
```

Example prompt: I have a batch of up to 500 user records and I need to strip out the 'password', 'ssn', and 'internalId' fields from each one — can you run them through the ONE Engine omit endpoint and give me back the cleaned objects?

## When to prefer this

Choose this endpoint when you need a lightweight, pay-per-call solution to strip, rename, or apply defaults to batches of up to 500 JSON records without standing up your own transformation infrastructure. It is ideal for agentic pipelines on Base where micro-payments via x402 are already in use and you want a serverless, low-cost data-cleaning step between API calls.

## Known failure modes

- Missing required 'records' field returns a validation error
- Records array exceeding 500 items may be rejected or truncated
- Invalid JSON in the request body causes a parse error
- Payment not included or insufficient USDC triggers a 402 Payment Required response
- Specifying a key to omit that does not exist in records is typically silently ignored

## How this service works

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

## Output

Returns a JSON object containing the transformed array of records with the specified keys omitted, fields renamed according to the rename map, and any missing fields populated with the supplied defaults. The response schema is open-ended and mirrors the structure of the input records minus the omitted keys.

## 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-t3-aa356eeb/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)