Conversation
KeeperHub agents on ERC-8004 ranked primarily by reputation events,
but until now there was no path for users who paid for a workflow
to leave on-chain feedback. This adds both interfaces -- CLI and
MCP -- to invoke the new server endpoint that signs and broadcasts
giveFeedback() through this wallet's Turnkey policy.
CLI: keeperhub-wallet feedback --execution-id <id> --value <int>
[--decimals <int>] [--comment <text>] [--agent-id <id>]
[--chain-id <int>]
MCP: feedback({executionId, value, valueDecimals, comment?, agentId?,
agentChainId?}) -- the calling LLM is expected to use this AFTER
a successful call_workflow when the user confirms a rating.
Both share the same HMAC-signed POST to /api/agentic-wallet/feedback
on app.keeperhub.com. The user wallet pays gas natively
(~$0.05-2 per call at typical mainnet gas). Future improvement is
gas sponsorship via Pimlico or Turnkey native -- noted in the
keeperhub-side policy header.
Validated end-to-end on Ethereum mainnet against KeeperHub's
ERC-8004 agent (id 31875): tx 0xd8391d...3e92 confirmed in block
25041073 with 171813 gas used.
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
CLI usage
```bash
keeperhub-wallet feedback \
--execution-id <id-from-call_workflow-response> \
--value 5 --decimals 0 \
--comment "great workflow"
```
Optional flags: `--agent-id` (default: KeeperHub agent 31875), `--chain-id` (default: 1, the only chain server-side allows today), `--base-url` (default: app.keeperhub.com).
MCP usage
```json
{
"name": "feedback",
"arguments": {
"executionId": "c5ybokpmwxi7kiau5wxja",
"value": 5,
"valueDecimals": 0,
"comment": "great workflow"
}
}
```
The calling LLM is expected to use this AFTER a successful `call_workflow` when the user confirms a rating. The companion `feedback` field in the workflow execution response (server-side) carries the prompt + tool reference so any agent reading workflow output knows to surface this to the user.
Test plan