# Delx Object Pick Exists

> Delx Object Pick Exists is a paid API for AI agents from api.delx.ai, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-13).

Filters an object to only the keys from a provided whitelist that actually exist on the object, returning the filtered object, missing keys, and count.

## Facts

- Endpoint: POST https://api.delx.ai/api/v1/x402/obj-pick-exists
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/delx-object-pick-exists-3f6928b7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hi4XC9CXKQjmfhrHT86VO

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 delx-object-pick-exists-3f6928b7 -d '<json body>'
```

Example prompt: From this user profile object {name: 'Alice', age: 30, password: 'secret', role: 'admin'}, pick only the keys ['name', 'age', 'email'] that actually exist on it — tell me which ones are present and which are missing.

## When to prefer this

Choose this endpoint when you need to safely whitelist a set of keys on an object without accidentally inventing values for keys that don't exist. It is ideal for sanitizing agent outputs, trimming API responses to a known schema, or auditing which expected fields are present in a payload — all without any network calls, external data access, or data retention.

## Known failure modes

- Missing or invalid 'keys' array returns an error or empty result
- Passing a non-object as 'object' may cause a validation error
- Empty keys array results in an empty object with all keys marked missing
- Keys with undefined or null values may be treated as existing or missing depending on implementation
- Payment failure (insufficient USDC balance) blocks the call via x402

## How this service works

Pick only keys that exist on an object. Call when you whitelist agent fields without inventing missing keys. Returns object, missing, count for $0.001 USDC via x402 on Base. No network, no keys, no retention; first-party local JSON only. Results are advisory; the caller owns budgets, auth, and production controls.

## Output

Returns a JSON object with three fields: 'object' (a new object containing only the whitelisted keys that existed on the input), 'missing' (an array of keys from the whitelist that were not found on the input object), and 'count' (the number of keys successfully picked).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "keys": {
   "type": "array",
   "description": "Input field: keys."
  },
  "object": {
   "type": "object",
   "description": "Input field: object."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "count": 1,
  "object": {
   "a": 1
  },
  "schema": "delx/util-obj-pick-exists/v1",
  "missing": [
   "z"
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-object-pick-exists-3f6928b7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.delx.ai](https://www.zero.xyz/host/api.delx.ai/llms.txt)