Agent Tools
Back to directory

kette.halowerk.com

https://kette.halowerk.com
● healthy general

Looks up a crypto asset by its exact NetSupply slug or an unambiguous symbol, then returns the scheduled releases inside a caller-selected window of up to 365 days. Unlock amounts remain decimal strings so large token quantities are not rounded. Each event states whether the schedule is enforced on-chain, how many lock objects it combines, when the promise was first recorded and how often it wa...

Category
general
Chains
eip155:8453
Price
$0.0020 USDC / call

Quality grade

How grading works
B+ 85.3 / 100
Availability 40.0 / 40
Endpoint responded (HTTP 200)
Payability 20.0 / 20
  • Answers a real HTTP 402 challenge
  • Publishes a /.well-known/x402 descriptor
  • Payment address on record
  • Settlement network declared
  • Price declared
Demand 25.3 / 40
30 distinct payers, 4075 USDC transfers in the last 30 days
Owner verified 0.0 / 3
Nobody has claimed this listing yet
Endpoint last checked 2 h ago. On-chain activity last read 29 h ago. Availability and on-chain demand are both re-probed daily; the grade updates automatically on the next pass.

Paid endpoints

24 resource(s) advertised by this origin.

POST https://kette.halowerk.com/token/resolve

A symbol is not an identity. Dozens of contracts carry the symbol USDC and most of them are not the one anyone means. This endpoint returns all of them rather than silently picking one: every match carries its chain, contract, on-chain symbol, name and decimals read directly from the contract, wheth

POST https://kette.halowerk.com/contract/verification

Checks one address on Ethereum, Base, Arbitrum, Optimism, Polygon or BNB Smart Chain against the open verification registry and against the chain itself. For a proxy the answer is deliberately split in two: whether the proxy is verified says almost nothing, whether the implementation it currently po

POST https://kette.halowerk.com/token/honeypot

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

POST https://kette.halowerk.com/token/restrictions

Scans the deployed bytecode for function selectors that grant control over trading, and reads the values that can be read directly. The decisive field is tax_modifiable: a tax of zero that the owner can raise to ninety-nine percent at any time is more dangerous than a fixed five percent, so the abil

POST https://kette.halowerk.com/token/holders

Reads the holder list of an ERC-20 token from a public block explorer index and reports concentration. Addresses that do not represent a person or entity - liquidity pools, bridges, burn addresses and exchange custody - are excluded from the adjusted figure and every exclusion is listed with its evi

POST https://kette.halowerk.com/token/liquidity-ownership

Reads the holders of an LP token and splits them into burned, locked in a named locker, and free. Burned and locked are two different things and are reported separately - burned is gone for good, locked comes back. A locker contract that is not in the curated table yields is_locker "unbekannt" rathe

POST https://kette.halowerk.com/token/authorities

Reads the contract itself rather than a project's claims. Ownership renouncement is checked, not believed: the zero address in owner() is evidence, a sentence in a whitepaper is not. Dangerous functions are found by their four-byte selectors in the runtime bytecode, and every finding names the funct

POST https://kette.halowerk.com/contract/upgrade-risk

Upgradeability alone is not a finding — every serious protocol is upgradeable. The finding is who holds the key and how much warning holders get. This endpoint reads the proxy pattern from the EIP-1967 slots, the clone bytecode or an implementation() call, resolves the admin, checks whether that adm

POST https://kette.halowerk.com/token/unlocks

Looks up a crypto asset by its exact NetSupply slug or an unambiguous symbol, then returns the scheduled releases inside a caller-selected window of up to 365 days. Unlock amounts remain decimal strings so large token quantities are not rounded. Each event states whether the schedule is enforced on-

POST https://kette.halowerk.com/wallet/allowances

Reads Approval events of one wallet from the chain, resolves the CURRENT allowance for every token and spender pair with a direct call, and weighs it against the balance actually held. An unlimited approval on an empty balance carries no risk and is reported as such. Every entry carries ready-made c

POST https://kette.halowerk.com/tx/decode

Turns opaque call data into something an agent can reason about before signing. The method signature is resolved from the verified source of the contract first, then from this hub's own list of common signatures, then from the open selector directory — and the answer always names which of the three

POST https://kette.halowerk.com/tx/simulate

Answers the question that stands before every signature: what really happens to my assets and my rights. The call is executed against the state of a named block on a simulation interface, never on the chain — this hub holds no private key and broadcasts nothing. Balance changes are not inferred from

POST https://kette.halowerk.com/token/report

Runs the identity resolver, the verification check, the authority scanner and the upgrade risk check against one token and merges them into a single answer. Nothing new is measured here: every statement carries the endpoint number it came from, so any finding can be re-bought individually and checke

POST https://kette.halowerk.com/wallet/portfolio

Lists token and native balances of one wallet across chains and prices them where a price exists. priced_pct is mandatory and says how much of the portfolio is actually backed by a price - a total where a third of the holdings have none is not an answer without that number. Tokens that carry the mar

POST https://kette.halowerk.com/wallet/activity

Reads the transaction history of one wallet from a public block explorer index and groups it by kind of action. Classification follows the called contract and method, never the amount - a transfer to a known router is a swap, not a payment. Anything that cannot be backed by a method name stays in th

POST https://kette.halowerk.com/wallet/pnl

Reads token movements of a wallet, prices every inflow and outflow at the time it happened, and derives cost basis, realised and unrealised profit or loss per asset. The method is stated because the result depends on it. Uncertainty is a mandatory field, not a footnote: an on-chain history knows not

POST https://kette.halowerk.com/wallet/classify

Derives behaviour classes from on-chain activity: share of swaps, regularity of intervals, hour-of-day spread, counterparty count and contract code. Several classes at once are allowed and usually more accurate than one. Every class carries its evidence; without evidence no class is set. automation_

POST https://kette.halowerk.com/wallet/counterparties

Collects the addresses a wallet interacted with from its transactions and token transfers, counts the interactions per edge and names the type of each contract where it can be backed by a curated entry or a verified contract name. Depth is capped at two by design: anything deeper turns this into a t

POST https://kette.halowerk.com/wallet/balances

Reads token balances of one wallet on several chains from a public index and the native balance from the node itself. The same asset exists on several chains in different versions; canonical and bridged issues are reported separately and still summed, because both together are the answer. Every chai

POST https://kette.halowerk.com/tx/status

Reads one transaction hash on Ethereum, Base, Arbitrum, Optimism, Polygon or BNB Smart Chain and answers the question an agent actually has: did it go through, is it final yet, and what did it cost. Finality is defined differently per chain, so the rule used and the required block count are part of

POST https://kette.halowerk.com/gas

Reads the fee history of the last 20 blocks on Ethereum, Base, Arbitrum, Optimism, Polygon or BNB Smart Chain and returns what a transaction costs right now. Priority fees come from the 10th, 50th and 90th percentile of the tips actually paid in those blocks — the percentile used is named, not hidde

POST https://kette.halowerk.com/chain/health

Queries every public RPC endpoint this hub knows for a chain in parallel — at least three, usually five — and reports what each one says instead of trusting one. Disagreement is the valuable finding: a single endpoint that lags or serves a different fork is exactly the failure mode this endpoint is

POST https://kette.halowerk.com/bridge/track

Reads the source transaction on chain, identifies the bridge from the contracts it touched, and reports what actually left the wallet. overdue is measured against the usual duration of THAT bridge, and the comparison value is part of the answer - not against a fixed number. For bridges that need a m

POST https://kette.halowerk.com/graph/patterns

Analyzes only the transaction graph supplied in the request. It detects four mechanical graph patterns: directed rings, pass-through nodes that receive and send similar amounts within a configured time gap, star patterns around one high-degree node, and chain-like structuring where similar amounts m

How to call

cURL · x402-fetch / x402-axios will auto-handle 402
curl -X POST https://kette.halowerk.com
/.well-known/x402.json
https://kette.halowerk.com/.well-known/x402

Listed in

Directories this entry was found in.

cdp-bazaar