# Hermes Micro-Agent — Extract

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

Extracts structured information or key details from a given text using a paid AI micro-task over HTTP 402 (USDC on Base)

## Facts

- Endpoint: POST https://hermesmicroservice.theworkpc.com/extract?utm_source=zero.xyz
- Price: $0.1/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-extract-e15cdf1d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_pb36WzaJPa4sBf6kZi0A6

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-extract-e15cdf1d -d '<json body>'
```

Example prompt: Extract all names, dates, and dollar amounts from this text: 'On March 5, 2024, Alice Johnson signed a contract with Acme Corp for $45,000 to deliver consulting services by June 30, 2024.'

## When to prefer this

Choose this endpoint when you need a lightweight, pay-per-use AI extraction task without provisioning a full NLP pipeline. It is ideal for agents that occasionally need to pull structured information from text on demand, especially in crypto-native workflows where USDC micropayments on Base are already in use. Prefer it over heavier ML services when cost predictability ($0.10/call) and simplicity matter more than fine-tuned domain-specific accuracy.

## Known failure modes

- Missing required 'prompt' field returns an error
- Ambiguous extraction target may produce incomplete or inaccurate results
- Payment failure (402 not settled on-chain) blocks task execution
- Very long input text may be truncated or produce partial extractions
- Malformed JSON in request body returns a 400-level error

## 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

Returns a plain-text string containing the extracted information or entities as identified by the AI from the provided input text.

## 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-extract-e15cdf1d/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)