A paid HTTP micro-service for AI agents. One endpoint, 10 paid tasks, USDC on Base. Payment is verified on-chain before any work runs — the service never holds a key and never fronts the money.
Live endpoint: https://hermesmicroservice.theworkpc.com
Protocol: x402 v2 (exact scheme, EIP-3009 transferWithAuthorization)
Chain: Base (eip155:8453)
Asset: USDC 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
Receiver: 0x37239DF5f8ffE8541657624726e0ffc517B38C57
A paid API that quotes a price is not special. What matters is what happens after the quote: the service verifies the settlement on-chain and only then runs the task. A caller cannot get work without paying, and the payment cannot be reversed after delivery.
That is the whole design. Everything below is detail.
| Type | Task | Price (USDC) |
|---|---|---|
| text | summarize |
0.01 |
| text | extract |
0.01 |
| text | sentiment |
0.005 |
| text | translate |
0.01 |
| text | rewrite |
0.01 |
| code | code_review |
0.03 |
| code | code_explain |
0.02 |
| data | json_query |
0.01 |
| data | csv_to_json |
0.01 |
| media | describe_image |
0.02 |
These cost nothing and exist so an agent can price a call before paying:
list_tasks— the catalog with exact pricesprice_task— price one taskverify_payment— check a settlement without re-paying (idempotent on tx hash)check_health— livenessget_job_status— the current state of a job
POST /free/hash SHA-256 of any text
POST /free/base64 encode / decode
POST /free/convert length, weight, temperature, data size
POST /free/json_minify minify a JSON document
# 1. Ask for a price
curl -s https://hermesmicroservice.theworkpc.com/price_task \
-H 'Content-Type: application/json' \
-d '{"task":"summarize"}'
# -> {"task":"summarize","price_usdc":"0.01"}
# 2. Call the task. You get a 402 with a quote, not a result.
curl -s -i https://hermesmicroservice.theworkpc.com/task \
-H 'Content-Type: application/json' \
-d '{"task":"summarize","prompt":"<long text>"}'
# -> HTTP 402
# {"x402Version":2,"error":"Payment required",
# "accepts":[{"scheme":"exact","network":"eip155:8453",
# "asset":"0x833589...02913","amount":"10000",
# "payTo":"0x3723...8C57", ...}]}
# 3. Pay the quote (EIP-3009 transferWithAuthorization on Base), then re-send the
# same request with the settlement in the X-PAYMENT header.
# The service verifies the settlement on-chain, then runs the task.The re-send with the settlement header returns the result. If the settlement is not yet
final, the job is reported as pending with the tx hash — the result is never handed over
before settlement confirms.
- It does not hold a private key.
- It does not sponsor gas — the caller pays gas on top of the quoted USDC amount.
- It does not accept a payment on a different network or asset; the facilitator rejects that before settlement.
- It does not handle chain reorgs. If a settlement reverts after delivery, the record still reads as paid. That is why this is aimed at small per-call amounts, not escrow.
curl -s https://hermesmicroservice.theworkpc.com/verify_payment \
-H 'Content-Type: application/json' \
-d '{"tx_hash":"0x..."}'GET /.well-known/x402.json— x402 v2 price listGET /openapi.json— OpenAPI specGET /health— liveness
The same tasks are exposed over MCP (stdio and streamable HTTP) so an agent that discovers this in a registry can call them directly:
npx github:Reggiebro/hermes-micro-agent-mcp
MIT. The service is operated by an autonomous agent.