# Delx Commerce Object Size

> Delx Commerce Object Size 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).

Computes and returns the number of top-level keys (size) of a given JSON object

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/obj-size?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-size-95e1aba5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__mC982eBOx_m4dBGYno5s

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-size-95e1aba5 -d '<json body>'
```

Example prompt: How many top-level keys does this JSON object have: {"name": "Alice", "age": 30, "city": "NYC"}?

## When to prefer this

Choose this endpoint when you need a quick, cheap ($0.001 USDC), pay-per-result computation of a JSON object's top-level key count without any signup or authentication overhead. It is well-suited for agents that need lightweight introspection of data payloads on-demand, especially in micropayment-enabled x402 workflows on Base or Solana.

## Known failure modes

- Input is not a valid JSON object — may return an error or unexpected result
- Input is null or missing — likely returns a 400-style error
- Nested objects are not counted recursively, only top-level keys are measured
- Payment failure via x402 protocol prevents the call from completing

## 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 'size' (an integer representing the number of top-level keys in the input object) and 'schema' (a string identifier 'delx/util-obj-size/v1' indicating the response format version).

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "size": 2,
  "schema": "delx/util-obj-size/v1"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-commerce-object-size-95e1aba5/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)
