# Hermes Micro-Agent – JSON Query

> Hermes Micro-Agent – JSON Query is a paid API for AI agents from hermesmicroservice.theworkpc.com, paid per call via x402, $0.15/call, status unknown (last checked 2026-10-30).

Executes a JSONPath or natural-language query against a JSON payload and returns the result, paid per-call via on-chain USDC on Base

## Facts

- Endpoint: POST https://hermesmicroservice.theworkpc.com/json_query?utm_source=zero.xyz
- Price: $0.15/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-30
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/hermes-micro-agent-json-query-b3e2b2df
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_M82jAlBObVr5hkDDILs2Q

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 hermes-micro-agent-json-query-b3e2b2df -d '<json body>'
```

Example prompt: I have this JSON blob: {"orders":[{"id":1,"status":"shipped"},{"id":2,"status":"pending"}]} — can you query it to extract just the ids of all orders with status 'pending'?

## When to prefer this

Choose this endpoint when you need to extract or query specific values from a JSON string or object on-demand without running local code, especially in agentic pipelines where JSON data arrives as a string and needs field extraction before the next step. It is well-suited for lightweight, pay-per-use JSON field lookups without spinning up a full data processing service. Prefer alternatives if you need bulk processing of many JSON documents or if you require complex aggregations beyond simple path extraction.

## Known failure modes

- Malformed JSON input causes parsing failure and returns an error string
- Ambiguous or poorly formed JSONPath/query prompt may return unexpected or empty results
- Payment on Base/USDC fails or is not confirmed, resulting in HTTP 402 rejection before execution
- Very large JSON payloads may exceed token or size limits
- Query references a non-existent key, returning null or empty result

## How this service works

20 paid AI and data micro-tasks over HTTP 402 on Base (USDC): summarize, extract, keywords, sentiment, translate, rewrite, proofread, python_debug, code_lint, code_explain, code_refactor, code_review, json_minify, json_query, csv_to_json, hash, base64, convert, describe_image, probe_media. Each call is priced per-task and verified on-chain before execution.

## Output

A plain string containing the result of the JSON query — this could be a single extracted value, a comma-separated list, a JSON snippet, or a formatted representation of the matched data, depending on the query prompt provided.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "prompt"
 ],
 "properties": {
  "task": {
   "type": "string",
   "description": "Which micro-task to run"
  },
  "input": {
   "type": "string",
   "description": "Alias for prompt"
  },
  "prompt": {
   "type": "string",
   "description": "Text to process"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "string"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/hermes-micro-agent-json-query-b3e2b2df/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from hermesmicroservice.theworkpc.com](https://www.zero.xyz/host/hermesmicroservice.theworkpc.com/llms.txt)