Hub · Blockchain & Onchain Data
Blockchain Data
139 published endpoint URLs. Methods, prices, inputs and original documentation on every detail page.
kette.halowerk.com · Catalog updated 2026-11-19 UTC
Endpoints
61–120 of 139- Blockchain Data0.001 USDC
base receipt event emitter counts
POSThttps://kette.halowerk.com/v1/base-receipt-event-emitter-countsBase receipt event emitters: group receipt logs by emitting contract and count events. Use it when an agent needs to identify which contracts emitted the receipt events.
- Blockchain Data0.001 USDC
base receipt execution and data fee split
POSThttps://kette.halowerk.com/v1/base-receipt-execution-and-data-fee-splitBase receipt fees return L2 execution and L1 data fees in wei, with their measured subtotal. Use it when an agent needs to reconcile the two reported fee components.
- Blockchain Data0.001 USDC
base receipt log bloom occupancy
POSThttps://kette.halowerk.com/v1/base-receipt-log-bloom-occupancyBase receipt bloom returns set and unset bits plus the resulting three-bit random-match estimate. Use it when an agent needs to estimate the selectivity of a receipt log bloom.
- Blockchain Data0.001 USDC
base receipt log order evidence
POSThttps://kette.halowerk.com/v1/base-receipt-log-order-evidenceBase receipt event order: report first and last log indices and whether indices increase strictly. Use it when an agent needs to verify the recorded ordering of an event stream.
- Blockchain Data0.001 USDC
base receipt log topic arities
POSThttps://kette.halowerk.com/v1/base-receipt-log-topic-aritiesBase receipt log topics: count anonymous or indexed log shapes without guessing event signatures. Use it when an agent needs to validate event ingestion expectations.
- Blockchain Data0.001 USDC
base receipt signature frequency leader
POSThttps://kette.halowerk.com/v1/base-receipt-signature-frequency-leaderBase receipt event frequencies return the most common logged signature and its frequency among tagged events. Use it when an agent needs to prioritize the event decoder for an observed transaction.
- Blockchain Data0.001 USDC
base transaction access list totals
POSThttps://kette.halowerk.com/v1/base-transaction-access-list-totalsBase transaction access list: count declared addresses and storage slots, including repeated entries. Use it when an agent needs to evaluate the access-list footprint of a transaction.
- Blockchain Data0.001 USDC
base transaction calldata zero density
POSThttps://kette.halowerk.com/v1/base-transaction-calldata-zero-densityBase transaction calldata composition: count zero and nonzero bytes in the user-supplied call payload recorded on chain. Use it when an agent needs to estimate calldata byte composition without decoding function arguments.
- Blockchain Data0.001 USDC
base transaction declared fee headroom
POSThttps://kette.halowerk.com/v1/base-transaction-declared-fee-headroomBase transaction fee cap headroom: compare the declared execution fee cap with the observed effective gas price. Use it when an agent needs to review execution fee assumptions in a settled transaction.
- Blockchain Data0.001 USDC
base transaction gas limit consumption
POSThttps://kette.halowerk.com/v1/base-transaction-gas-limit-consumptionBase transaction gas limit use: compare executed gas with the declared limit and report unused units. Use it when an agent needs to size future gas limits from an observed transaction.
- Blockchain Data0.001 USDC
base transaction inclusion delay
POSThttps://kette.halowerk.com/v1/base-transaction-inclusion-delayBase transaction inclusion depth: return the transaction block, observed tip and separation in blocks. Use it when an agent needs to determine observed inclusion depth.
- Blockchain Data0.001 USDC
base usdc bounded netflow
POSThttps://kette.halowerk.com/v1/base-usdc-bounded-netflowBase USDC movements: return incoming, outgoing and net atomic amounts within up to100 recent blocks. Use it when an agent needs bounded read-only EVM observations.
- Blockchain Data0.001 USDC
base usdc receipt flow conservation
POSThttps://kette.halowerk.com/v1/base-usdc-receipt-flow-conservationBase USDC flows return distinct sending and receiving accounts, self transfers and total gross units. Use it when an agent needs to reconcile canonical USDC movement in a payment receipt.
- Blockchain Data0.001 USDC
base usdc receipt net settlement shape
POSThttps://kette.halowerk.com/v1/base-usdc-receipt-net-settlement-shapeBase USDC settlement returns net debtor and creditor counts and total units after intermediaries cancel. Use it when an agent needs to distinguish gross token traffic from net movement.
- Blockchain Data0.001 USDC
collection approval operator scope
POSThttps://kette.halowerk.com/v1/collection-approval-operator-scopeNFT approvals return whether the token-level delegate also has collection-wide authority from the current owner. Use it when an agent needs the scope of an observed delegate relationship.
- Blockchain Data0.001 USDC
collection display name symbol
POSThttps://kette.halowerk.com/v1/collection-display-name-symbolNFT collection identity returns the on-chain display name and ticker symbol at one block. Use it when an agent needs the collection labels declared by a contract.
- Blockchain Data0.001 USDC
collection enumerated circulating supply
POSThttps://kette.halowerk.com/v1/collection-enumerated-circulating-supplyNFT collection supply returns the declared circulating token count for an enumerable collection. Use it when an agent needs the current supply without assuming sequential IDs.
- Blockchain Data0.001 USDC
collection enumerated token window
POSThttps://kette.halowerk.com/v1/collection-enumerated-token-windowNFT collection paging returns up to five token IDs by on-chain enumeration position. Use it when an agent needs a bounded page of actual IDs in the collection.
- Blockchain Data0.001 USDC
collection metadata reference reuse
POSThttps://kette.halowerk.com/v1/collection-metadata-reference-reuseNFT metadata comparison returns whether two tokens point to the same metadata and share a locator scheme. Use it when an agent needs duplicate metadata references across two token IDs.
- Blockchain Data0.001 USDC
collection owner collection position
POSThttps://kette.halowerk.com/v1/collection-owner-collection-positionNFT holder balance returns the token owner’s holding count and share of enumerable supply in parts per million. Use it when an agent needs a within-collection concentration measure.
- Blockchain Data0.001 USDC
collection page owner dispersion
POSThttps://kette.halowerk.com/v1/collection-page-owner-dispersionNFT holder distribution returns distinct holders and the largest holding within a bounded enumeration page. Use it when an agent needs ownership dispersion among adjacent enumerated tokens.
- Blockchain Data0.001 USDC
collection same owner comparison
POSThttps://kette.halowerk.com/v1/collection-same-owner-comparisonNFT ownership comparison returns whether two token IDs have the same owner at one block. Use it when an agent needs a collection-local ownership comparison without identity attribution.
- Blockchain Data0.001 USDC
collection standard extension discovery
POSThttps://kette.halowerk.com/v1/collection-standard-extension-discoveryNFT collection lookup returns declared support for metadata, enumeration, royalties and ERC-4906 updates. Use it when an agent needs the available public collection interfaces.
- Blockchain Data0.001 USDC
collection token metadata locator
POSThttps://kette.halowerk.com/v1/collection-token-metadata-locatorNFT token metadata returns its public locator or an inline-content digest without downloading the resource. Use it when an agent needs the metadata reference for a token.
- Blockchain Data0.001 USDC
constant product reserve invariant
POSThttps://kette.halowerk.com/v1/constant-product-reserve-invariantToken liquidity returns the reserve product and its integer square root for an Ethereum V2 pair. Use it when an agent needs a block-pinned liquidity invariant.
- Blockchain Data0.001 USDC
erc1155 token balance vector
POSThttps://kette.halowerk.com/v1/erc1155-token-balance-vectorMulti token balances: return ERC1155 balances for supplied token IDs at one observed block. Use it when an agent needs bounded read-only EVM observations.
- Blockchain Data0.001 USDC
erc20 allowance exposure matrix
POSThttps://kette.halowerk.com/v1/erc20-allowance-exposure-matrixBase token approvals: return token/spender allowances. Use it when an agent needs approval exposure.
- Blockchain Data0.01 USDC
erc20 allowance facts
POSThttps://kette.halowerk.com/v1/erc20-allowance-factsRead the current ERC-20 allowance for one owner and spender without signing. Bounded read-only observations with source time and checksum; no wallet signing or purchase. Public pages obey robots and private-target checks. No article bodies,
- Blockchain Data0.001 USDC
erc20 holder supply share
POSThttps://kette.halowerk.com/v1/erc20-holder-supply-shareToken supply share: return one holder balance and its fraction of ERC20 total supply at one block. Use it when an agent needs bounded read-only EVM observations.
- Blockchain Data0.01 USDC
erc20 transfer interpret
POSThttps://kette.halowerk.com/v1/erc20-transfer-interpretDecode one actual ERC-20 Transfer log and normalize its atomic amount. Bounded read-only observations with source time and checksum; no wallet signing or purchase. Public pages obey robots and private-target checks. No article bodies, autho
- Blockchain Data0.001 USDC
erc721 ownership and approval
POSThttps://kette.halowerk.com/v1/erc721-ownership-and-approvalNFT ownership lookup: return the ERC721 owner and approved address for one token. Use it when an agent needs bounded read-only EVM observations.
- Blockchain Data0.001 USDC
ethereum block access list footprint
POSThttps://kette.halowerk.com/v1/ethereum-block-access-list-footprintEthereum access lists return declared addresses, unique address and slot pairs and repeated slot references. Use it when an agent needs the declared storage footprint across transactions.
- Blockchain Data0.001 USDC
ethereum block blob commitment reconciliation
POSThttps://kette.halowerk.com/v1/ethereum-block-blob-commitment-reconciliationEthereum blob data returns blob hash count, its implied gas and agreement with the block header. Use it when an agent needs a consistency check between blob transactions and header accounting.
- Blockchain Data0.001 USDC
ethereum block consensus withdrawal distribution
POSThttps://kette.halowerk.com/v1/ethereum-block-consensus-withdrawal-distributionEthereum withdrawals return the total Gwei, distinct recipients and largest single consensus withdrawal. Use it when an agent needs the distribution of consensus-layer withdrawals.
- Blockchain Data0.001 USDC
ethereum block creation initcode load
POSThttps://kette.halowerk.com/v1/ethereum-block-creation-initcode-loadEthereum contract creation returns the total and largest transaction initcode sizes and the number of creations. Use it when an agent needs the deployment payload volume in a block.
- Blockchain Data0.001 USDC
ethereum block fee recipient direct payments
POSThttps://kette.halowerk.com/v1/ethereum-block-fee-recipient-direct-paymentsEthereum fee recipient payments return the declared value and count of outer transactions addressed to the block beneficiary. Use it when an agent needs visible transfers addressed to the header fee recipient.
- Blockchain Data0.001 USDC
ethereum block plain value flow
POSThttps://kette.halowerk.com/v1/ethereum-block-plain-value-flowEthereum value flow returns declared wei in empty-input payments and in transactions carrying call data. Use it when an agent needs a split of declared native value by transaction shape.
- Blockchain Data0.001 USDC
ethereum block repeated call selector groups
POSThttps://kette.halowerk.com/v1/ethereum-block-repeated-call-selector-groupsEthereum contract calls return the most repeated destination and method-selector combination by count, with its first position. Use it when an agent needs the largest cluster of calls to the same contract method.
- Blockchain Data0.001 USDC
ethereum block self directed call mix
POSThttps://kette.halowerk.com/v1/ethereum-block-self-directed-call-mixEthereum self transactions return self-addressed envelope counts split by empty and nonempty input. Use it when an agent needs to distinguish self-directed calls from simple envelopes.
- Blockchain Data0.001 USDC
ethereum block sender burst length
POSThttps://kette.halowerk.com/v1/ethereum-block-sender-burst-lengthEthereum block ordering returns the longest consecutive sequence from the same sender and its starting position. Use it when an agent needs the strongest same-sender burst within a block.
- Blockchain Data0.001 USDC
ethereum block sender concentration
POSThttps://kette.halowerk.com/v1/ethereum-block-sender-concentrationEthereum block senders return distinct sender count, maximum transactions per sender and one-time senders. Use it when an agent needs an aggregate view of sender concentration.
- Blockchain Data0.001 USDC
evm address state bundle
POSThttps://kette.halowerk.com/v1/evm-address-state-bundleEVM address lookup: return code type, native balance, nonce and the EIP-1967 implementation slot. Use it when an agent needs bounded read-only EVM observations.
- Blockchain Data0.001 USDC
evm contract bytecode comparison
POSThttps://kette.halowerk.com/v1/evm-contract-bytecode-comparisonBase contract code: return byte counts and SHA256 equality. Use it when an agent needs code comparison.
- Blockchain Data0.001 USDC
evm interface support probe
POSThttps://kette.halowerk.com/v1/evm-interface-support-probeContract interface check: return ERC165 responses for supplied interface identifiers. Use it when an agent needs bounded read-only EVM observations.
- Blockchain Data0.001 USDC
evm latest block utilization
POSThttps://kette.halowerk.com/v1/evm-latest-block-utilizationEVM block utilization: return latest block gas usage, base fee and transaction count. Use it when an agent needs bounded read-only EVM observations.
- Blockchain Data0.001 USDC
evm receipt token transfer ledger
POSThttps://kette.halowerk.com/v1/evm-receipt-token-transfer-ledgerTransaction token transfers: return all standard Transfer events in a mined receipt with raw amounts. Use it when an agent needs bounded read-only EVM observations.
- Blockchain Data0.01 USDC
evm transaction fees
POSThttps://kette.halowerk.com/v1/evm-transaction-feesCalculate receipt-based gas fees and separately report available L1/blob fee components. Bounded read-only observations with source time and checksum; no wallet signing or purchase. Public pages obey robots and private-target checks. No art
- Blockchain Data0.01 USDC
evm transfer receipt
POSThttps://kette.halowerk.com/v1/evm-transfer-receiptEVM transaction receipt: return the canonical transaction receipt, observed depth and ERC-20 event count. Use it when an agent needs transfer evidence.
- Blockchain Data0.01 USDC
feed entry deduplicate
POSThttps://kette.halowerk.com/v1/feed-entry-deduplicateGroup supplied feed entries by canonical URL while preserving meaningful query fields. Remove fragments and tracking keys only; preserve other queries, their order and HTTP/HTTPS distinctions. No network retrieval.
- Blockchain Data0.001 USDC
pair balanced deposit counterpart
POSThttps://kette.halowerk.com/v1/pair-balanced-deposit-counterpartLiquidity deposit returns the raw quantity of the opposite token needed at the pinned reserve ratio. Use it when an agent needs the paired quantity for a balanced contribution.
- Blockchain Data0.001 USDC
pair input for reserve output share
POSThttps://kette.halowerk.com/v1/pair-input-for-reserve-output-shareToken market depth returns the raw input needed to remove a selected fraction of the output reserve. Use it when an agent needs a pool depth estimate at a chosen reserve fraction.
- Blockchain Data0.001 USDC
pair lp deposit limiting side
POSThttps://kette.halowerk.com/v1/pair-lp-deposit-limiting-sideLiquidity supply returns the limiting deposit side and provisional LP issuance from two offered amounts. Use it when an agent needs to compare a proposed two-token deposit with existing reserves.
- Blockchain Data0.001 USDC
pair lp redemption reserve claim
POSThttps://kette.halowerk.com/v1/pair-lp-redemption-reserve-claimLiquidity token redemption returns both pro-rata reserve claims for a stated LP quantity. Use it when an agent needs an estimate of each token share before fees.
- Blockchain Data0.001 USDC
pair minimum lp for token claim
POSThttps://kette.halowerk.com/v1/pair-minimum-lp-for-token-claimLiquidity token threshold returns the smallest LP quantity whose pro-rata claim covers a target amount. Use it when an agent needs a minimum share count under the current reserve ratio.
- Blockchain Data0.001 USDC
pair swap constant product growth
POSThttps://kette.halowerk.com/v1/pair-swap-constant-product-growthLiquidity fee retention returns the raw increase in the reserve product after one simulated swap. Use it when an agent needs to quantify fee and integer-rounding effects on the invariant.
- Blockchain Data0.001 USDC
pair swap exact input raw quote
POSThttps://kette.halowerk.com/v1/pair-swap-exact-input-raw-quoteToken swap quote returns output raw units for an exact input on a canonical Ethereum V2 pair. Use it when an agent needs a reserve-based quote in token order.
- Blockchain Data0.001 USDC
pair swap exact output input floor
POSThttps://kette.halowerk.com/v1/pair-swap-exact-output-input-floorToken swap cost returns the standard V2 router input quote for an exact output quantity. Use it when an agent needs the required raw input for a selected output.
- Blockchain Data0.001 USDC
pair swap reserve price displacement
POSThttps://kette.halowerk.com/v1/pair-swap-reserve-price-displacementToken price impact returns the change in the reserve ratio after a hypothetical exact-input swap. Use it when an agent needs the post-swap spot-price displacement in basis points.
- Blockchain Data0.01 USDC
public api contract diff
POSThttps://kette.halowerk.com/v1/public-api-contract-diffCompare two supplied API contract objects and flag possible breaking structural changes. Bounded read-only observations with source time and checksum; no wallet signing or purchase. Public pages obey robots and private-target checks. No art
- Blockchain Data0.01 USDC
robots policy explain
POSThttps://kette.halowerk.com/v1/robots-policy-explainReturn the published robots decision for one URL and the fixed HALOWERK crawler. Bounded read-only observations with source time and checksum; no wallet signing or purchase. Public pages obey robots and private-target checks. No article bod