# HALOWERK x402werk — Offer Parse

> HALOWERK x402werk — Offer Parse is a paid API for AI agents from x402.netzhandwerker.de, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-15).

Fetches and parses an x402 payment challenge (HTTP 402) from a remote URL or a supplied challenge object, returning structured payment requirement details.

## Facts

- Endpoint: POST https://x402.netzhandwerker.de/offer/parse
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/halowerk-x402werk-offer-parse-b3069de6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_898Mcdg2tS74HsnrYqdy5

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 halowerk-x402werk-offer-parse-b3069de6 -d '<json body>'
```

Example prompt: Can you fetch and parse the x402 payment challenge from https://api.example.com/paid-resource and tell me what the price and payment address are?

## When to prefer this

Use this endpoint when an AI agent needs to inspect or understand the payment requirements of an x402-protected endpoint before deciding whether and how to pay. It is the right choice when you have either a URL of a paywalled API or a raw 402 challenge object and need structured payment details (price, network, address, version) extracted without executing any actual payment. Prefer this over attempting to call the paid endpoint directly when you need to audit, display, or route based on payment terms.

## Known failure modes

- Target URL is private, loopback, or link-local — rejected with a 4xx error
- Target URL does not return an x402 (HTTP 402) challenge — parsing fails
- Supplied challenge object does not conform to x402 v1 or v2 schema — parse error
- Request times out before the remote endpoint responds (timeout_ms exceeded, max 12000ms)
- Malformed URL provided (does not match ^https?:// pattern or exceeds 2048 chars)
- Remote endpoint is unreachable or returns a non-402 HTTP status

## How this service works

HALOWERK x402werk — bezahlte Endpunkte nach x402. Preise in USDC auf Base Mainnet.

## Output

A structured object containing the parsed x402 payment challenge fields: protocol version (v1 or v2), required payment amount (in USDC), accepted blockchain network (e.g. Base Mainnet), recipient payment address, and any additional offer metadata extracted from the challenge.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "pattern": "^https?://",
   "maxLength": 2048,
   "description": "Absolute http or https URL of the paid endpoint whose 402 challenge should be read. Private, loopback and link-local targets are rejected."
  },
  "challenge": {
   "type": "object",
   "description": "A 402 challenge object you already hold, in x402 v1 or v2 form. Use this instead of url when nothing should be fetched."
  },
  "timeout_ms": {
   "type": "integer",
   "default": 6000,
   "maximum": 12000,
   "minimum": 1000,
   "description": "Time budget for fetching the foreign challenge."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/halowerk-x402werk-offer-parse-b3069de6/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.netzhandwerker.de](https://www.zero.xyz/host/x402.netzhandwerker.de/llms.txt)