# Data Toolkit – JMESPath Query

> Data Toolkit – JMESPath Query is a paid API for AI agents from data.openverbs.com, paid per call via x402, $0.004/call, status unknown (last checked 2026-09-14).

Evaluates a JMESPath expression against a supplied JSON value and returns the matching result

## Facts

- Endpoint: POST https://data.openverbs.com/v1/query
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/data-toolkit-jmespath-query-28a568b3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_YDeR8fdRHhfFNTmUuTRU1

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 data-toolkit-jmespath-query-28a568b3 -d '<json body>'
```

Example prompt: I have a JSON array of customer records and I want to pull out only the names of customers whose account balance is greater than 1000 — can you run a JMESPath query like `customers[?balance > \`1000\`].name` against this data?

## When to prefer this

Choose this endpoint when you need lightweight, serverless JSON querying via the well-standardised JMESPath language — ideal for extracting fields, filtering arrays, or projecting subsets of JSON without standing up your own processing infrastructure. Prefer it over general-purpose code execution endpoints when your transformation is expressible as a JMESPath query, since it is cheaper, faster, and stateless.

## Known failure modes

- Invalid JMESPath expression syntax — returns an error describing the parse failure
- Expression length exceeds 10,000 character maximum — validation error
- Missing required fields (data or expression) — schema validation error
- Expression is valid but matches nothing — returns null or empty array
- Input data is not valid JSON — parsing error

## How this service works

Evaluate a JMESPath expression against a JSON value and return the selected/projected result. A malformed expression is rejected before payment.

## Output

Returns the JSON value produced by evaluating the provided JMESPath expression against the input data — this can be a filtered array, a single scalar, a projected list of values, or null if nothing matches.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "type": "object",
     "required": [
      "data",
      "expression"
     ],
     "properties": {
      "data": {
       "description": "Any JSON value (object, array, string, number, boolean or null)."
      },
      "expression": {
       "type": "string",
       "maxLength": 10000,
       "minLength": 1,
       "description": "A JMESPath expression, e.g. `people[?age > `30`].name`."
      }
     },
     "additionalProperties": false
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/data-toolkit-jmespath-query-28a568b3/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from data.openverbs.com](https://www.zero.xyz/host/data.openverbs.com/llms.txt)