paket.halowerk.com
HALOWERK provides paid endpoints that AI agents call and pay for per request via x402 on Base. No account, no API key, no signup.
The wallet the 402 directs payment to. Its whole payment record — every payer, every chain — is on the merchant page.
Asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
The payTo wallet does not resolve to a registered ERC-8004 agent. That is not a verdict on the service — most of the catalog is unregistered.
Live 402 challenge
Captured by the enrichment pass, not read just now. Prices can change — always read the 402 the endpoint answers with.
{
"docs": "https://paket.halowerk.com/llms.txt",
"name": "lifecycle_check",
"error": "payment_required",
"accepts": [
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"asset": "USDC",
"version": "2",
"eip712Domain": {
"name": "USD Coin",
"chainId": 8453,
"version": "2",
"verifyingContract": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"
},
"network_name": "Base Mainnet",
"assetTransferMethod": "eip3009"
},
"payTo": "0x2880EdfFF13100677Bf97A3CBdF3Bc34771C4E5E",
"amount": "3000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 300
}
],
"pricing": "https://paket.halowerk.com/pricing",
"resource": {
"url": "https://paket.halowerk.com/v1/lifecycle-check",
"mimeType": "application/json",
"description": "Answers the question an agent actually has about a product cycle: for the version in use, is support over, how many days remain, and where should it move. Given a product identifier from endoflife.date and optionally a version, it locates the matching release line and returns the release date, the end of active support, the end of life, the end of extended security support where one exists, whether the line is an LTS line, the latest patch release within that line and the number of days to each…"
},
"extensions": {
"bazaar": {
"info": {
"input": {
"body": {
"product": "nodejs",
"version": "20.11.1"
},
"type": "http",
"method": "POST",
"bodyType": "json"
}
},
"schema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"input"
],
"properties": {
"input": {
"type": "object",
"required": [
"type",
"method",
"bodyType",
"body"
],
"properties": {
"body": {
"type": "object",
"required": [
"product"
],
"properties": {
"product": {
"type": "string",
"maxLength": 80,
"minLength": 1,
"description": "Product identifier as used by endoflife.date, e.g. nodejs, python, postgresql, ubuntu, debian, redis."
},
"version": {
"type": "string",
"maxLength": 40,
"description": "The version in use, e.g. 20.11.1. Without it every cycle is returned."
}
},
"additionalProperties": false
},
"type": {
"type": "string",
"const": "http"
},
"method": {
"enum": [
"POST",
"PUT",
"PATCH"
],
"type": "string"
},
"bodyType": {
"enum": [
"json",
"form-data",
"text"
],
"type": "string"
}
},
"additionalProperties": false
}
}
}
}
},
"price_usdc": "0.003",
"description": "Answers the question an agent actually has about a product cycle: for the version in use, is support over, how many days remain, and where should it move. Given a product identifier from endoflife.date and optionally a version, it locates the matching release line and returns the release date, the end of active support, the end of life, the end of extended security support where one exists, whether the line is an LTS line, the latest patch release within that line and the number of days to each boundary — negative when the date has passed. Without a version it returns every cycle with the same fields, marks which are still maintained and names the newest supported line. Version matching walks from the most specific line downwards, so 20.11.1 finds the cycle 20 rather than failing, and the matched cycle is always named so a wrong match is visible. Dates that the source leaves open come back as null with the cycle marked accordingly, never as a guess. The authoritative statement is always the vendor announcement; this is a normalised reading of a community-maintained dataset.",
"inputSchema": {
"type": "object",
"required": [
"product"
],
"properties": {
"product": {
"type": "string",
"maxLength": 80,
"minLength": 1,
"description": "Product identifier as used by endoflife.date, e.g. nodejs, python, postgresql, ubuntu, debian, redis."
},
"version": {
"type": "string",
"maxLength": 40,
"description": "The version in use, e.g. 20.11.1. Without it every cycle is returned."
}
},
"additionalProperties": false
},
"price_model": "per_call",
"x402Version": 2,
"instructions": "Sign the accepted terms with an x402 client and repeat the request with the payment header.",
"payment_header": "PAYMENT-SIGNATURE",
"capability_request": {
"url": "https://bedarf.halowerk.com/capabilities/request",
"cost": "free",
"method": "POST",
"description": "Missing a capability, or does the scope not fit? Report the need here - no payment required. Similar reports are bundled; the response returns an id you can check back on.",
"body_example": {
"max_price": 0.01,
"description": "what exactly is needed",
"requested_capability": "short label"
}
}
}Accepts
The payment requirements as published to the catalog. Read the live 402 before paying — a price here is a claim, not a quote.
Pay 0.003 USDC on Base to 0x2880…C4E5E. The signed payment is good for 5 minutes.
- Paid to
- 0x2880…C4E5E
- USD Coin contract
- 0x8335…02913
- Payment window
- 5 minutes
- As published
- 3000 smallest units
The catalog’s raw entry
[
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"asset": "USDC",
"version": "2",
"eip712Domain": {
"name": "USD Coin",
"chainId": 8453,
"version": "2",
"verifyingContract": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"
},
"network_name": "Base Mainnet",
"assetTransferMethod": "eip3009"
},
"payTo": "0x2880EdfFF13100677Bf97A3CBdF3Bc34771C4E5E",
"amount": "3000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 300
}
]Extensions
{
"bazaar": {
"info": {
"input": {
"body": {
"product": "nodejs",
"version": "20.11.1"
},
"type": "http",
"method": "POST",
"bodyType": "json"
}
},
"schema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"input"
],
"properties": {
"input": {
"type": "object",
"required": [
"type",
"method",
"bodyType",
"body"
],
"properties": {
"body": {
"type": "object",
"required": [
"product"
],
"properties": {
"product": {
"type": "string",
"maxLength": 80,
"minLength": 1,
"description": "Product identifier as used by endoflife.date, e.g. nodejs, python, postgresql, ubuntu, debian, redis."
},
"version": {
"type": "string",
"maxLength": 40,
"description": "The version in use, e.g. 20.11.1. Without it every cycle is returned."
}
},
"additionalProperties": false
},
"type": {
"type": "string",
"const": "http"
},
"method": {
"enum": [
"POST",
"PUT",
"PATCH"
],
"type": "string"
},
"bodyType": {
"enum": [
"json",
"form-data",
"text"
],
"type": "string"
}
},
"additionalProperties": false
}
}
}
}
}Provenance
- Seen in the source catalog
- 2026-08-11 20:21Z
- Last indexed by Roundhouse
- 2026-09-10 20:00Z
- Last enriched (probe, favicon, geo)
- 2026-09-21 05:45Z
- x402 version
- 2
- Max timeout
- 300s
- Liveness probe
- HTTP 402
Hand this page to an agent
Copy the prompt and paste it into Claude, an MCP client or your own agent — it will vet this service and call it over the free read API. No key, no account.
GET api.roundhouseai.io/v0/endpoints
This endpoint's own trailing-30-day call count, as published by the upstream catalog and snapshotted daily. 18 snapshots so far. Verified volume counts only settlements with an on-chain EIP-3009 marker.
Show the promptHide the prompt
Using Roundhouse, look up the x402 service paket.halowerk.com and tell me whether it is worth paying: what a call costs, whether the endpoint answered when last probed, and what its payment record actually shows. curl -s 'https://api.roundhouseai.io/v0/endpoints?q=paket.halowerk.com' curl -s 'https://api.roundhouseai.io/v0/merchants/<the payTo wallet returned above>' Then call it: read the price from the live 402 at https://paket.halowerk.com/v1/lifecycle-check, never from a cached figure, and pay with an x402 client. The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except /v0/unified* and /v0/endpoints. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402, or use an organization key from https://roundhouseai.io/dashboard/team. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.