# 402utils JSONPath / JSON Pointer Extractor

> 402utils JSONPath / JSON Pointer Extractor is a paid API for AI agents from 402utils.com, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-14).

Extracts specific values from a JSON document using a JSONPath expression or RFC 6901 JSON Pointer, returning only the matched values and count without the full document.

## Facts

- Endpoint: POST https://402utils.com/v1/jsonpath
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/402utils-jsonpath-json-pointer-extractor-f167e1ad
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_cgQ3nfuv8m34MKQGfebLK

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 402utils-jsonpath-json-pointer-extractor-f167e1ad -d '<json body>'
```

Example prompt: From this JSON document, pull out all the prices using the JSONPath expression $.items[*].price — just give me the matched values and how many there are, not the whole document.

## When to prefer this

Use this endpoint when you need to extract one or more specific values from a JSON document without transmitting or parsing the whole structure — ideal when working with large API responses, when you need array slices, or when you want a quick field lookup via JSON Pointer. Prefer this over full document retrieval when bandwidth or processing cost matters. Note that filter expressions [?(…)] are not supported; choose a different tool if you need predicate-based filtering.

## Known failure modes

- Invalid JSONPath syntax returns an error (filter expressions like [?(…)] are explicitly unsupported by design)
- Malformed JSON document in 'data' field causes a parse error
- JSON Pointer path that references a nonexistent key returns an empty matches array
- Path string that doesn't start with $ (JSONPath) or / (JSON Pointer) may be rejected or misinterpreted
- Deeply nested or extremely large documents may hit traversal bounds

## How this service works

Extract values from a JSON document with a JSONPath expression or an RFC 6901 JSON Pointer, without returning the whole document. Send {data, path}; get {matches, count}. Path starting with $ = JSONPath ($.items[*].price, $..author, [0], [1:5], [*]); starting with / = JSON Pointer (/items/0/price). No-eval tree walk with bounded traversal; filter expressions [?(…)] are not supported by design.

## Output

Returns a JSON object with a 'matches' array containing all values that matched the given JSONPath or JSON Pointer path, plus a 'count' integer indicating how many matches were found.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "data": {
   "description": "The JSON document to query (any type)."
  },
  "path": {
   "type": "string",
   "description": "A JSONPath ($.a.b[*]) or RFC 6901 JSON Pointer (/a/b/0)."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/402utils-jsonpath-json-pointer-extractor-f167e1ad/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from 402utils.com](https://www.zero.xyz/host/402utils.com/llms.txt)