HALOWERK kettenwerk
Runs each step separately as a simulation (eth_call with state override) against the current chain state and reports each result on its own, so a token that can be received but not moved on is visible as exactly that. Nothing is ever executed: no transaction is broadcast, no key is held, no approval is given. Limits, and they are decisive: can_buy and can_sell through a DEX router are NOT simulated - that needs a funded account and a router path this service cannot back, so both stay null. What
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://kette.halowerk.com/llms.txt",
"name": "honeypot_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": "10000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 300
}
],
"pricing": "https://kette.halowerk.com/pricing",
"summary": "Simulates a transfer of an ERC-20 token against the live chain state with an overridden balance and reports, step by step, whether it goes through or reverts - without ever sending a transaction.",
"resource": {
"url": "https://kette.halowerk.com/token/honeypot",
"iconUrl": "https://kette.halowerk.com/favicon.svg",
"mimeType": "application/json",
"description": "Runs each step separately as a simulation (eth_call with state override) against the current chain state and reports each result on its own, so a token that can be received but not moved on is visible as exactly that. Nothing is ever executed: no transaction is broadcast, no key is held, no approval is given. Limits, and they are decisive: can_buy and can_sell through a DEX router are NOT simulated - that needs a funded account and a router path this service cannot back, so both stay null. What ",
"serviceName": "HALOWERK kettenwerk"
},
"extensions": {
"bazaar": {
"info": {
"input": {
"body": {
"chain": "eip155:8453",
"token": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"
},
"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": [
"chain",
"token"
],
"properties": {
"chain": {
"type": "string",
"description": "Chain identifier, for example ethereum, base, arbitrum, optimism, polygon or bsc."
},
"token": {
"type": "string",
"description": "ERC-20 contract address, 0x followed by 40 hex characters."
},
"holder": {
"type": "string",
"description": "Optional: an address that actually holds the token. Its balance is used as the source for the transfer simulation, which makes the result far more meaningful."
}
},
"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.010",
"description": "Runs each step separately as a simulation (eth_call with state override) against the current chain state and reports each result on its own, so a token that can be received but not moved on is visible as exactly that. Nothing is ever executed: no transaction is broadcast, no key is held, no approval is given. Limits, and they are decisive: can_buy and can_sell through a DEX router are NOT simulated - that needs a funded account and a router path this service cannot back, so both stay null. What IS tested is the transfer itself, which is where most traps sit. Balances are overridden at the account level, not inside the token contract storage, so a token that reads balances from its own mapping may report zero and the step then ends as \"unklar\" rather than as a pass. A negative result is no proof of fraud and a positive one is no clearance: the contract can change its behaviour after this check, and an owner with a tax switch can flip it at any time. That sentence belongs to every answer. Where the simulation does not carry, the verdict is \"unklar\" and the fields stay null.",
"inputSchema": {
"type": "object",
"required": [
"chain",
"token"
],
"properties": {
"chain": {
"type": "string",
"description": "Chain identifier, for example ethereum, base, arbitrum, optimism, polygon or bsc."
},
"token": {
"type": "string",
"description": "ERC-20 contract address, 0x followed by 40 hex characters."
},
"holder": {
"type": "string",
"description": "Optional: an address that actually holds the token. Its balance is used as the source for the transfer simulation, which makes the result far more meaningful."
}
},
"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.",
"outputSchema": {
"type": "object"
},
"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.01 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
- 10000 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": "10000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 300
}
]Extensions
{
"bazaar": {
"info": {
"input": {
"body": {
"chain": "eip155:8453",
"token": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"
},
"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": [
"chain",
"token"
],
"properties": {
"chain": {
"type": "string",
"description": "Chain identifier, for example ethereum, base, arbitrum, optimism, polygon or bsc."
},
"token": {
"type": "string",
"description": "ERC-20 contract address, 0x followed by 40 hex characters."
},
"holder": {
"type": "string",
"description": "Optional: an address that actually holds the token. Its balance is used as the source for the transfer simulation, which makes the result far more meaningful."
}
},
"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 09:09Z
- Last indexed by Roundhouse
- 2026-09-10 09:00Z
- Last enriched (probe, favicon, geo)
- 2026-09-24 12:15Z
- 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. 16 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 HALOWERK kettenwerk 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=HALOWERK%20kettenwerk' 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://kette.halowerk.com/token/honeypot, 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.