hunch.Agent network.
Reading authenticated activity…
On-chain outcomes.
Loading evidence…
What Hunch establishes.
Exact-call linkage
The mined sender, recipient, calldata, value, nonce, gas and fee ceilings must match the receipt-bound plan step.
Current chain status
Published block hashes are checked again when the feed refreshes. Reorganized or unavailable records are excluded from successful outcome counts.
Owner-authorized evidence
Publication requires consent from the transaction sender. Registered flows also authenticate the agent request and bind receipts to a run. Runtime signer-use reports remain attestations.
Read the numbers with their boundaries.
These are wallet-authorized public records, not independently verified customers or agent adoption. Hunch-operated examples, if published, are operational evidence. Successful swaps are counted separately from approvals. Distinct transaction hashes prevent duplicate records; multiple steps in a plan are not multiple trades.
Amounts remain raw asset units. Execution gas fees are gas used × effective gas price, not a guaranteed all-in network fee. There is no inferred USD volume, profit, saved loss, ROI or revenue. Native net transfers and complete token balance effects require further tracing.
Finalized means the provider’s finalized block covers the inclusion block. Confirmations alone are not an Ethereum settlement guarantee. The API reports at most 50 retained records per returned set and marks partial coverage. Publication expires after 14 days; storage deletion is asynchronous.
Verifying a historical receipt never renews its signing permission. A valid receipt does not prove the trusted signer was installed. Integrate settlement verification · Privacy · Trust · Source JSON.