# ONE Engine Object Entries

> ONE Engine Object Entries 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).

Extracts all key-value entries from a JSON object, returning them as an array of [key, value] pairs with a count.

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v1/object/entries?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-object-entries-f5ffcad7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_9RJpw2ORgbgDMRsei6IiO

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-object-entries-f5ffcad7 -d '<json body>'
```

Example prompt: Can you break down this JSON object into its individual key-value entries for me? The object is {"name": "Alice", "age": 30, "city": "NYC"}.

## When to prefer this

Choose this endpoint when you need a simple, low-cost ($0.001 USDC) utility call to enumerate the key-value entries of a flat JSON object, especially in autonomous agent workflows where programmatic decomposition of dynamic or unknown objects is needed without spinning up custom code execution.

## Known failure modes

- Input is not a valid JSON object — may return an error or empty entries
- Missing or malformed 'value' field in request body — endpoint may return 0 entries or error
- Input contains deeply nested objects — only top-level entries are returned, not recursive
- Payment failure via x402 — request blocked if USDC micropayment is not fulfilled

## How this service works

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

## Output

Returns a JSON object with a 'count' field indicating the number of entries, and an 'entries' array where each element is a two-element array [key, value] representing one property of the input object.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "value": {
   "type": "object"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "count": 2,
  "entries": [
   [
    "a",
    1
   ],
   [
    "b",
    2
   ]
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/one-engine-object-entries-f5ffcad7/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)