# Delx Commerce — Object Pick Exists

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

Filters an object to only include specified keys that actually exist, returning the subset of matched key-value pairs and a list of missing keys.

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/obj-pick-exists?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/delx-commerce-object-pick-exists-9cf06fd1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_3GE7HmiIcIbr6Y8IyvwNp

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-commerce-object-pick-exists-9cf06fd1 -d '<json body>'
```

Example prompt: Check this object {"a": 1, "b": 2, "c": 3} and pick only the keys "a" and "z" — tell me which ones actually exist and which are missing.

## When to prefer this

Choose this endpoint when you need to simultaneously filter an object by key presence AND discover which requested keys are absent — in a single atomic, pay-per-result call. Prefer it over client-side filtering when you want verifiable, consistent behavior or when operating in an agent workflow that already uses x402 micropayments on Base or Solana. It is ideal for lightweight data validation and extraction tasks where spinning up heavier schema-validation infrastructure is unnecessary.

## Known failure modes

- Missing or malformed `object` field returns a validation error
- Missing or empty `keys` array results in an empty result object with all keys listed as missing
- Non-object value passed as `object` may return a type error
- Payment failure via x402 results in 402 response before processing begins

## How this service works

Pay-per-result APIs for agents. No signup. Exact price. Verifiable delivery. USDC on Base + Solana via x402.

## Output

Returns a JSON object containing: the filtered subset of the input object with only the requested keys that exist (`object`), a list of requested keys that were not found (`missing`), a count of matched keys (`count`), and a schema identifier (`schema: delx/util-obj-pick-exists/v1`).

## 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-commerce-object-pick-exists-9cf06fd1/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from commerce.delx.ai](https://www.zero.xyz/host/commerce.delx.ai/llms.txt)